[ previous section | contents | next section ]

Installation of the devPad environment

Here's how to install the devPad environment and runtime classes:

Copy the 'dpenv.zip' or 'dpenv.tar.gz' file from the devPad documentation directory to the Java home directory, using the original name. The name of the Java home directory will vary depending on the operating system you are using. Some possibilities are:
```
  /java
  /jdk1.1/java
  \javaos2
  \jdk1.1\java
```
It will contain directories such as 'bin' and 'lib'.
[Note: if your Java home directory is on a CD-ROM, or otherwise inaccessible, you'll need to choose a different directory and set up a CLASSPATH environment variable that points to it. Consult your Java toolkit documentation for details on how to do this. You'll also need to set the devPad home directory -- see below.]
With the Java home directory as your current directory, unpack the package, following the instructions in "Unpacking the devPad package" above.
This should add the .zip file for the devPad environment classes (devPad.zip) and the environment's preferences and runtime documentation files (devPad.icons/*, devPad.properties, ISOlat1.ent and nodoc.html) to the Java 'lib' directory.
In addition, some sample scripts should have been added to the Java 'bin' directory:
```
  devPad.cmd -- the devPad environment command in Rexx
  dp.cmd      -- shorter name for devPad.cmd
```
The .cmd files are simple batch scripts for making it easier to use the compiler. You don't have to use these, but they save some typing. They should require little modification to run under your platform.
Check that the names are correct in the 'lib' directory: there should be a directory called 'devPad.icons' and files called 'devPad.properties', 'ISOlat1.ent' and 'nodoc.html'; if the name is all in lowercase, or the word 'icons', 'properties' or 'html' is truncated, the package has not been unpacked correctly (see Unpacking the devPad package).
For Java to be able to find the devPad classes, you must update the CLASSPATH environment variable by adding the full path and name of the devPad.zip file to the CLASSPATH setting. There will often already be a CLASSPATH variable set, including a path to the standard Java classes.zip file. Specify or add the full path (disk, directories, and file specification) for devPad.zip, making sure that the case of every letter is exactly right (Java is very case-sensitive). For example, the full path might be something like:
```
  e:\javaos2\lib\devPad.zip
```
The procedure for setting the CLASSPATH variable depends on your operating system (and there may be more than one way). Here are some examples:
- In OS/2 or Windows, use a SET CLASSPATH= command in CONFIG.SYS (for OS/2) or in AUTOEXEC.BAT (for Windows) and re-boot after changing. In both cases the command syntax is the same, and might look like this:
```
  set classpath=.;f:\javaos2\lib\devPad.zip
```
  In this example, the first segment of the value (before the semicolon) lets classes in the current directory be found, and the second segment includes the classes needed by devPad. Both environments normally include the standard Java classes automatically.
- For Unix (Korn shell or Bourne shell), use:
```
  CLASSPATH=:$CLASSPATH
  export CLASSPATH
```
  and changes for re-boot or opening of a new window should be placed in your .login (Bourne) or .profile (Korn) file
- For Unix (C shell), use:
```
  setenv CLASSPATH :$CLASSPATH
```
  and changes for re-boot or opening of a new window should be placed in your .cshrc file
If you are unsure of how to do this, check the documentation you have for installing the Java toolkit.

Checking your installation is correct

To check installation, change directory to the devPad documentation directory, then (being very careful to get the case of letters correct):

Enter the command
```
  java devPad.devPadMain Welcome.pad
```
This should starts the devPad environment, and open the Welcome workspace.

With the sample scripts provided (devPad.cmd), or the equivalent in the scripting language of your choice, the steps above can be combined into a simple single command:

  devPad Welcome.pad

This package also includes a trivial 'dp.cmd' file that simply passes on its arguments to devPad; 'dp' is just a shorter name that saves keystrokes, so for the last example you could type:

  dp Welcome.pad

Note that scripts may be case-sensitive; unless running the OS/2 Rexx script, you will probably have to spell the name of the program exactly as it appears in the filename.

The devPad Home directory

If you need to put the devPad.properties and runtime documentation files into a directory other than the 'lib' directory below the Java home directory, then you can set an alternative directory path that devPad will use to find the messages file.

This alternative directory is called the devPad home directory and may be set using the -D option on the java command that invokes the devPad environment. For example (perhaps for an OS/2 or Windows system):

  java -Ddevpad.home=f:\dphome devPad.devPadMain Welcome.pad

which sets the directory path 'f:\dphome' as the devPad home directory. With this setting, devPad would look for the properties file as:

  f:\dphome\lib\devPad.properties

In other words, devPad expects its properties and runtime documentation files to be in the 'lib' directory below the devPad home directory, and the default devPad home directory is the Java home directory.

If you are using the devPad.cmd on OS/2 to invoke the compiler, then this -D option will be set up automatically if the path is set as the value of an environment variable called DEVPAD_HOME.

[ previous section | contents | next section ]