______________________________________________________________________ SWING, SUPPORTED BY IBM README ______________________________________________________________________ Swing, Supported by IBM (Swing) is supported on the following OS/2 products: OS/2 Warp 4 with FixPak 5 or higher or DBCS equivalent OS/2 Warp Server Version 4 with FixPak 32 or higher or DBCS equivalent OS/2 Warp Server Advanced Version 4 with FixPak 32 or higher or DBCS equivalent OS/2 Warp Server Advanced Version 4 SMP Feature with FixPak 32 or higher or DBCS equivalent OS/2 Warp Server for e-business WorkSpace On-Demand clients and servers OS/2 Warp 3 with FixPak 32 or higher or DBCS equivalent OS/2 Warp Connect with FixPak 32 or higher or DBCS equivalent Note: For information on the Double Byte Character Set (DBCS) FixPak equivalents, see the "FixPaks" section. ______________________________________________________________________ CONTENTS 1.0 OVERVIEW 1.1 FixPaks 2.0 CONTENTS OF THIS RELEASE 3.0 INSTALLING THE SWING TOOLKIT OR THE SWING RUNTIME 3.1 Desktop Method 3.2 OS/2 Command Prompt Method 4.0 RUNNING AN SWING APPLICATION ON OS/2 5.0 USING SWING IN AN IDE 5.1 Compiling and Running Swing Applications without an IDE 6.0 UNINSTALLING EITHER THE SWING TOOLKIT OR THE SWING RUNTIME 6.1 Desktop Method 6.2 OS/2 Command Prompt Method 7.0 ADDITIONAL INFORMATION 8.0 KNOWN LIMITATIONS 9.0 TRADEMARKS 1.0 OVERVIEW ______________________________________________________________________ Swing provides a platform-independent way of developing applications with a consistent look and feel. This release includes the Swing libraries, examples, and API documentation. This release is also known as Java Foundation Classes (JFC) 1.1 with Swing 1.1. For information on fixes by IBM since Swing 1.1 First Customer Ship (FCS) from Sun, see FIXES.LST file located in the directory where you installed Swing. 1.1 FixPaks ______________________________________________________________________ Required FixPak level for DBCS (Japanese, Traditional Chinese, Simplified Chinese, or Korean) Languages: o OS/2 Warp 3 WX03006 o OS/2 Warp 4 FX00505 For information about downloading a particular FixPak, visit the IBM FixPak Web site at: http://ps.software.ibm.com/pbin-usa-ps/getobj.pl?/pdocs-usa /otherservices.html Or see the Developer Kit README located in the [x:\JAVA11] directory. [x:\JAVA11] is the drive and directory where you installed the Developer Kit. By default, JAVA11 is the name of the directory. 2.0 CONTENTS OF THIS RELEASE ______________________________________________________________________ The following files are found in both the Swing Toolkit and the Swing Runtime: README.txt This file README.html Links to interesting files CHANGES.txt Notes on Sun changes since the previous release. FIXES.LST IBM changes since Swing 1.1 FCS from Sun The following files are found only in the Swing Toolkit: SRC.ZIP Swing source code. doc/api/index.html Automatically generated Swing API documentation. doc/api/overview-summary.html No-frame version of the Swing API documentation. examples/SwingSet The comprehensive Swing example. examples/Simple A simple Swing application. examples/SwingApplet A simple Swing applet. examples/SampleTree An example using Swing tree features. examples/Stylepad An example using Swing text features. examples/Notepad Another text example. examples/DBDemos Files to set up databases for use with JDBC. examples/Table JTable/JDBC database connectivity examples. examples/Metalworks Demonstrates the Metal look and feel. examples/FileChooserDemo An example using JFileChooser. The following files are found only in the Swing Runtime: SWING.JAR The Swing classes. WINDOWS.JAR The Windows look and feel. MOTIF.JAR The Motif look and feel. BEANINFO.JAR Beans-related files and classes. SWINGALL.JAR All of the above (useful for IDEs). MULTI.JAR An experimental multiplexing look and feel. CAUTION: These Swing Runtime files do not need to be unzipped. The Java Runtime will extract them as necessary. 3.0 INSTALLING THE SWING TOOLKIT OR THE SWING RUNTIME ____________________________________________________________________ The following sections give you information on installing either the Swing Toolkit or the Swing Runtime. You can install them using either the desktop method or the OS/2 command prompt method. Note: You must install the Swing Runtime to run the examples in the Swing Toolkit. 3.1 Desktop Method __________________________________________________________________ To install using the INSTALL.EXE object, follow these steps: 1. Open the OS/2 System folder. 2. Open the Drives object. 3. Open the drive where the Swing files were extracted. 4. Open the folder where the Swing files were extracted. 5. Double-click the INSTALL.EXE object to start the installation program. The INSTALL.EXE command brings up a GUI with eleven buttons specifying the languages you can install the program in. Click the language you prefer and the installation program will lead you through the installation steps. 3.2 OS/2 Command Prompt Method __________________________________________________________________ To start installation, make sure that you are in the directory where the Swing files were extracted. At the OS/2 command prompt, type: INSTALL The install command brings up a GUI with eleven buttons specifying the languages you can install the program in. Click the language you prefer and the installation program leads you through the installation steps. 4.0 RUNNING A SWING APPLICATION ON OS/2 ____________________________________________________________________ Installing the Swing Runtime modifies the CLASSPATH variable in the CONFIG.SYS file to include the SWINGALL.JAR file that contains all the Swing class files. Installation also sets the environment variable, SWING_HOME, in CONFIG.SYS file to the drive and directory where the Swing Runtime is installed. To run the examples provided in the Swing Toolkit, run the RUNNIT.CMD file located in the following example directory, [x:\JAVA11]\swing\examples [x:\JAVA11] is the drive where you installed the Developer Kit and Swing files. 5.0 USING SWING IN AN IDE ____________________________________________________________________ To use Swing components in an Integrated Development Environment (IDE), such as Borland's JBuilder, Symantec's Cafe, Sun's JavaWorkshop, or IBM's VisualAge, you must import the SWINGALL.JAR file into the IDE. The SWINGALL.JAR file includes the base Swing implementation, several look and feel attributes (Metal, Windows, and Motif), and information that makes the Swing components work as beans. The SWINGALL.JAR file is necessary only if you plan to use Swing in one of the IDEs, or if you would like to include one "all inclusive" JAR file in your CLASSPATH or application. 5.1 Compiling and Running Swing Applications without an IDE __________________________________________________________________ This section tells you how to compile and run your own programs. Note: You do not need to read this section to be able to run the examples included in this release, because they are pre-compiled and provide RUNNIT.CMD files. When you compile or run a Swing application, make sure that the CLASSPATH contains the SWINGALL.JAR file or the SWING.JAR file and the JAR files for the platform-specific look and feel you are using. If you are only using the Java look and feel (Metal), then you do not need an additional JAR file because Metal is included in SWING.JAR. The installation program will modify the CLASSPATH for you to include the SWINGALL.JAR file. If you use the "-classpath" compiler option, be sure to include the correct Swing JAR file(s), the appropriate Developer Kit CLASSES.ZIP file, and the directory that the source code is in. Examples on compiling or running a Swing application are as follows: To compile a Swing application: [x:\JAVA11]\bin\javac -deprecation -classpath .;x:\JAVA11\lib\ classes.zip;x:\JAVA11\swing\swing.jar MySwingProgram.java [x:\JAVA11] is the drive where you installed the Developer Kit and Swing files. To run a Swing application: [x:\JAVA11]\bin\java -classpath .;x:\JAVA11\lib\ classes.zip;x:\JAVA11\swing\swing.jar;x:\JAVA11\ swing\windows.jar MySwingProgram [x:\JAVA11] is the drive where you installed the Developer Kit and Swing files. 6.0 UNINSTALLING THE SWING TOOLKIT OR THE SWING RUNTIME ____________________________________________________________________ You can uninstall the Swing Toolkit or the Swing Runtime using the following methods: 6.1 Desktop Method __________________________________________________________________ To uninstall using the Remove the Developer Kit object, follow these steps: 1. Open the OS/2 System folder. 2. Open the System Setup folder. (If you are uninstalling on OS/2 Warp 4, open the Install/Remove folder.) 3. Open the Uninstall Features folder. 4. Select the Remove the Developer Kit for OS/2 object to start the uninstall program. 6.2 OS/2 Command Prompt Method ____________________________________________________________________ To start uninstalling, make sure that you are either in the directory where the Developer Kit files were extracted or in the [x:\JAVA11]\UNINSTAL directory ([x:\JAVA11] is the drive where you installed the Developer Kit). At an OS/2 command prompt, type: UNINSTAL The uninstall program leads you through the uninstallation process. Only files and directories created by the installation process are removed. 7.0 ADDITIONAL INFORMATION ____________________________________________________________________ The following files or Web sites will give you information on the use of Swing: o The License (LICENSE.TXT) file. This file is located in the directory where you installed Swing. o Sun's Swing Web site, The Swing Connection. This Web site offers information that developers ask for most. The content is based on information from the designers of Swing. http://java.sun.com/products/jfc/tsc/ o The Java Tutorial Web site. The Java Tutorial now gives information about Swing. To view the Graphical User Interface (GUI) section of the Java Tutorial, visit this Web site: http://java.sun.com/docs/books/tutorial/uiswing 8.0 KNOWN LIMITATIONS ____________________________________________________________________ In the Input Method Editor (IME) for Korean, the Hangul characters will not be viewable while they are being created. However, the completed character is viewable after it is created. 9.0 TRADEMARKS ____________________________________________________________________ The following terms are trademarks of International Business Machines Corporation in the U.S., or other countries, or both: IBM OS/2 Java is a trademark of Sun Microsystems, Inc. in the U.S. and other countries. The Java technology is owned and exclusively licensed by Sun Microsystems, Inc. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. (c) Copyright IBM Corporation 1998, All rights reserved. ______________________________________________________________________ END-OF-README-FILE ______________________________________________________________________