Re: HTML+ support for eqn & Postscript

• Mail folder: WWW Talk Apr-Jun 1993 Archives
• Next message: Chuck Shotton: "Re: SPaces and Tabs in HTML documents"
• Previous message: Kevin Altis: "Re: SPaces and Tabs in HTML documents"
• In-reply-to: Dave_Raggett: "HTML+ support for eqn & Postscript"
• References: Dave_Raggett: "HTML+ support for eqn & Postscript"

Message-id: <Yg7AIJ8B0KGW9gectj@holmes.parc.xerox.com>
Date: 	Mon, 14 Jun 1993 11:36:05 PDT
Sender: Bill Janssen <janssen@parc.xerox.com>
From: Bill Janssen <janssen@parc.xerox.com>
To: torben@hawaii.edu, janssen@parc.xerox.com,
        Dave_Raggett <dsr@hplb.hpl.hp.com>
Subject: Re: HTML+ support for eqn & Postscript
Cc: www-talk@nxoc01.cern.ch
In-reply-to: <9306140936.AA00563@manuel.hpl.hp.com>
References: <9306140936.AA00563@manuel.hpl.hp.com>

Excerpts from ext.WorldWideWeb: 14-Jun-93 HTML+ support for eqn & Pos..
Dave_Raggett@hplb.hpl.hp (1775)

> Browsers can then be upgraded to display new formats without changing their
> code at all. All you would need is a way of binding the MIME content type
> to the function name for that format, e.g. via X resources or a config file.
> The functions could be implemented as separate programs driven via pipes and
> stdin/stdout or as dynamically linked library modules (Windows DLLs).

Yes, that sounds good.  My favorite way to handle this is to have the
browser create and manage an X sub-window over the area where the inset
is to be displayed, and pass the window ID of the sub-window to the
subprogram which understands the inset format, with the understanding
that that program is to handle all events and refresh on the sub-window,
but the browser gets to handle configuration and window movement.

Bill