For the curious or the expert,
we describe below how we made the Applet and how to rebuild it (in case
you want to add your own changes). If you don't care about that now
and do not mind if clicking the "print", "read" and "write" buttons produces
nothing, then skip directly to the Applet. It has self contained
Bookmark that link to bypass this "readme".
You can always come back for the information once you decide you wish you could print or save your work.
Finally, we suggest that you print the documentation out and keep it next to you the first time you go through that Applet. The Applet is self-documented, so click on the PDF or PostScript version to make hardcopy.
For the studious, read on below.
For the adventurous, jump right in
Currently, Internet Explorer 4.0 is the next best option if you do not have access to Navigator 4.06. With IE 4.0, the Applet printing button fails, but the work around below will allow you to get a printed picture of the Applet with your results graphed.
Normally, if you are reading this, you already have the applet.
If you want to tell someone else how to get it the simplest way
is to download the gzipped tar file. You can then use
gunzip -c S.tar.gz |tar -xovf -
or the equivalent for your operating system to unpack the tar file. Free versions of gzip and tar are available. See the GNU project web page and its links.
The authors will maintain a copy of the applet with current (August, 1998) and subsequent updates for an undetermined length of time. Send mail to the authors for the dowload site information.
Once you have a copy of the Applet, you are free to change it and redistribute it in accordance with the Gnu Public License.
To build the applet from source you need a Java Development Kit from Sun Microsystems at http://java.sun.com/, or Linux users may prefer the most recent from the Java-Linux porting project at http://www.blackdown.org or you may find other related development kits.
We have used both JDK1.1.3 and JDK1.1.5. You will also need JavaCC (Java Compiler compiler) from http://www.suntest.com/JavaCC to build our parser generator written using JJtree. JJtree is part of the JavaCC distribution. Note we used JavaCC version 0.7 which is compatible with JDK1.0 so that older browsers would be functional, but the newer 0.8 version also works it just produces code that requires JDK1.1. A makefile that works in Unix/Linux is distributed in the javasrc directory. You will have to modify the first few lines to point to the various directories on your system. If you are compiling under a different operating system, the Makefile should still indicate the operations needed to build the system. Under Unix/Linux typing make will build all the java class files.
To build the documentation, you will need Latex2e, the makeidx, graphicx packages (these normally come with the tetex distribution all available at the Comprehensive Tex Archive Network sites, see for example http://www.cdrom.com/pub/tex/ctan/CTAN.sites. You will also need the latex2html translator and the associated html package from http://cbl.leeds.ac.uk/nikos/tex2html/doc/latex2html/latex2html.html. If you want to make an Adobe PDF file you will need a copy of Adobe Acrobat. PDF files look best with PostScript Type 1 fonts available at ftp://ftp.ams.org. There is a makefile in the docsrc directory that will go through all the steps necessary to build the pdf, postscript, and html files.
Under Unix/Linux, typing make in the Schroedinger directory (once the Makefile in javasrc has been modified as mentioned above) will produce the entire distribtution. Typing make clean will get rid of multiple copies of some files, and typing make veryclean will keep only those files necessary to rebuild the distribution from scratch.
Additional documentation on the source code is available in javadoc format.
We also provide the applet in a full JDK1.1 version using the Java Foundation Classes light weight components (i.e. the swing set). This version is available in the swing subdirectory and includes a customizable Examples menu (by changing the Examples.properties file), customized look and feel, as well as some built in help. In addition it uses the Java internationalization, so that all the labels and examples etc. can be changed to other languages by including localized versions of the Labels.properties and Examples.properties files (That is adding Labels_it.properties and Examples_it.properties files will cause these files to be used if your locale is set to use Italian.)
You can try out this swing version by pointing your browser at the test.html file in the swing subdirectory. You can also run it as an application by typing
java Seq2Swingwhile in the swing subdirectory.