141–146 of 146 posts
Perhaps I'm missing something, but why can't we render HTML directly onto the canvas in the browser? The parser is there, the layout engine is already implemented, and the calculation of box layout is already done. It should be doable without going in circles. If only the browser had a flag indicating which "surface" to render on. I was looking at Glide Grid the other day, and it renders so fast, even with 1 million…
There is also HTML/CSS layout engine litehtml ( https://github.com/litehtml/litehtml ) and even a full-blown web engine in JS: WebKit.js ( https://github.com/trevorlinton/webkit.js )
What in the world?
Earlier quoted context omitted.
The purpose is for documents that don't use flexbox.
Alright so that’s about as useful as saying “I built a word processor without left, right, middle align or tables”.
This is an amazing piece of work. Thanks for making this open-source. The default way of generating beautiful PDFs in the backend these days is, running a headless browser and using browser APIs to turn HTML/CSS into PDFs. And apparently, it's a bit costly running instances of browser in the server and scale it properly for huge workloads. This is literally a game changer. Now it's possible to design PDFs using HTML/…