Here are some sketchy installation notes.

Unix Installation:
-----------------

The simplest possible installation for WebEQ merely requires unpacking
the distribution file.  You should be able to look at the examples in
the "latex" and "plist" directories with Netscape 2.0 or greater.
Note that you should be able to open these pages as files, if you
don't have easy access to a web server.  However, in this case, you
won't be able to specify the source input by URL.  

The next level of sophistication is to install the "classes" directory
tree somewhere that is accessible to a your web server.  In this case,
web pages anywhere should be able to reference this location as the
codebase.  For example, if you unpack the distribution file somewhere
that is visible to your web server, you can look at the example files
in Netscape by opening them as locations in the usual fashion.

The third level of sophistication is to set a CLASSPATH environment
variable which points to the "classes" directory before invoking
Netscape.  The CLASSPATH must also contain the location of the
Netscape system classes.  A typical example looks something like:

CLASSPATH=/usr/local/lib/netscape3/:/java/webeq/classes

In this case, you should be able to look at pages
located anywhere, opened either as file or location.  Moreover, the
WebEQ class files should load locally from the directory given in the
CLASSPATH.  However, there are some subtleties that I don't yet
understand, and it seems to work a bit erratically.


Window Installation:
-------------------

The first two levels of WebEQ installation should be the same as under
Unix.  

To get Netscape to use locally installed classes under Win95, it
appears you need to move the contents of the "classes" directory into
the directory where Netscape stores its own class files.  This is
because under Windows, the CLASSPATH appears to be set at the time
Netscape is installed.

Typically this directory is something like

C:\Program Files\Netscape\Navigator\Program\java\classes\bin

Also, I have only gotten this to work for http access and not file
access. However, I think this reflects a bug in the program and not an
inherent limitation.