4 ms·
Why would they showcase the drag and drop coupled with this intriguing isometric block UI? It really takes the focus away from the core functionality of the li
by jordache 9y ago
Why would they showcase the drag and drop coupled with this intriguing isometric block UI? It really takes the focus away from the core functionality of the library.
I was totally focused on how the blocks interact. It's not anywhere close to the type of apps I build so the examples do not really give me a feel how well it may work for typical CRUD use cases.
- zeroxfe 9y ago> Why would they showcase the drag and drop coupled with this intriguing isometric block UI? Because it looks and feels awesome!? :-) Seriously though, I didn't think it took that much away from the core functionally. I quite enjoyed testing the limits of the functionality with the demo.
- andyfleming 9y agoI really like the page, but I think that there could be a section with much clearer real-world use cases would be helpful, especially if it showed the actual syntax. There's not even a link to the documentation (though it's in the README if you click "Contribute").
- joeax 9y agoMy takeaway was that they wanted to show that anything can be made draggable, i.e. isometric blocks created using CSS transforms. The browser actually maps mouse/touch events from the transformed space back to the untransformed cartesian x,y point. In other words, if I scale a 100x100 <div> 3x then hover exactly in the center of it, I'll get 50,50 regardless of the scale/skew/rotation/matrix. This is really useful for collision detection, which they are trying to demo.
- ehnto 9y agoI am really surprised at the backlash toward the demo. It's simple and fun. Dragging and dropping is a pretty simple concept anyway, you're going to have to build your logic into it. The reason this is cool is because cross browswer drag and drop is difficult with the native APIs. Not having to deal with them for basic drag and drop is great and likely the point of the library.