11–20 of 21 posts
Neat, but the zoom works the opposite way that I'd expect, is that just me?
Either way it's just two API calls in the demo page, the buttons aren't part of the lib itself
Shame it uses the bloated jquery UI
We build the lib into two components. There's the jQuery-dependent one that just powers the UI interaction and translates cols and rows into pixels for DOM elements. Then there's the main logic, which is an agnostic class that implements all the grid positioning and collision management logic. This makes it possible to calculate new grid positions on the server-side. Same with running unit tests.
http://cl.ly/image/1E0A0z2C0x0b -> http://cl.ly/image/102E232Z443j
I don't see why the items should dance around when "zooming out"/adding more rows, if the available space and constraints are the same. Is there a gravity component to it? http://cl.ly/image/1E0A0z2C0x0b -> http://cl.ly/image/102E232Z443j
PS. We have some docs for these methods https://github.com/uberVU/grid#resizegridrows
Neat, but the zoom works the opposite way that I'd expect, is that just me?
It was reversed up until a few days ago, when I was told "adding/removing rows works the opposite way that you'd expect it" heh Either way it's just two API calls in the demo page, the buttons aren't part of the lib itself
Changing my browser window width doesn't seem to affect anything. Even after a page reload. It doesn't seem responsive at all. Am I missing something?
Take a look at the project README for more info: https://github.com/uberVU/grid/blob/master/README.md
Earlier quoted context omitted.
It was reversed up until a few days ago, when I was told "adding/removing rows works the opposite way that you'd expect it" heh Either way it's just two API calls in the demo page, the buttons aren't part of the lib itself
This is possibly because the buttons aren't labeled. Depending on whether you see them as "zoom in/out" buttons or "add/remove columns" buttons, your expectation is going to be different.