-
Notifications
You must be signed in to change notification settings - Fork 67
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Document and maybe integrate "blocks" or "cells" for easy grid layouts #294
Comments
Hey @andymeneely, I've put together a "halfway" concept: Right now, it's looking like it'll be tricky to support Here's an example of But I'm not loving the asymmetry of a unit available in We could say What are your thoughts? Happy to move forward with a PR and call out the asymmetry in the documentation, or shelve it for another time :) |
big, big +1 on this issue. I agree that having a different I haven't checked out the associated PR yet, but looking at how DPI is passed to I'd encourage you to not complicate this by having non-square cells, gutters, or anything like that. This feature would be amazing for rapidly prototyping cards on graph paper and/or in code. It doesn't need to be anything more. |
Yeah adding a custom unit shouldn't be hard at all. I'll be picking up my Squib work soon and will do something like this. And it'll work the same between yaml and ruby. You'll be able to modify the size of a "cell" as a config setting and it'll default to 75px or 1/8in. |
This is going to be part of v0.16! |
Heard about this neat little monkeypatch from @mzemel. This snippet: https://github.com/mzemel/whipped/blob/a31cd0fcb19223755e33b1edbc0f0343448134aa/deck.rb#L4-L14
So you can then align things like
3.blocks
in your code easily without doing multiplication in your head.At the very least, we could document this.
We could also introduce a "block" or "cell" as a custom unit that defaults to 37.5. That way you can have a layout file that says:
The text was updated successfully, but these errors were encountered: