Skip navigation links

NetBeans Architecture Answers for Look & Feel Customization Library module

WARNING: answering questions version 1.24 rather than the current 1.29.

Interfaces table

Group of java interfaces
Interface NameIn/OutStabilitySpecified in What Document?
PlafAPIExportedFriend .../netbeans/swing/plaf/package-summary.html

Group of property interfaces
Interface NameIn/OutStabilitySpecified in What Document?
LookAndFeelClassNameExportedUnder Development

The module initializes proper Look&Feel. The decision is done based on various inputs including what has been specified on command line. To allow easier branding for those who build applications on top of NetBeans, there is key LookAndFeelClassName in org.netbeans.swing.plaf.Bundle bundle which can be branded to actual name of the L&F class. The module will decide which sets of customizations to load based on the chosen look and feel.

LookAndFeelCustomsClassNameExportedUnder Development

The module adds some UIManager keys and values to provide e.g. special border for main window toolbar or UI classes for tab control headers. By default the proper subclass of LFCustoms is derived from current Look and Feel name. Applications building on top of NetBeans can provide their own look and feel customizations by branding LookAndFeelCustomsClassName key in org.netbeans.swing.plaf.Bundle bundle.

General Information

Project and platform dependencies


Compatibility with environment

Access to resources

Lookup of components

Execution Environment

Format of files and protocols

Performance and Scalability