Uses of Interface
net.sf.cuf.fw.Dc

Packages that use Dc

Package	Description
net.sf.cuf.fw	This package holds a very light weight framework for structuring Java Swing or JavaFX applications. It basically defines each dialog is modeled as a strongly coupled pair of a dialog component (class implements the Dc interface) and a presentation component (class implements the Pc interface) the application is modeled with exactly on object that implements the Application interface a very simple life cycle is defined (the the interfaces for details)
net.sf.cuf.fw2	This package contains a "medium" sized framework for structuring a Java Swing or JavaFX client, and is based on the interfaces in the net.sf.cuf.fw package.

Uses of Dc in net.sf.cuf.fw

Methods in net.sf.cuf.fw with parameters of type Dc

Modifier and Type	Method and Description
void	Pc.init(Dc pDc, Map<String,? super Object> pArgs) This method is called by the dialog controller peer during the initialisation phase of an application. All arguments are handed in with a map object, that map always contains the application object with the key Application.APPLICATION_KEY.
void	Dc.init(Dc pParent, Map<String,? super Object> pArgs) This method is called by the parent dialog controller during the initialisation phase of an application. An implementation should first initialize all of its sub-controllers (if there are any) and then initialize its presentation component. All arguments are handed in with a map object, that map always contains the application object with the key Application.APPLICATION_KEY.

Uses of Dc in net.sf.cuf.fw2

Subinterfaces of Dc in net.sf.cuf.fw2

Modifier and Type	Interface and Description
interface	AppDc A AppDc enhances the basic Dc interface with support for AppEvent's and serves as a dialog coordinator for any number of DialogDc objects. There is one AppDc/AppPc pair per top-level application window.
interface	DialogDc A DialogDc enhances the basic Dc interface with a more powerful dialog lifecycle and support for AppEvent's. A DialogDc object is in one of the following five states: not exist (before new was called) created (new was called and an object exists) initialized (after the call to init()) active (after a call to doActivate()) passive (after a call to doPassivate()) The life cycle is typical for top level dialogs, that can be activated by the user through some menu/toobar/...

Classes in net.sf.cuf.fw2 that implement Dc

Modifier and Type	Class and Description
class	AbstractAppDc The AbstractAppDc implements the common stuff (AppEvent handling) of the AppDc interface.
class	AbstractDialogDc The AbstractDialogDc implements the common stuff (AppEvent handling, canPassivate check) of the DialogDc interface.

Methods in net.sf.cuf.fw2 that return Dc

Modifier and Type	Method and Description
Dc	DialogManager.getActiveDialog() Returns the last dialog that was opened by this DialogManager or null if there is currently no active dialog.
Dc	AppDc.getActiveDialog() Returns the active dialog.
Dc	AbstractAppDc.getActiveDialog()
Dc	DialogDescription.getDc() Return the dialog of this description
Dc	OpenDialogEvent.getDialog() The dialog Dc of this open event.
Dc	CloseDialogEvent.getDialog() The dialog Dc of this close event.

Methods in net.sf.cuf.fw2 that return types with arguments of type Dc

Modifier and Type	Method and Description
List<Dc>	DialogManager.getActiveDialogs() Returns a list of active dialog objects.
List<Dc>	AppDc.getActiveDialogs() Returns a list of the active dialogs.
List<Dc>	AbstractAppDc.getActiveDialogs()
Class<? extends Dc>	DialogDescription.getDialogClass() Retrun the dialog class.

Methods in net.sf.cuf.fw2 with parameters of type Dc

Modifier and Type	Method and Description
void	DialogManager.DialogCallback.dialogClosed(Dc pDc, boolean pWasClosed, Map<String,Object> pArgs) Called after a dialog was closed.
void	DialogManager.DialogCallback.dialogOpened(Dc pDc, Map<String,Object> pArgs) Called after a dialog was opened.
void	AbstractDialogPc.init(Dc pDc, Map<String,? super Object> pArgs) This method is called by the dialog controller peer during the initialisation phase of an application.
void	AbstractDialogDc.init(Dc pParent, Map<String,? super Object> pArgs) This method is called by the parent dialog controller during the initialisation phase of an application.
void	AbstractAppDc.init(Dc pParent, Map<String,? super Object> pArgs) This method is called by the Application during the initialisation phase of an application.
static void	DialogDescription.initDialogs(Map<String,DialogDescription> pKnownDialogs, Application pApp, Dc pParent, Map<String,? super Object> pArgs) Initialize the Dc's for a map of dialog descriptions.
void	DialogManager.openDialog(OpenDialogEvent pEvent, Dc pParent) Open a new dialog.
void	DialogManager.postAppEvent(Dc pDc, AppEventSupport pAppEventSupport, AppEvent pAppEvent) Filter for an AppEvent hierarchy: if a OpenDialogEvent or an CloseDialogEvent is posted, we try to handle it.
void	DialogDescription.setDc(Dc pDc) Set the dialog for this description

Method parameters in net.sf.cuf.fw2 with type arguments of type Dc

Modifier and Type	Method and Description
void	DialogDescription.setDialogClass(Class<? extends Dc> pDialogClass) Set the dialog class

Constructors in net.sf.cuf.fw2 with parameters of type Dc

Constructor and Description
CloseDialogEvent(Object pSource, Dc pDialog) Creates a new close dialog.
CloseDialogEvent(Object pSource, Dc pDialog, boolean pDispose) Creates a new close dialog.
OpenDialogEvent(Object pSource, Dc pDialog) Create a new open dialog event.
OpenDialogEvent(Object pSource, Dc pDialog, Map<String,Object> pDialogArguments) Create a new open dialog event.