 |
MultiLineLabel 1.2
Installation & Compatibility |
|
WILDCREST
ASSOCIATES |
[Main Page]
[Sample Applet] [User
Manual] [Javadoc
Documentation]
[Installation & Compatibility]
[License & Contact Information]
Installation
Download the MultiLineLabel zip file and unzip. This will create
a MultiLineLabel folder containing both code and documentation.
To access documentation, use your favorite browser to view the file
MultiLineLabelREADME.html.
To use MultiLineLabel as an ordinary class, since MultiLineLabel.class
is in package com.wildcrest, com\wildcrest\MultiLineLabel.class needs to
be accessible from your class path. You need to do one of the following
things:
-
Modify your classpath to include the MultiLineLabel folder (the top-level
folder of what was unzipped)
-
Modify your classpath to include MultiLineLabel.jar
-
Pick a folder in your current classpath that does not already have a com
folder. Copy MultiLineLabel's com folder into it. For example, this
might be the folder that contains your application, which is always in
your classpath.
-
Pick an existing com folder in your current classpath that does not have
a wildcrest subfolder. Copy the wildcrest subfolder into your existing
com folder
-
If you already have a com\wildcrest folder in your classpath, copy MultiLineLabel.class
into it.
To use MultiLineLabel as an ordinary class in Java applets you should do
one of the following things:
-
Put com\wildcrest\MultiLineLabel.class in the same folder as your applet
(whether on your local system or across the network)
-
In the applet tag, set ARCHIVE="MultiLineLabel.jar" (or "C:\directory\MultiLineLabel.jar"
if it is somewhere else)
-
In the applet tag, set CODEBASE="directory-containing-com\wildcrest\MultiLineLabel.class"
NOTE: Prior to JDK 1.2, you could also use MultiLineLabel
if it was in your classpath. However, with JDK 1.2 Sun has modified
their appletviewer from earlier versions so that it no longer uses your
system classpath. Therefore, for JDK 1.2, one of the applet techniques
above is required. Some regular browsers and appletviewers in other
development environments behave the same as appletviewer above, while others
may honor your system classpath as java does for applications. Following
the instructions above should be work for applets in all cases.
To use MultiLineLabel as a JavaBean, copy MultiLineLabel.jar into the
jar folder appropriate for your visual application builder:
for the JavaSoft BDK BeanBox:
\bdk\jars
for the IBM WebRunner BeanTester:
\webrunner\BeanTools\beantester\beans
for Symantec Visual Cafe:
can place the .jar anywhere (use "Add Component to Library..." command,
then add to desired palette)
for Borland JBuilder: can
place the .jar anywhere (right click on component palette, select "Properties",
then use "Add from Archive")
FYI, the MultiLineLabel.class in com\wildcrest is identical to the MultiLineLabel.class
in the MultiLineLabel.jar archive.
Compatibility and known problems
MultiLineLabel was developed under JDK 1.1.7 on Windows 95. It
has been tested successfully with the following systems:
-
JDK 1.1.4, 1.1.5, 1.1.6, 1.1.7, and 1.2 on Windows 95
-
JDK 1.2 on Windows NT
-
JDK 1.2 on Solaris
-
Netscape Communicator 4.04 (JDK1.1.4) on Windows 95 and Windows NT
-
Microsoft Internet Explorer 4.0 on Windows 95 and Windows NT
-
Microsoft Internet Explorer 4.0 on Macintosh System 8.
MultiLineLabel uses the JDK 1.1 event model and thus will not work under
JDK 1.0.2.
MultiLineLabel has been tested in the follow visual development environments
and bean tools:
-
Symantec Cafe 3.0A on Windows 95 (intermittently fails to refresh background
when bringing up the text property editor, typing any key repaints correctly)
-
JavaSoft BDK 1.0 BeanBox February 98 release
-
IBM WebRunner BeanTester 1.3 on Windows 95
Please report any difficulties with MultiLineLabel on your configurations
by email to products@wildcrest.com. Be sure to include what Java
release, OS, and development environment or bean tools you are using.
Efforts will be made to fix problems in MultiLineLabel, but certain problems
may be outside of its control or not possible for it to detect and/or correct.
© Copyright 1999, Wildcrest Associates (http://www.wildcrest.com)