ArcWeb's HTML Extensions

• Inlined images may be virtually any type which ChangeFSI autorecognises, including RISC OS sprites (although not 'deep' sprites, yet)
• Since RISC OS sprite areas may contain multiple sprites, I have extended the same principle used for documents, to images. Hence, something like <img src="myfile#myiconbar"> will retrieve the sprite called myiconbar from myfile which resides in the same directory as the document that contains it. Furthermore, omitting the filename will force a look up in the Wimp common sprite pool, so <img src="#switcher"> will get you the icon.
• URLs may reference files on the local machine. These are recognised by the syntax: local://filing-system/file-from-$. The filing system includes the media specifier, so ADFS::HardDisc4 is an example of a valid filing system. The rest of the filename is given from and including the root. Filing systems without media specifiers may be used by omitting that part of the FS name (see the example with resources: below. In the path name, all / and . characters are transposed to make it look more like a conventional URL.
• local: URLs may point to applications, in which case following them will launch the application. eg. <a href="local://resources:/$/Apps/!Help"> will open an anchor which will launch Acorn's !Help application. However, for your own protection, this will NOT happen unless the page containing the link to an application was also loaded from a local: page.
• Some of the extensions proposed by Netscape Communications Corp. have had support added for them as well, including background images, colour changing, id attribute for any tag.
• Some of the HTML 3.2 "Wilbur" extensions have been added, such as referencing certain colours by name.
• ArcWeb has support for finger URLs as well. Even Netscape 2 doesn't have these yet!