Re: hyper-TeX and standards for client-side extensions

• Mail folder: WWW Talk Jan 94-present
• Next message: Markus Stumpf: "patch for NCSA httpd-1.1 to allow http-gatewaying"
• Previous message: burchard@geom.umn.edu: "Re: hyper-TeX and standards for client-side extensions"
• In-reply-to: burchard@geom.umn.edu: "Re: hyper-TeX and standards for client-side extensions"
• References: burchard@geom.umn.edu: "Re: hyper-TeX and standards for client-side extensions"

Message-id: <chFk_l0B0KGWMYkuRP@holmes.parc.xerox.com>
Date: 	Wed, 26 Jan 1994 15:54:25 PST
Sender: Bill Janssen <janssen@parc.xerox.com>
From: Bill Janssen <janssen@parc.xerox.com>
To: burchard@geom.umn.edu
Subject: Re: hyper-TeX and standards for client-side extensions
Cc: www-talk@www0.cern.ch
In-reply-to: <9401262228.AA20862@mobius.geom.umn.edu>
References: <9401262228.AA20862@mobius.geom.umn.edu>
Content-Length: 797

Hyper-DVI, then.  Sure, should work just fine.  I was thinking that
Hyper-Postscript would take about the same amount of work, and probably
provide a bigger payback, in terms of versatility.  In fact, Paul
Kranenburg at Erasmus University in the Netherlands just sent me a
version that only needs two changes:  first, the links it supports are
Sun answerbook links, rather than Internet URL's (trivial change); and
second, it's implemented as an XView widget rather than an Xt widget
(sort of a big change).  The links are just comments in the Postscript
which indicate a document, and a sensitive rectangle on the page.  The
widget ``signals'' the specified document when the user clicks on the
specified region.  Easy.  In fact, dvips could generate this format from
Hyper-DVI, I imagine.

Bill