A. The Java Foundation Classes (JFC) are a comprehensive set of GUI components and services which dramatically simplify the development and deployment of commercial-quality desktop and Internet/Intranet applications.
A. The Java Foundation Classes are a superset that contains AWT. JFC extends AWT by adding many components and services.
A. There are six main differences:
A. Not being a port from a different environment, the Java Foundation Classes conform 100% with Java's object and component model. Developers find JFC a very easy and natural extension to the Java Platform.
A. The Java Foundation Classes substantially reduces the amount of programming needed by providing many reusable and cross-platform UI components.
In addition, foundation services offered in JFC enable developers to build richer solutions with fewer lines of code. The last and most important point is that developers don't have to worry that their application will only perform well on one platform. JFC is designed to be 100% cross-platform.
A. Absolutely; we have close relationships with all the major Java development environment vendors. As part of the Java Platform, JFC is available in all major Java development tools. A listing of tool providers can be found on this site under the product directory.
A. Because the Java Foundation Classes are designed to be truly cross-platform, they run equally well on all Java Compatible Platforms.
A. The JFC/Swing components can be divided into two groups -- those that provide improved, JFC/Swing versions of AWT components, and those that are new.
A. Available for JDK 1.1 and in the Java 2 Platform:
Available only in the Java 2 Platform:
A. Applications built using JFC are not locked in to a specific look and feel. Using JFC, developers can create apps that either have a native platform look and feel or use the Java look and feel -- or they can create their own custom look and feel. The power lies in the hands of developers -- they can develop their products using the look and feel that is most appropriate for their users.
A. They are the same thing. These are just two term that describe the attributes of JFC components.
A. Nothing! Sun does not charge for the use or distribution of JFC.
A. Swing is the project code name for the lightweight GUI components in JFC.
A. As part of JFC, the Accessibility API enables Java applications to work with alternate input and output devices such as Screen Readers, Screen Magnifiers, Braille terminals, and others. The Accessibility API takes the current Java system that is visually oriented and extends it to be usable by people who need to work with other non-visual devices. We are truly taking "Write Once, Run Anywhere" to another level by extending the benefits of Java Computing to users with disabilities.
A. With Java 2D, developers can render, manipulate, and transform complex 2D images and text. Java 2D enables the creation of richer-looking components and applications.
A. To provide a common interface for developers who are deploying applications and services in a heterogeneous computing environment.
A. Yes. The Java 2 Platform, SE, provides pluggable look-and-feel implementations for the Windows and UNIX platforms. Other look and feels are available, as well.
A. We have not determined that we have the right to deliver the Windows look and feel on platforms other than Windows. If Microsoft were to confirm our right to deliver this look and feel on other operating systems, we would be delighted to remove the lock. To date, Microsoft has declined to do this.
|Swing versions of AWT components||New components|
combo boxes (
scroll panes and scroll bars
menus and menu bars
styled text areas
spinners (as of 1.4)
formatted text fields (as of 1.4)