You can write a translator that imports a foreign file format to create a TScrapItemOn<MGraphic>. When this translator is installed, WebRunner Sample automatically uses it for any in-line images of that type. A JPEG or TIFF translator would be very useful.
Another translator you can write is one that translates between a foreign file format and a TModelScrapItem holding an embedded document component. Both the GIF and XBM translators show how to support this, but you can take it one step further by adding a translator to go from a video or audio format like MPEG or AIFF to produce a document component. Once this translator is globally installed, any link that leads to a document of that type brings up your component, embedded in the WebRunner Sample.
Supporting varying
media types
Writing new translators is the easiest way to extend the WebRunner Sample because you can do it without touching a line of code in the program itself. There are two routes you can choose from. Reusing link and image document components
You can reuse the link and graphic document components in other programs
in which you want to display an atomic graphic or a reference to an
-internet resource. Implementing additional HTML protocol
WebRunner Sample does not implement the entire HTML protocol. For example, you might choose to support forms that provide interactive access to World Wide Web services or tables that provide improved formatting for multi-column data. Other common
browser features
Looking at a production-quality WWW viewer such as Mosaic or Netscape` might give you ideas for new features. For example, while a link is being followed, both these viewers have a button that can be pressed to cancel the operation. Other desirable features include history lists of the last few pages or a dialog box that allows users to enter a link to follow.
[Contents]
[Previous]
[Next]
Click the icon to mail questions or corrections about this material to Taligent personnel.
Generated with WebMaker