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.
This table lists all of the module exported APIs
defined stability classifications. It is generated
based on answers to questions about the architecture
of the module. Read them all
Group of java interfaces
Group of property interfaces
|Interface Name||In/Out||Stability||Specified in What Document?
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
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.
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
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