Tgif Home
----
About Tgif
Current Release & Download
FAQ
Copyright & Redistribution Info
A Screendump of Tgif
Release History
Tools That Tgif Uses
Tools That Work with Tgif
Author of Tgif
Miscellaneous Info
----
 
Return to Tgif's Home Page
William Chia-Wei Cheng
(bill.cheng@acm.org)
 

Tgif - Configure Tgif to Work with Netscape

(Polish version of this page), (Czech version of this page)
 
MIME
  • Web Browsers, such as NCSA Mosaic and NetScape, support the launching of external viewers such as tgif. Often, they use MIME (Multipurpose Internet Mail Extentions, RFC1521 (187,425 bytes)) configuration files to decide what to launch.
  • Tgif files have been proposed to use the application MIME type and x-tgif MIME subtype. The HTTP server on http://bourbon.usc.edu:8001 sends tgif files as the application/x-tgif MIME type.
  • If you would like to launch tgif when an URL specifies a tgif file, please update your MIME configuration files as indicated below.
  • After you have update your MIME configuration files, you can visit Tgif's Hyper-Structured-Graphics Home Page from NCSA Mosaic or Netscape by clicking on the URL here (you probably have to restart the Web Browser for the MIME configuration files to take effect).

    If the MIME configuration files are not setup properly, you would probably get a dialogbox asking you where you want to put the file referenced in the above URL.


MIME Configuration Files
~/.mime.types
  • Add the following line to the .mime.types in your home directory:

        application/x-tgif  obj
~/.mailcap
  • Add the following line to the .mailcap in your home directory:

        application/x-tgif; tgif %s
Test the MIME Configuration Files
  • Tgif's Hyper-Structured-Graphics Home Page -- but beware of the following idiosyncrasy...
  • When a Web Browser such as NCSA Mosaic or Netscape launchs an external viewer to view an URL (such as the one above), it often fetches the URL and save it in a temporary directory (such as /tmp). Normally, these URL's point to image files which do not contain any links. Therefore, when the above URL is saved in /tmp, it presents a unique problem. URL's specified using the relative naming method within that file will be resolved by the Web Browser to files in the /tmp directory which obviously do not exist.
  • The temporary solution (as implemented in the above URL) is to put a self-referencing link in the URL to point to itself using a full URL name. Therefore, when you visit the above URL, the first thing to do is to click on the self-referencing link. Please note that this only works if you are running version 2.16 or above tgif.