haste-compiler VS react-grid-layout

Back then, I was using Haste to compile Haskell to JavaScript for the frontend part. But now I fail to properly restore the environment to make the hastec call work. Also, I'm not sure if Haste is still actively maintained.

My ludum-dare 34 entry does have scrolling, and some images which are only visible in some screens but not others. I didn't do any effort to load and unload them as required though, I just keep everything loaded at all times. One potential difficulty is that this game uses Haste to compile Haskell to JavaScript, soI don't know if your framework supports that.

Very cool Dustin. Reminds me (a little) of some work that the Haskell Haste folks were doing to blur the front/backend via the compiler. Interested to see what you learn along the way refactoring hyperfiddle.

You can find additional information about the React-Grid-Layout in the repository and documentation.

This is react-grid-layout with some custom logic https://github.com/react-grid-layout/react-grid-layout

react-grid-layout looks like a good candidate, but it seems like it lacks a way to customize/add rules for positioning elements to prevent "stacks" of elements. Imagine a user models a brick wall and you want to prevent users from stacking bricks above each other (prevent bricks stack bond and allow something like running bond brick pattern)

I was looking to build a somewhat similar project with react and react grid layout.

Would it be possible to prototype something like this in figma? http://react-grid-layout.github.io/react-grid-layout/examples/0-showcase.html

react-grid-layout A draggable and resizable grid layout with responsive breakpoints, for React.

A lot of projects seem to like: https://github.com/react-grid-layout/react-grid-layout

I’ve done that before using react grid layout (https://github.com/react-grid-layout/react-grid-layout) to allow for moving and resizing components, and then a lot of custom code. Having a well thought architecture makes a lot of difference there.