Tab Control
Friend, Private or Third Party

The Swing components in this package were carefully designed to be consistent with standard Swing components in their function, usage and ui registration mechanisms.

See:
Description

Tab Control

org.netbeans.swing.popupswitcher
org.netbeans.swing.tabcontrol	TabDisplayer and TabbedControl
org.netbeans.swing.tabcontrol.event
org.netbeans.swing.tabcontrol.plaf

The Swing components in this package were carefully designed to be consistent with standard Swing components in their function, usage and ui registration mechanisms.

What is New (see all changes)?

• Jan 13 '09 Added new methods to WinsysInfoForTabbedContainer class which can adjust the behavior of TopComponents in tabbed container.

  Added new methods to class WinsysInfoForTabbedContainer to find out the status (enabled/disabled) of some window system features for given TopComponent, e.g. is the TopComponent allowed to slide-out etc.

• Jun 6 '08 Added new abstract class WinsysInfoForTabbedContainer which can adjust some tabbed container properties and behavior.

  The new abstract class WinsysInfoForTabbedContainer is a replacement for interface WinsysInfoForTabbed. The new class implements the old interface and also contains method informing the tabbed containers about the state of some of window system switches that may disable some of its functionality. (For example disable window sliding).

• Nov 28 '07 Added support for transparency of slided-in windows

  Containers with slided-in windows can be painted with different alpha channel to achieve window transparency.

• Jul 24 '07 API switched to 'public - under development'

  Since there are some third party modules that provide non-standard look and feel for the TabControl, the API is switched back to 'public - under development status'.

• Oct 5 '06 Module core/windows now has Friend API dependency on core/swing/tabcontrol

  The Tab Control module was unnecessarily exposing all of its packages as public API. Since it's no longer possible to use the Tab Control as a standalone module (because of its dependencies on Windows API) the module now has only a single friend module - Core/Windows.

  There were also other changes in Tab Control UI classes for various L&Fs (i.e. classes that were previously in public API packages), some methods have been removed, some were added. Also some classes in org.netbeans.swing.tabcontrol package have changed.

Use Cases

Primary use cases are in the NetBeans window system, as top level containers in the main window; future use cases include providing a consistent UI for tabs in the property sheet, the component inspector and the output window, but this probably will not happen for 4.0.

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?
TabbedContainerAPI	Exported	Friend	.../swing/tabcontrol/TabbedContainer.html
PopupSwitcherAPI	Exported	Friend	.../swing/popupswitcher/package-summary.html API contains classes used only by switchers accessible through main menu in "Window/Documents..." and "Go To/Recent Document". Besides this module the package is used from core/windows too. Classes contained in the package are rather general and therefore this package could be moved in the future. It is placed here only due to current modules dependencies. Consequently the package is not intended for external use. For more information on SwitcherTable and SwitcherTableItem see a javadoc.

Group of property interfaces

Interface Name	In/Out	Stability	Specified in What Document?
nb.tabs.suppressCloseButton	Exported	Under Development	The system property nb.tabs.suppressCloseButton can be used to hide close buttons by default.

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?

Nothing.

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