3 ms·
The great thing about writing the layout computation code is that specs are mostly additive. You can start by supporting only a few properties and then as you p
by vjeux 11y ago
The great thing about writing the layout computation code is that specs are mostly additive. You can start by supporting only a few properties and then as you progress support more and more.
I've used this approach for css-layout[1] and in 2 weeks I got enough implemented to support most use cases we've needed to build mobile apps.
Also, Cassowary won't really help you there. It's going to take a much bigger effort to translate CSS into constraints than just reimplementing the steps themselves.
[1] https://github.com/facebook/css-layout https://github.com/facebook/css-layout
- leeoniya 11y agocool project! flex-box is a mostly self-contained and powerful spec (if i understand correctly). however, when you don't need to account for floats, relative layout, mixed box-sizing, negative margins, complex overflow conditions and interaction with a ton of older specs, you vastly simplify the problem space for yourself. it makes perfect sense for a modern system but is quite far from a general impl that can compute layout from html+css unconditionally. the article starts with: "Once I got an X idea, but its implementation required a calculated DOM with all its styles and goodies" so the goal is not "the most useful subset". flexbox is currently the least-used (& least supported) layout, so for the author's purposes which sounds like scraping existing markup would not help very much.