We JUST merged the v2 engine proof-of-concept into the main branch. Big thanks to shark to get that one done. The whole engine setup should be much more comprehensible and we save a lot boilerplate code that was needed in the "old" version.

I'm currently busy with the GTK browser which coming along fine. It can manage tabs, loads html data and display this (in raw html form, like view-source:). However, now we need to somehow connect the engine stuff to this browser. A small substep in this process is trying to get output from a (html)renderer into the browser. Since we use vello as our main backend rendering toolkit, our goal is now to get something with vello to be renderered in the browser. Unfortunately, this seems a big issue and we are looking for all kind of ways to achieve the goal. In the meantime, we also trying to setup a second renderbackend, which uses Cairo instead of vello. The upside of this is that gtk works with cairo, so connecting them together is much easier. But obviously, we must setup a new backend which takes a bit of time (not too much though),.. it's also a very nice usecase to check our "unique selling point" of being able to switch out components is as easy as we like to say it is.. Let's hope that is the case :-)