bibliothek.gui.dock.common.intern

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

PREV PACKAGE NEXT PACKAGE

FRAMES NO FRAMES

Package bibliothek.gui.dock.common.intern

Classes and interfaces used internally.

See:
Description

Interface Summary
CControlAccess	Gives access to the internal methods of a `CControl`. This class is not intended to be used by clients, using it wrongly can result in weird behavior of its owning `CControl`.
CControlFactory	A factory creating various elements that are needed in a `CControl` and its associated components.
CDockable	A basic element representing some `Component` and a wrapper around a `Dockable`. Note: This interface is not intended to be implemented by clients.
CDockableAccess	An interface giving access to the hidden properties of a `CDockable`.
CDockFrontendListener	A listener that is added to a `CDockFrontend`.
CommonDockable	A `Dockable` which is a wrapper for a `CDockable`.
CommonElement	Root interface for `CommonDockable` and for `CommonDockStation`.
MutableCControlRegister	A `CControlRegister` whose contents can be changed.

Class Summary
AbstractCDockable	An abstract implementation of `CDockable`.
AbstractCStation<S extends CommonDockStation<?,?>>	A simple implementation of `CStation`.
AbstractDockableCStation<S extends CommonDockStation<?,?>>	An abstract implementation of `CStation` that can be docked like a `CDockable`.
CDockableLocationListenerManager	Helps `CDockable`s to keep track of their location and can automatically fire events to a `CDockableLocationListener`. Clients should not instanciate this class directly, they should add a `CDockableLocationListener` to a `CDockable` instead.
CDockController	The `DockController` that is usually used by a `CControl`.
CDockFrontend	A `DockFrontend` that uses `CSetting` instead of `Setting`.
CListenerCollection	A collection of the listeners which are normally added to a `CDockable`.
CommonMultipleDockableFactory	A factory used to create `CommonDockable`s.
CommonMultipleDockableLayout	An intermediate representation of the layout of a `CommonDockable` that is connected with a `MultipleCDockable`.
CommonSingleDockableFactory	This factory is used to create new `SingleCDockable`s using various `SingleCDockableFactory`s.
CommonSingleDockableLayout	An intermediate representation of the layout of a `CommonDockable` that is connected with a `SingleCDockable`.
ControlVetoClosingListener	A converter listening for `VetoableDockFrontendEvent`s and firing new `CVetoClosingEvent`s.
ControlVetoFocusListener	This listener observes a `DockController` and forwards all calls to a `CVetoFocusListener`.
CPlaceholderStrategy	This strategy assigns a unique identifier to all `CDockable`s that are registered at a `CControl`.
CSetting	A `Setting` that stores also the contents of a `CLocationModeManager`.
DefaultCControlRegister	Standard implementation of `CControlRegister`.
DefaultCDockable	An `CDockable` that uses a `DefaultCommonDockable` to show its content. Subclasses may override `DefaultCDockable.createCommonDockable()` to provide a custom subclass of `DefaultCommonDockable`, note that `DefaultCDockable.createCommonDockable()` is called as soon as the internal representation is required, e.g.
DefaultCommonDockable	A default implementation of `CommonDockable`, based on a `DefaultDockable`.
DelayedWorkingAreaSetter	A `DelayedWorkingAreaSetter` is a listener that is added to a `CControl` and waits until a `CStation` with a specific identifier is registered.
EfficientControlFactory	A factory that uses the most efficient elements, can only be used in environments where global events can be observed.
RootStationAdjacentFactory	This factory stores the property `CStation.getTypeId()` for any `CStation` that is found.

Enum Summary
DefaultCDockable.Permissions	Describes what the user can do with the enclosing `DefaultCDockable`. A name like `X_Y` tells, that feature `X` and feature `Y` are available.

Package bibliothek.gui.dock.common.intern Description

Classes and interfaces used internally. In general clients are discouraged to use the elements in this package directly. To be more specific:

Clients should not create objects of classes in this package
Clients should not implements interfaces of this package
Clients can use subclasses and subinterfaces which extend elements of this package but are not declared within this package
Clients can use the methods and constants offered in this package
These rules are not enforced in any way. Clients can use elements of this package, it may just not be the easiest solution