Yes! A long time no real progress on here, but we haven't sat still (well, a bit, a lot of other things got in between).. but we're again busy with getting things done!

So, at the moment, there are a lot of different systems all waiting to be merged into the big engine system. Most of these will replace older systems, and we need to make sure things work properly. Since they are heavy rewrites, we have attempted a few times to get things merged, which failed over and over again.

It was just too much to handle in one go, which in all fairness, did not do good to the overall spirit of things.

But since a month or so, we decided to see if we could get some help from AI on this part.. I know i know.. will gosub become a vibe-browser now!?? No, absolutely not. But we do see the potential in having a developer sitting next to you who can see things much faster and much deeper than you yourself can.

And this helps a lot in the big refactoring parts.. We allowed it to get the knowledge of the current engine and the new components like the new api structure. We came up with a plan to gradually move things over into the engine without 1) getting too overwhelmed by "new" code and 2) without breaking all the things.

It turns out that this was exactly what it did, and we now have an engine that works on the new api system. Sure, there is still a LOT of code coming into the engine, but in essence this code has not changed, just moved with some wrappers or small changes here and there. All in all, it gave us back the small PR's, a way to review code and to get things moving along again.

We are doing basically the same thing now with the new render pipeline, after which we can remove the old one from the code completely. Then, it's a matter of waiting until we get the new CSS3 system into the engine and we should be able to have rendered content in a flow that we want.