Jar Files
The supplied jar files for the WinJ are called the pvName.jar. Every jar file is self-contained and can be used independently from other jars. The jar files can be found in the pvWinJ package directory. To use these files, simply install them into the development environment of your choice and begin accessing them from there.
Class Files
The installation of the pvWinJ classes is very straight forward. The class files need
to be placed in the directory named pvWinJ. This pvWinJ directory should be created above
any directory that is part of the CLASSPATH system environment variable. Samples and
applications which reference pvWinJ can then load and run.
For example:
1. Create c:\pvApps\pvBeans11\pvWinJ.
2. Copy all classes of pvWinJ package under that directory. (PV*.class and C*.class)
3. Edit autoexec.bat file: "SET CLASSPATH=%CLASSPATH%;C:\pvApps\pvBeans11".
4. Reboot computer.
5. Run samples or use classes in your development environment.
At this point the pvWinJ package can be accessed by the Java VM.
The sample applications import the pvWinJ package, so this package is assumed to exist as
a subdirectory somewhere in the CLASSPATH.
When posting your Applets on a Web site, the pvWinJ package needs to be placed as a
subdirectory of the application so that the package can be located by the Java VM of the
user's browser.
Dependencies Between Classes
This section can be helpful for distribution of product or custom installation. The
information about run time classes can allow to build one final
run-time-minimum-size-jar-file with custom java classes and to reduce number of custom
classes supplied with an application.
All pvWinJ classes can be subdivided on two major groups: the text-edit and button.
1. Run time classes:
a. The first group depends on the following shared classes: PVEdit.class,
CBorder7.class, CBorderSet.class, CShadow.class, CLED.class, COdometer.class. The PVEdit
requires only these six classes.
Note: If the Odometer, Shadow, or LED styles are not used, then the corresponding classes
can be also not installed to run an applet.
The PVDate, PVMask, and PVStaticText besides all "PVEdit classes" requires
another extra class with a corresponding name.
b. The second group depends on the following shared classes:
PVButton.class, CBorder7.class, and CShadow5.class. The PVButton requires only these three
classes.
The PVImageButton, PVRoundButton besides all "PVButton classes" requires another
extra class with a corresponding name.
For example, to use the PVDate and PVImageButton components the following classes are
required: PVEdit.class, PVDate.class, PVButton.class, PVImageButton.class, CBorder7.class,
CBorderSet.class, CShadow.class, CLED.class, COdometer.class.
2. Design time classes:
Besides corresponding run time classes discussed above, there are used the BeanInfo and
Customizer classes for a particular component and the PVEditColor class.
a. The list of additional classes for the PVEdit: PVEditBeanInfo.class,
PVEditCustomizer*.class(es), PVEditColor*.class(es).
The PVDate, PVMask, PVStaticText besides all PVEdit*.class use two extra classes:
PVNameBeanInfo.class and PVNameCustomizer.class. (where Name is Date, Mask, etc.)
For example, the PVDate uses PVEditBeanInfo.class, PVEditCustomizer*.class(es),
PVDateBeanInfo.class, PVDateCustomizer.class and PVEditColor*.class(es).
b. The list of additional classes for the PVButton:
PVButtonBeanInfo.class, PVButtonCustomizer*.class(es), and PVEditColor*.class(es).
The PVRoundButton besides all PVButton*.class uses PVRound*.class. The PVImageButton uses
PVButton*.class and PVImageButton*.class.