CSE logo University of Washington Department of Computer Science & Engineering
 CSE 413 Au 02 - Software
  CSE Home   About Us    Search    Contact Info 

CSE 413
 Home page
Administration
 Syllabus
 Grading
 Calendar
 Accommodations
Classwork
 Lectures
 Homework
 Exams
 Software
 Other Links
Email list
 Info
    Software Tools

The software packages for this class are installed in the Math Sciences Computing Center . The download files provided here are only needed if you are doing the course work on some other system.

DrScheme

The DrScheme interpreter is available from the Scheme website for free download. DrScheme runs on Windows (95 and up), Mac OS, or Unix running the X Window System. DrScheme is useful given at least 32 MB of RAM. Installing DrScheme requires roughly 30 MB of disk space.

There is a local copy of the Revised 5 Report on the Algorithmic Language Scheme available from this site.

Graphviz

We will be using this graphics visualization package from ATT Research to draw some of the data structures that we are studying. The Graphviz information page is http://www.research.att.com/sw/tools/graphviz/.

A local copy of the Windows installer ( graphviz-1.8.10.exe) is available. Installers for other systems (and the source files) can be found starting at the ATT page linked above.

The only program in the package that we actually need is "dot".

Postscript Viewer

The Graphviz program "dot" generates output in Postscript format. There are many viewers available for Postscript; you will need one for this class. I use GSview with Ghostscript on my Windows machines. The home page for GSview is http://www.cs.wisc.edu/~ghost/gsview/ where you will find the latest revision information for both GSview and Ghostscript.

Local copies of the Windows installers for Ghostscript (gs704w32.exe) and GSview (gsv43w32.exe) are available. Installers for other systems (and the source files) can be found starting at the GSview page linked above.

Install Ghostscript first, then GSview.

Java

For the last portion of the course, you'll need the following software:

  1. The Java SDK from Sun
  2. A programmer's editor like jEdit

The code you turn in should only rely on the standard Sun Java libraries. Your code should not rely on "wizards", special libraries that might be provided with your environment, or other special libraries from textbooks or the Internet. The programs that you turn in will be compiled and run using the setup described here.

Java SDK

You must first install the Java 2 Standard Edition Software Development Kit (SDK) from Sun Microsystems. Note that you need the development kit (SDK), not the Java Runtime Environment (JRE). You can use J2SE version 1.3.1 or 1.4.

Download the installer from the Sun web pages (java.sun.com/j2se/). The Java 2 SDK can be installed and run on Windows 95/98/NT/W2000/XP and most Unix variants, including Linux and Sun/Solaris. Java 2 version 1.3 is included with Mac OS X, so you should be able to run the course software on OS X without having to install Java 2 first. Java 2 is not available for the classic Mac OS (OS 9 and earlier).

The distribution is big, roughly 36MB, so if you're connecting by slow modem, allow plenty of time.

To install, double-click on the installer program, and then follow the instructions.

Some notes:

  • Install Java in a directory where the pathname has NO spaces. For example, I install all my application programs in directories called C:\apps\appname. On my home systems, Java 1.3.1 is installed in C:\apps\jdk131. Don't use C:\Program Files\appname. The space in the pathname can cause weird errors that are difficult to track down.
  • Be sure you install the Java Development Kit (JDK). There is a smaller package called the Java Runtime Environment (JRE), which is a subset of the JDK that includes files needed to run, but not create, Java programs. The JRE is not adequate for our purposes -- be sure to get the JDK.
  • A large part of the JDK distribution is source code. You don't need to install the source code, although it is sometimes interesting to read to see how the Sun programmers have implemented the libraries that we are using. You don't need the native library header files. You can install the demos if you like. (You'll eventually get the option of what you want to install when you run the installer program that you downloaded from Sun.)

Java SDK documentation

Sun provides excellent documentation for all the class libraries that are part of the Java platform. I strongly recommend that you download and install the documentation. Unfortunately, the download file is also very large (31MB), but it is very useful to have the documentation at your finger tips while you are programming. The documentation is available from the same place you downloaded the JDK (java.sun.com/j2se/1.3/download.html#docs) or (java.sun.com/j2se/1.4/download.html#docs), in the form of a large zip file. Download it, and unzip it into the same directory where you installed Java itself. For example, I will unzip the documentation for J2SE 1.4.0 into C:\apps\jdk140. This will give you all the html files that describe the Java libraries. If you add a link in your browser bookmarks, then you can get the documentation for any library method with just a few clicks of the mouse.

jEdit

jEdit is a programmer's editor. It is an open source project, written in Java, and freely available over the web at jedit.org. You don't need to use it if you have some other editor that you prefer.

  1. Go to the jEdit download page and download the appropriate version of the latest stable release. You probably will want the Java-based installer.
  2. To install jEdit, simply double-click on the JAR file you downloaded; the installer may start automatically.
  3. If it doesn't, then you will need to open an MS-DOS prompt (Start->Programs->MS-DOS Prompt) and enter the following commands:
    • cd directory where you downloaded the JAR file
    • java -jar filename.jar
  4. For example, if you downloaded jedit40install.jar into C:\Downloads, you would enter:
    • cd C:\Downloads
    • java -jar jedit40install.jar
  5. If for whatever reason you want to start the installer in text-only mode, specify text as the last parameter on the command line. In text only mode, the installer will not display its GUI, and instead it will ask questions in the MS-DOS prompt.
  6. If you encounter a problem while installing jEdit, take a look at The jEdit FAQ
  7. Take a look at this tutorial, which shows you how to setup jEdit with the compiler and the JSwat debugger.

jEdit plugins

One of the nice things about jEdit is that it has a plug-in architecture and so there are quite a few useful utility modules that have been written to work with jEdit. Use the plug-in manager within jEdit to install them. The plugins that I use include:

  • Buffer Tabs
  • Character Map
  • Common Controls
  • Console
  • Error List
  • Java Browser
  • JCompiler
  • JDiff
  • JSwat
  • Whitespace

Use menu item Utilities - Global Options - Docking to set quick access tabs for the various plugins. Use Utilities - Global Options - Toolbar to create one-click buttons to compile and run the current buffer. The gif image files that I used for these buttons are JavaCup24.gif and Play24.gif. You can right-click and save the image files for your use, or use any other images that you like.

You're done!

The course software should be installed at this point. If you'd like, you can create shortcuts to the documentation and jEdit program files and put them in a more convenient place like the desktop or the QuickLaunch bar. Be sure to create shortcuts; don't move the files themselves. If you move them, things are likely to break.

CSE logo Department of Computer Science & Engineering
University of Washington
Box 352350
Seattle, WA  98195-2350
(206) 543-1695 voice, (206) 543-2969 FAX
[comments to webmaster]