4 ms·

There's a project called Sciter that uses a sub/superset of CSS and HTML to create native apps. They have their own flow styling for this, and boy is it nicer t

There's a project called Sciter that uses a sub/superset of CSS and HTML to create native apps. They have their own flow styling for this, and boy is it nicer than flexbox: https://terrainformatica.com/w3/flex-layout/flex-vs-flexbox.htm https://terrainformatica.com/w3/flex-layout/flex-vs-flexbox.... More details here: https://terrainformatica.com/2018/12/11/10-years-of-flexboxing/ https://terrainformatica.com/2018/12/11/10-years-of-flexboxi... I know the author pitched this as an idea to w3c a while back, but I don't know why it was rejected in favor of flexbox.

akira2501 4y ago
What I like about my style, is that the document structure enforces the layout structure. The two are much more closely bound, and with this style, you can perform arbitrary levels of subdivisions of your containers. Working off your last link, the final "holy grail" example, with less style but the same exact layout: https://jsfiddle.net/Lpedja35/ https://jsfiddle.net/Lpedja35/ You don't have to have a matrix with an artificial rank to represent this. I only need to specify the 1 and 4 rows once. I don't have to make a square and then decide how to divide it, which, is the "table thinking" I mentioned earlier. I just observe which elements need Grow and then design from the inside out.