> ### Welcome to The Swing 1.1 Release! (Officially known as "JFC 1.1") This file has three parts: Links to Important Documents How to Find and Submit Bug Reports How to Give Feedback #### Links to Important Documents Before you use this release, please read these two documents:
> `README.txt` | Describes the files in this release and how to get started using this release.
> `LICENSE.txt` | Legal stuff.
> If you used Swing 1.1 Beta 3 you'll probably be interested in this file:
> `CHANGES.txt` | Changes we've made since the Swing 1.1 Beta 3 release.
> From there, you might want to visit these places:
> The Swing Connection | The Swing team's Web site. Contains everything from instructions on running applets to previews of upcoming functionality to technical discussions. This is the one-stop source for Swing information.
> Creating a GUI with Swing | Part of the online version of The Java Tutorial. Has step-by-step information on using Swing, including a guide to getting started with Swing and discussions (with full examples) of using many Swing classes.
> While you're using the Swing 1.1 release, you'll probably need these documents:
> SwingSet README | Describes how to run the SwingSet example, which demonstrates many of the features in Swing and can run as either an applet or as an application. Includes instructions for running SwingSet in the Applet Viewer, Internet Explorer, and Netscape Communicator.
> API documentation (NO FRAMES) | Generated by the javadoc tool from comments in the Swing source code.
- 3. #### How to Find and Submit Bug Reports To get e-mail listing all known Swing bugs, please try our buglist autoresponder. You'll get a single reply by writing to the following address: swing-buglist-responder@qwerty.eng.sun.com The Swing Connection's 911 page lists workarounds for some of Swing's most annoying bugs: Call 911 The Java Developer Connection's bug page lets you search our bug database, giving you access to the complete text of bug reports: Bug Parade To encourage us to fix a particular bug very soon, please vote for the bug. You can do so by viewing the bug report in the Java Developer Connection, and then clicking the Vote button in the left margin. If you need to file a bug, please submit it through java.sun.com: Report a Bug or Request a Feature When asked for the product, choose the version of the JDK that you're using. For the subcategory, select classes_swing. If the bug is holding up your development, please also send e-mail to the Swing team (swing-feedback@java.sun.com). Tell us what the bug number is and what you need to be able to continue your development. When you file a bug report, please include the following information: A program or code snippet that shows the problem. The platform you're using. A backtrace, if appropriate. This will tell us what the program is doing when the bug occurs. To generate a backtrace, do this: Go to the shell window in which you entered the 'java' command. Make sure it has the keyboard focus and that the interpreter (`java` command) isn't a background process. Enter the appropriate character:
     Control-\ | (Solaris)
     Control-Break | (Win 95/NT)
You should see a bunch of text in the window. Please put a copy of it into your bug report. #### How to Give Feedback We'd love to hear about what you're doing with Swing. We'd also like to hear your ideas for improvements and your concerns about Swing APIs, performance, bugs, packaging, and so on. Please keep in mind that our current focus is on improving Swing's reliability, performance, and documentation -- and not on adding new features. However, we welcome all feedback and we thank you for your support. Please send your feedback to this e-mail address: swing-feedback@java.sun.com #### A Final Exhortation Please keep in touch. Visit The Swing Connection regularly!