treesaver

A layout engine works on a different level of abstraction, putting layout features in CSS will be awkward. CSS is fine for typographic features and selectors, but layout is all about relationships. Actually, one really impressive engine for web layout engine is Treesaver: https://github.com/Treesaver/treesaver It's meant to provide primitives that are familiar to people from graphic design working on paginated content, like columns, grids, floating containers. Like Latex, it's also has the least-bad-layout strategy, but here, this runs on the client in Javascript, so that it adapts to the screen size. I had just stopped working on a startup based on this technology. Operationally, it was proving extremely difficult adding effects that people are taking for granted in InDesign to work in a responsive manner on top of CSS and a 20kLoC Javas

If you have a minute, take a peek at the code -- really nice JavaScript style, especially for fiddly UI work: https://github.com/Treesaver/treesaver/blob/master/src/ui/ar...

Thanks all, author here (along w/ bramstein). The documentation and site aren't quite ready yet, but we're getting there. If you're curious to see how to use the framework, your best bet is to start with this tutorial we're working on: https://github.com/Treesaver/treesaver/wiki/Walkthrough

I had a look at the problem and it seems to be related to the page transition animations (the amount of flicker seems corresponds to the animation steps.) I've created a ticket for this issue: https://github.com/Treesaver/treesaver/issues/issue/148 We'll fix it, thanks for reporting it.

That looks like a bug, I've created a ticket for this issue: https://github.com/Treesaver/treesaver/issues#issue/147 Thanks for catching and reporting it.