| JSC >
Guidelines Home Page > Java Look and Feel Design Guidelines >
Part I: Overview >
2: The Java Foundation Classes >
Look and Feel Options
You, the designer, have the first choice of a look and feel design. You can determine the look and feel you want users to receive on a specific platform, or you can choose a cross-platform look and feel.
Do not specify a look and feel explicitly. This way, the Java look and feel, which is a cross-platform look and feel, is used by default.
If an error occurs while specifying the name of any look and feel, the Java look and feel is used by default.
If you do not specify the Java look and feel, you can specify another look and feel--one that ships with the JFC or one that someone else has made. Note, however, that not all look and feel designs are available on every platform. For example, the Microsoft Windows look and feel is available only on the Microsoft Windows platform.
Because there is far more to the design of an application than the look and feel of components, it is unwise to give end users the ability to swap look and feel designs while working in your application. Switching look and feel designs in this way only swaps the look and feel designs of the components from one platform to another. The layout and vocabulary do not change. Since layout conventions vary from platform to platform, this situation can result in an interface that looks inappropriate. For instance, swapping look and feel designs does not change the titles of the menus. (If you must provide users with the ability to switch look and feel designs, see Appendix D.)
|Java Look and Feel Design Guidelines, second edition.
Copyright 2001. Sun Microsystems, Inc. All Rights Reserved.