Closed xTrayambak closed 6 months ago
What I'm thinking is that the layout engine will have two states -- the stack (which will be rendered by processLayout) and the layout (a TableRef[tuple[x, y: int], Box])
The X and Y coordinates however are the literal coordinates where the box will be rendered, not what the Box's X and Y coordinates intend.
It seems I have found an issue in the renderer itself -- it segfaults when resizing. I'm fixing it right now.
Okay, this bug is really bizzare. Resizing works a few times, then it segfaults the 12th-14th'ish time
It only happens when the X coordinate exceeds 1000. Really weird stuff.
I'll just leave this bug and focus on the layout engine for now, if anyone interested minds helping out, please do.
Ferus can now render p1 tags. I have not commited it yet.
Welp, I scrapped it all in favour of rewriting it to be like mbrubeck/robinson's layout engine.
Screw it. I'm just brainstorming a layout engine on my own for now. Pray that I survive!
This is an extremely ambitious project. I wish you the best of luck!
Me too!
This is an extremely ambitious project. I wish you the best of luck!
Thanks!
Me too!
Thank you!
Ferus now does basic layout in the experimental branch.
We're redoing it.... again. Yep.
Not relevant to the project rewrite now. All discussions will be moved to the new layout solver
Layout has been moved in-tree again for the sake of my sanity. It's working a bit now.
Hey everyone! It's finally time for Ferus to, well, actually display HTML! This will be a megathread dedicated to slowly implementing the layout engine bit by bit. Any and all contributions are more than appreciated! Please push changes to the experimental branch, not the main branch. Once this ends, and everything is smoothed out, the experimental branch will be merged with main.