Re: HTML+ support for eqn & PostscriptBill Janssen <firstname.lastname@example.org>
Date: Mon, 14 Jun 1993 11:36:05 PDT
Sender: Bill Janssen <email@example.com>
From: Bill Janssen <firstname.lastname@example.org>
To: email@example.com, firstname.lastname@example.org,
Subject: Re: HTML+ support for eqn & Postscript
Excerpts from ext.WorldWideWeb: 14-Jun-93 HTML+ support for eqn & Pos..
> 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.