At this moment we have a few components: a html5 parser, a css parser, a css validator, a renderer that uses taffy and vello toolkits to do layouts and actually rendering. But all needs to be tied together into a single engine.

We have the following plan:

• Finish up the enginev2 part, where we have a more decent way of working with the engine altogether. This needs a little bit of work, mostly on the testing side of things (mocking stuff is more difficult now).
• Finish up the eventloop system. We created a simple eventloop system based on threads and tokio in order to deal with the async nature of browsers. It's still a poc, but we hope we can incorporate this into the main engine.
• Write up the gosub-gtk concept. This is what i'm currently doing, and its the gtk version of a browser which i started over a year ago, and never looked at again. Right now, it's more about figuring out gtk-rs and the gtk toolkit in order to make some kind of graphical user interface which looks browserlike. This is basically the "body" of what we are building.
• Once these components are done, we want to merge them all into a single repo creating a complete engine + browser. I assume we are going to split the gtk stuff away into a separate browser / useragent repo, but to make things easier for now we keep everything inside a single repo.

Much work though, but it seems that a lot of pieces are coming together finally and we might even have something hopefully soon that can actually looks like a browser! yay gosub!