About the JFC and Swing

JFC is short for Java Foundation Classes, which encompass a group of features for building graphical user interfaces (GUIs ^[1] ) and adding rich graphics functionality and interactivity to Java applications. JFC was first announced at the 1997 JavaOne ^SM developer conference. It is defined as containing the features shown in Table 1. ^[2]

^[1] The acronym for graphical user interface, GUI, is pronounced "gooey."

^[2] See the JFC home page for more information on JFC features: http://java.sun.com/products/jfc/index.html.

Table 1. Features of the Java Foundation Classes

Feature	Description
Swing GUI Components	Includes everything from buttons to split panes to tables. See screenshots of all the components in A Visual Index to Swing Components (page 37) in Chapter 3.
Pluggable Look-and-Feel Support	Gives any program that uses Swing components a choice of look and feel. For example, the same program can use either the Java or the Windows look and feel. Many more look-and-feel packages are available from various sources. As of v1.4.2, the Java platform supports the GTK+ look and feel, which makes hundreds of existing look and feels available to Swing programs.
Accessibility API	Enables assistive technologies, such as screen readers and Braille displays, to get information from the user interface.
Java 2D TM API	Enables developers to easily incorporate high-quality 2D graphics, text, and images in applications and applets. Java 2D includes extensive APIs for generating and sending high-quality output to printing devices.
Drag-and-Drop Support	Provides the ability to drag and drop between Java applications and native applications.
Internationalization	Allows developers to build applications that can interact with users worldwide in their own languages and cultural conventions. With the input method framework developers can build applications that accept text in languages that use thousands of different characters , such as Japanese, Chinese, or Korean.

This book concentrates on the Swing components. We help you choose the appropriate components for your GUI, tell you how to use them, and give you the background information you need to use them effectively. We also discuss other JFC features as they apply to Swing components.

Note: "Swing" was the code name of the project that developed the new components. Although unofficial , it's frequently used to refer to the new components and related API. "Swing" is immortalized in the package names for the Swing API, which begin with javax.swing .

Which Releases Contain the Swing API?

The short answer is that the Swing API has been included in the Java 2 platform, Standard Edition (J2SE ^TM ) since its initial release (1.2). A 1.4.2 release of the Java 2 platform is included on the CD that accompanies this book. You can also download the latest release from the Sun Microsystems Web site at: http://java.sun.com/j2se/.

This book concentrates on the Swing API in the Java 2 platform, Standard Edition, v1.4.2. Except where noted, the code in this book works, without change, with earlier J2SE releases. ^[3] We also include notes about a few important changes expected in 1.5.

^[3] We recommend that you use the latest version of the Java 2 platform. However, it is possible to use the Swing components with releases as early as 1.1. We give tips for using earlier releases where necessary.

Which Swing Packages Should I Use?

The Swing API is powerful, flexible ”and immense. In release 1.4 of the Java platform, the Swing API has 17 public packages:

javax.accessibility	javax.swing.plaf	javax.swing.text.html
javax.swing	javax.swing.plaf.basic	javax.swing.text.parser
javax.swing.border	javax.swing.plaf.metal	javax.swing.text.rtf
javax.swing.colorchooser	javax.swing.plaf.multi	javax.swing.tree
javax.swing.event	javax.swing.table	javax.swing.undo
javax.swing.filechooser	javax.swing.text

Fortunately, most programs use only a small subset of the API. This book sorts out the API for you, giving you examples of common code and pointing you to methods and classes you're likely to need. Most of the code in this book uses only one or two Swing packages:

• javax.swing

• javax.swing.event (not always required)