@Spektro The datatypes system is not really sophisticated enough to support a proper web datatype, for example inline images was part of the AmigaGuide spec, but never implemented, as it can only cope with data file at a time, no child data files. Datatypes is also missing data stream and progressive rendering support that makes it unsuitable for us with a browser compared to simply embedding the raw codec libraries. Admittedly it's not very Amiga like to have duplicate code, but it's what every other system does and we certainly can't rely on the OS getting 21st century features anymore. BUT what I was thinking was as follows:
- an architecture that makes both the web engine and the JS engine available as separate entities (imagine being able to use Javascript for rexx scripts)
- a web browser that obviously embeds the two
- a light quickviewer suitable for previewing files, that again just embeds the web engine. This would meet your 'datatype' need for use with workbench, DOpus etc.
This is what webkit is architected for, like how it works on the Mac between Safari, the system WebView and the Finder QuickView. It would make it possible to have Electron which in turn is what many popular apps like Slack and Skype are now built with.
This even leaves it open to other browser UIs if you don't like the default one.
As for 68K support, I already mentioned while it would be great to be able to do, the combination of missing dependencies like cairo, lack of recent version of GCC, and the need for 200MB+ RAM would seem to rule it out.