Overview (Look & Feel Customization Library)

Look & Feel Customization Library
Package	Description
org.netbeans.swing.plaf	This library installs custom values into UIDefaults, such as colors, borders and UI class names, which various components in NetBeans use to provide a customized or native appearance.

N/A

What is New (see all changes)?

Jan 31 '13 Support for dark theme fro Metal and Nimbus look and feel.

When using Nimbus or Metal look and feel then system property netbeans.plaf.dark.theme=true will switch to dark color theme which nicely fits to 'Norway Today' editor color schema.
Nov 27 '12 New look and feel customizations for Windows 8

New look and feel customizations for Windows 8
Jun 26 '12 New functions for getting foreground text color and color shifting

new functions:
static String getHexString(int color) static String getTextFgColorHTML() static Color getTextFgColor() static Color shiftColor(Color color) static Color getForeground(AttributeSet a)
Jun 30 '11 It is now possible to customize application-specific UIManager keys and values.

Read more about the look and feel Customs branding property.
May 6 '10 It is now possible to brand name of Look And Feel

Read more about the Look And Feel branding property.

Use Cases

Used by NetBeans to customize the UI to conform to UI design specifications; can be used by third parties who are employing parts of the NetBeans platform in their applications, such as the windowing system.

Exported Interfaces

This table lists all of the module exported APIs with defined stability classifications. It is generated based on answers to questions about the architecture of the module. Read them all...

Group of java interfaces

Interface Name	In/Out	Stability	Specified in What Document?
PlafAPI	Exported	Friend	.../netbeans/swing/plaf/package-summary.html

Group of property interfaces

Interface Name In/Out Stability Specified in What Document?

LookAndFeelClassName

Exported

Under 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.

LookAndFeelCustomsClassName

Exported

Under 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.

Implementation Details

What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?

Components such as the window system, which use values defined here, will behave in a reasonable way if those values are not defined. However, it is preferable that they declare a runtime dependency on the plaf library.

Read more about the implementation in the answers to architecture questions.

Look & Feel Customization LibraryFriend, Private or Third Party