@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.
A quick comment about this. For developers having a WebKit gadget (or similar) would be most useful for embedding the web engine in apps. However, for users a "datatype" would enable quick viewing of HTML files via multi-view. It wouldn't be much of a datatype really. It would basically be the WebKit gadget embedded in a datatype that is set up to recognize HTML/XHTML. And maybe a simple text/rich-text export ability.
NOTE: There are HTML datatypes already, and yes, they cope with loading external images (e.g.,
here. They're just waaaay too dated.
Of course, HTML viewing could also be done simply by opening an actual web browser...
Hans