Package javax.microedition.plaf

AGUI provides a Pluggable Look and Feel architecture, similar to that which is defined in Java SE (from which AGUI is subset).

See:
Description

Interface Summary

ButtonUI	Pluggable look and feel interface for JButton.
ComboBoxUI	Pluggable look and feel interface for JComboBox.
DesktopPaneUI	Pluggable look and feel interface for JDesktopPane.
LabelUI	Pluggable look and feel interface for JLabel.
ListUI	The JList pluggable look and feel delegate.
MenuBarUI	Pluggable look and feel interface for JMenuBar.
MenuItemUI	Pluggable look and feel interface for JMenuItem.
OptionPaneUI	Pluggable look and feel interface for JOptionPane.
PopupMenuUI	Pluggable look and feel interface for JPopupMenu.
ProgressBarUI	Pluggable look and feel interface for JProgressBar.
ScrollBarUI	Pluggable look and feel interface for JScrollBar.
SliderUI	Pluggable look and feel interface for JSlider.
SpinnerUI	Pluggable look and feel interface for JSpinner
TabbedPaneUI	Pluggable look and feel interface for JTabbedPane.
TreeUI	Pluggable look and feel interface for JTree.

Class Summary

PlatformFactory

This class provides the factory for creating objects that delegate the implementation of UI components.

Package javax.microedition.plaf Description

AGUI provides a Pluggable Look and Feel architecture, similar to that which is defined in Java SE (from which AGUI is subset). The AGUI expert group debated considerably about the architecture of the pluggable look and feel functionality and determined the following:

• Pluggable look and feel was an essential part of the AGUI optional package
• The primary use of this infrustructure was for implementors of AGUI (OEM's and Service Providers) to deeply customize the look and feel of the toolkit
• Applications should not have direct control over the look and feel of the platform
• The architecture should be implementable on native toolkits
• The fundamental architecture of pluggable look and feel in Java SE was sound, but some of the details needed to be re-evaluated

In order to support the above requirements a new architecture was created. The created architecture and API form a framework and guidance for a pluggable look and feel. However, the current version of the API does not guarantee look&feel implementations to be portable across devices or AGUI implementations. The look and feel implementations will be dependent on the device and also on the internal structure of the implementation in Swing components.

The basic change that was made to pluggable look and feel architecture was to move the implementation APIs from classes to interfaces. The reasoning behind this was to allow greater flexibility for implementations. The set of changes made for AGUI are:

• ComponentUI is the only abstract class left in from Java SE in the javax.swing.plaf
• javax.microedition.plaf contains the remainder of the UI classes.
• All UI classes in javax.microedition.plaf are changed from abstract classes to interfaces
• A plaf factory PlatformFactory has been added to javax.microedition.plaf
• A platform factory is required for each look and feel.
• The factory is responsible for the supply of UI delegate objects
• The property PlaformFactory is set to the initial factory
• The method PlatformFactory.createPlatformObject() returns objects of type ComponentUI
• No application API to allow programmer to access the UI.

Note: Most of the Swing API is not thread safe. For details, see Threads and Swing, a section in The Java Tutorial.

Since:

1.2