<b><i>How to Install and Run Beans</i></b>

-->

How to install and run my "water" Beans

I attach my sources and jar file in one zip. To compile sources you need to have your CLASSPATH point to "some_dir/classes" like this :

CLASSPATH=\some_dir\classes;%CLASSPATH%

Unzip water.zip in \some_dir. You will have three subdirectories :

\some_dir\classes	- compiled classes
\some_dir\jars		- JAR file
\some_dir\src		- Java sources

To rebuild :

cd \some_dir\src\bdktest\water
nmake -f Makefile

To run :

Start BeanBox from beanbox/ directory with run.bat/sh batch file. For everything to work correctly CLASSPATH must be set as in this batch file, introspection depends on CLASSPATH !
```
run.bat/sh :

	if "%OS%" == "Windows_NT" setlocal
	set CLASSPATH=classes
	java sun.beanbox.BeanBoxFrame
```
Use BeanBox "File/LoadJar..." menu to load your BdkWater.jar file
Water beans will appear in BeanBox ToolBox panel. Now you can drop them to the main BeanBox panel and start plumbing !

How to create JAR files from your own packages and how to write Makefile for M$ Nmake

First of all some notes (don't forget to check also how to run BeanBox correctly !) :

BeanBox doesn't like manifest files with "\" - use "/". Like this :

  Name : bdktest/water/Source.class 
  Java-Bean: True

  Name: bdktest/water/Valve.class 
  Java-Bean: True

Leave blank lines between "Name" entries !

To make BeanBox treat your jar file correctly you need to run jar from your "classes" directory - the directory one level above your package top directory. Providing that you store your *.class files in $(CLASSDIR) directory, you need to do something like this in your Makefile :

  cd $(CLASSDIR)
  $(JAR) cfm $(JARFILE) <

Don't put your JAR file in BeanBox default "jars" directory, this will slow down BeanBox at start up. Instead, use your own "jars" directory, for example like in the following directory tree :

\somedir\jars\*.jar
\somedir\src\bdktest\water\*.java
\somedir\classes\bdktest\water\*.class


To load your JAR file use BeanBox "File/LoadJar..." menu.

You don't need to use separate manifest file, just insert it in your
Makefile like in example bellow.

----- Makefile ------------

JAVADIR = c:\jdk1.1\java\bin
JAVAC = $(JAVADIR)\javac -deprecation
JAR = $(JAVADIR)\jar

CLASSDIR = ..\..\..\classes
PKGCLASSDIR = bdktest\water
JARFILE= ..\jars\BdkWater.jar
  
CLASSFILES= \
	$(CLASSDIR)\$(PKGCLASSDIR)\WaterEventObject.class \
  $(CLASSDIR)\$(PKGCLASSDIR)\WaterListener.class \
  $(CLASSDIR)\$(PKGCLASSDIR)\Source.class \
  $(CLASSDIR)\$(PKGCLASSDIR)\Valve.class \
  $(CLASSDIR)\$(PKGCLASSDIR)\Pipe.class \
	$(CLASSDIR)\$(PKGCLASSDIR)\MyValve.class \
	$(CLASSDIR)\$(PKGCLASSDIR)\MyValveOpenEditor.class \
  $(CLASSDIR)\$(PKGCLASSDIR)\MyValveCustomizer.class \
	$(CLASSDIR)\$(PKGCLASSDIR)\MyValveBeanInfo.class


all: $(JARFILE)
#all: $(CLASSFILES)


$(JARFILE): $(CLASSFILES) $(GIFFILES) 
  cd $(CLASSDIR)
  $(JAR) cfm $(JARFILE) <<manifest.tmp $(PKGCLASSDIR)\*.class
Name: bdktest/water/Source.class 
Java-Bean: True

Name: bdktest/water/Valve.class 
Java-Bean: True

Name: bdktest/water/Pipe.class 
Java-Bean: True

Name: bdktest/water/MyValve.class 
Java-Bean: True
<<

.SUFFIXES: .java .class

# Rule for compiling a normal .java file 
{}.java{$(CLASSDIR)\$(PKGCLASSDIR)}.class :
	$(JAVAC) -d $(CLASSDIR) $<


buildAll: 
        @echo Rebuild all ...
        $(JAVAC) -d $(CLASSDIR) *.java


clean: 
    -del $(CLASSFILES)
    -del $(JARFILE)
            
------ end of Makefile ----------