Lava - The Java GUI Builder

Installation Guide

To run Lava you need :

Step One : Install JDK

The first step is to install JDK 1.2 if you have not already done so. The JDK can be downloaded from the Javasoft Homepage if need be. Verify that the JDK is correctly installed by issuing the command :

java -version

You should receive a version number that corresponds to JDK 1.2. NB. It is very important that you install the correct version of the JDK as version other than 1.2 can not be relied upon to correctly run Lava 1.4. Verify that your classpath is set up correctly by running some of the example programs included with the JDK. Once you are sure about the integrity of your JDK installation you are ready to install Lava.

Step Two : Install Lava

The Lava distribution is supplied in a compressed format. To install Lava you will need to decompress the files from the distribution archive into a directory on your computer. To decompress the archive :

  1. Create a new directory to store the files in e.g. c:\lava. This directory can be anywhere you wish but for the sake of simplicity this guide assumes you have installed Lava into c:\lava.
  2. Using an appropriate archive manager that can deal with long file names, e.g. WinZip, open the Lava distribution archive.
  3. Ensure that you check options relating to retaining the directory structure of the archive. Failure to do this will result in all files being stored in the same directory.
  4. Complete the operation by extracting the files to the newly created directory.
  5. Verify that the files are present by looking in the new directory.

You now need to ensure that the Lava class files are included in the CLASSPATH environment variable. The class files are stored in the file lava.jar in the installation directory. You do not need to decompress the lava.jar file and can simply add it to the classpath by issuing a platform dependant command similar to :

set CLASSPATH=%CLASSPATH%;c:\lava\lava.jar

You can check that this worked by issuing platform dependant command similar to the one below and checking for the presence of the c:\lava\lava.jar entry in the response.

echo %CLASSPATH%

Step Three : Run Lava

Once installation has been accomplished, you can run Lava by first changing to the installation directory. You should now issue the command :

java uk.co.demon.hnet.lava.Lava

If installation was correctly performed, this should result in the Lava splash screen appearing while Lava analyses any registered JavaBeans. The main Lava GUI will appear shortly after this happens. Any exceptions of the form java.lang.ClassNotFoundException probably mean that your CLASSPATH settings are incorrect - go back to step two.

Included in the release are some batch files that are examples of how to set up Lava so you can run it from anywhere. By setting the lava.home environment variable and including the lava.jar file in your CLASSPATH, you can run Lava from anywhere without changing to the Lava directory. lava.bat is an example of how this can be done. Note the case involved in the command line as this is important.

Other command line operations for Lava are shown below :

Lava 1.4B by Dan Page of hairNET - [http://www.hnet.demon.co.uk]. Copyright 1996-1998 All rights reserved Lava Version 1.4B Lava Home OS Name Windows 95 OS Version 4.0 Java Version 1.1.6 AWT Version 45.3 USAGE : java [-Dlava.home=<lavaHome>] uk.co.demon.hnet.lava.Lava [<option>..] -file <file> Load <file> into Lava on startup. -component <component> Make a new component on startup, bypassing the dialog. -ini <file> Use <file> instead of lava.ini. -? Print this help screen.

This software is provided by the author "As is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.