New modern Webrowser Quasar

@LiveForIt @joerg @samo79 @K-L
If I may chime in on this discussion. For now, it looks like the program will be ported to AOS4 from the original code.
If the original version uses “ibfreetype + fontconfig,” then even if someone were doing this without AI, they wouldn't bother with it.
The priority is stable code, and then fine-tuning. Why create problems for yourself right from the start? There will definitely be time for that later.

@smarkusg

Well, yeah you are right

@Maijestro

Quote:
I'd like to advocate for using MUI or ReAction, rather than native Intuition/GadTools, for the user interface. It's likely that AI can just as easily create the UI using native Intuition as using one of the GUI toolkits, so there's little advantage to the developer in the AI era.

But there are advantages to the user, who can customize the look of the UI using one of the toolkits, unlike native Intuition. And there are advantages to the system, since it's more memory efficient for several programs to share something like a toolbar class than it is for each program to roll their own using just native Intuition/GadTools gadgets.

@Maijestro

Amazing!

@samo79
Quote:All of my AmigaOS 4.x parts were on the Pleyo OWB SVN.
That doesn't exist since several years anymore, but the author of the AROS OWB port who, unlike the MorphOS OWB developer, uploaded all of his changes to the Pleyo SVN as well may still have a copy of those sources.
I don't have the complete OWB sources anymore, all I have on backups are diffs of my latest changes to the OWN SVN, and the sources of my AmigaOS 3.9/m68k port which doesn't include the AmigaOS 4.x-only AmigaOS native font rendering functions: The bullet.library from AGFA Compugraphic used in AmigaOS 2.1-3.9 was way too limited compared to Detlef's AmigaOS 4.x outline font engine.

@Maijestro

Wow. Looking good. This is a needed product for OS4.