Based on @wolf480pl 's suggestion, over the next few days I'll attempt to give very highlevel introductions to the topics I tend to toot about, to help you follow along. I don't know how successful I'll be...

I will pin these!

Namely how browsers & operating systems work, energy-efficient computing, etc. Feel free to ask questions to help refine these introductions!

Follow

I'm an amateur browserengine dev as a hobby. I like showing the potential for HTML+CSS downloaded over HTTP to work beautifully across any medium! I started with an auditory browser named "Rhapsode", and am preparing to create one for TV remote input called "Haphaestus".

Aiming to achieve deeply-intertwined accessibility, IoT coolness, simplicity, & privacy.

These apply CSS to the downloaded/parsed XML for that styletree to be transliterated into output once layed-out.

1/2

I take care to bring user & alternative stylesheets to the forefront (concepts which have always been part of the specs...), and I ensure useragent & user styles can be bolder upon knowing there's no authorstyles!

Rhapsode barely has a layout pass, instead passing the "styletree" near-directly to eSpeak NG as SSML (Speech Synthesis Markup Language). Then there's the matter of input...

Forms will (preparing to implement them for Rhapsode now!) be a separate codepath. JS is unimplemented.

2/2

Oh, and for the sake of helping follow along with my dev toots I should state I give the different components of my browser engine distinctive names:

* HURL - URL dispatcher
* Stylist - CSS engine
* Mondrian - Rendering engine (to be implemented)
* Layout engines to-be-named...

I make heavy use of 3rd party parsers including XML/HTML-Conduit. I will reuse major components of GNOME's text-rendering stack.

Collectively these are the "Argonaut Stack" upon which I create the "Argonaut Suite"!
3/2

Sign in to participate in the conversation
FLOSS.social

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).