These pages contain a collection of toolbar button graphics. The graphics have been designed specifically for use with the Java look and feel. They conform to the Java look and feel Design Guidelines (see the " Designing Button Graphics" section of the " Application Graphics" chapter). A set of attributes accompanies each graphic. This information can easily be used to create Swing Actions.
As the Human Interface Group, we strive to improve the user experience for you and your end-users. This graphics repository provides you with professional quality graphics that will save you development time. Your end-users benefit by leveraging their knowledge of these graphics and terminology across different Java look and feel applications.
To provide feedback about the graphics repository, send email to the Java look and feel Design Team.
The graphics that comprise the Java look and feel Graphics Repository are located in the "jlfgr-1_0.jar" file. This Jar file can be obtained by downloading and unzipping the following Zip file.
Download the Java look and feel Graphics Repository:
Each graphic has a set of attributes describing it and specifying how it should be used. These attributes include:
"Description" is the concept that the graphic should embody. This explanation can help you decide if this concept matches your product's functionality. Modified to account for the context, this long explanation might be appropriate for use in a status bar.
"Graphics" are the two images that visually represent the "Description" field. They are 16x16 pixels and 24x24 pixels, respectively. The design principles and techniques used to create these graphics are described in the " Designing Button Graphics" section of the Java look and feel Design Guidelines.
"Name" is the short phrase that should appear in menus and on buttons. Variables, set off by curly brackets, appear in some of the "Name" fields. If this extra information is available, provide it for your end-user's benefit. If you determine that your end-users might benefit from the display of both graphics and text, provide a method for end-users to indicate their preference of text only, graphics only, or both graphics and text. To determine if ellipses are called for in your menu items or on your buttons, consult the Java look and feel Design Guidelines.
"Tool Tip" is the short phrase that should appear as the Tool Tip. Variables, set off by curly brackets, appear in some of the "Tool Tip" fields. If this extra information is available, provide it for your end-users benefit.
"Shortcut" or "Accelerator" is the keystroke combination (consisting of the given letter and a modifier key) that should activate the function. Functionality that end-users need simple and constant access to should have shortcuts. Ensure that each shortcut is unique within your application. For a more complete description of design considerations for shortcuts, please see the "Shortcuts" section in the Java look and feel Design Guidelines. Both new and existing shortcuts are summarized in an "Expanded Shortcuts" table.
"Mnemonic" is the keystroke that, within the appropriate scope, activates the function. Mnemonics are most often seen on menu items. The suggested mnemonics are provided to ensure that the keystrokes do not conflict with each other. Please use them in the given order. Consistency across Java look and feel applications enhances your end-user's comfort with and confidence in your product. For a more complete description of design considerations for mnemonics, please see the "Mnemonics" section in the Java look and feel Design Guidelines.
"File Name" is the relative path name for the graphics. They follow the format:
This file name uniquely specifies the location of the graphic within the Java Archive. The graphics are grouped by usage in subdirectories. For example, there are two different button graphics for "Stop". One is for media transport and one for general use. There is also an "Align Left" for text and an "Align Left" for general objects.
"Other Notes" is for useful information that is not appropriate or captured in the other fields. If the "Description" field is not sufficient to help determine whether a concept matches the product's functionality, this field may help to guide your decision.