Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed position grid with 100% window height #118

Closed
Dimosthenis opened this issue Apr 2, 2015 · 4 comments
Closed

Fixed position grid with 100% window height #118

Dimosthenis opened this issue Apr 2, 2015 · 4 comments

Comments

@Dimosthenis
Copy link

First of all thank you for this useful plugin and for your hard work.

I need to create a responsive layout horizontally and vertically in full window size.
The reason I need it "full-screen" is because of the grid items which should respond on click
events and change position to all 4 edges of the screen randomly.

I changed grid-stack container to 100% width and height and added some css with data attributes like
"data-gs-y" top (position) and "data-gs-height" with percentage but It is not working as smooth I hoped
because in window resizes some items overlap

Thank you again, I hope you understand what I'm trying to accomplish

@Dimosthenis Dimosthenis changed the title Fixed position grid with fixed size items Fixed position grid with 100% window height Apr 24, 2015
@alangunning
Copy link

+1 for supporting cell_height as percentages

@stefan-schweiger
Copy link

+1

1 similar comment
@nkotha
Copy link

nkotha commented Dec 22, 2015

+1

@radiolips
Copy link
Member

It makes more sense for the user to manage this. In order to get the 100% height you're referring to, @Dimosthenis , you can simply take the height and divide it by whatever you'd like before passing a cellHeight to gridstack. This would work for initial load, but obviously would not be responsive. Now, if you change page size after that, gridstack fires resize events, and these could be used to modify the height or width of the content. I'm personally doing this in my project for some widgets but not for others - which is precisely why it shouldn't be part of the core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants