net.sf.cuf.examples.model.uc2

Class UseCase2Dc

java.lang.Object

net.sf.cuf.fw2.AbstractDialogDc

net.sf.cuf.examples.model.uc2.UseCase2Dc

All Implemented Interfaces:

AppEventSupport, Dc, DialogDc, Disposable, SimpleLifeCycle

public class UseCase2Dc
extends AbstractDialogDc
implements DialogDc

UseCase2Dc is the dialog component of a very simple dialog. It demonstrates the "can passivate" mechanism.

Field Summary

Fields inherited from class net.sf.cuf.fw2.AbstractDialogDc

mAppEventSupport, mDialogManager

Constructor Summary

Constructors

Constructor and Description
UseCase2Dc()

Method Summary

Methods

Modifier and Type	Method and Description
boolean	canPassivate() Test to check if a dialog in the active state can be moved to the passive state, we ask our presentation component if it is o.k.
void	dispose(Map<String,? super Object> pArgs) Called from the dialog coordinator to tell the dialog to cleanup all resources.
void	doActivate(Map<String,? super Object> pArgs) Called from the dialog coordinator to tell the dialog to switch to the active state.
void	doPassivate(Map<String,? super Object> pArgs) Called from the dialog coordinator to tell the dialog to switch to the passive state.
Object	getVisualPresentation() Called from the dialog coordinater in the initialized, active or passive state to get the visual representation for this dialog.
void	init(Dc pParent, Map<String,? super Object> pArgs) This method is called by the parent dialog controller during the initialisation phase of an application.

Methods inherited from class net.sf.cuf.fw2.AbstractDialogDc

postAppEvent

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface net.sf.cuf.appevent.AppEventSupport

postAppEvent

Constructor Detail

UseCase2Dc

public UseCase2Dc()

Method Detail

init

public void init(Dc pParent,
        Map<String,? super Object> pArgs)

This method is called by the parent dialog controller during the initialisation phase of an application.

Specified by:

init in interface Dc

Overrides:

init in class AbstractDialogDc

Parameters:

pParent - our parent must implement AppEventSupport

pArgs - variable argument list modeled as a key/value map, never null.

doActivate

public void doActivate(Map<String,? super Object> pArgs)

Called from the dialog coordinator to tell the dialog to switch to the active state.

Specified by:

doActivate in interface SimpleLifeCycle

Parameters:

pArgs - arguments, key is a String, value is any suitable objekt for the key

canPassivate

public boolean canPassivate()

Test to check if a dialog in the active state can be moved to the passive state, we ask our presentation component if it is o.k. to passivate.

Specified by:

canPassivate in interface SimpleLifeCycle

Overrides:

canPassivate in class AbstractDialogDc

Returns:

true if the dialog can be passivated

doPassivate

public void doPassivate(Map<String,? super Object> pArgs)

Called from the dialog coordinator to tell the dialog to switch to the passive state.

Specified by:

doPassivate in interface SimpleLifeCycle

Parameters:

pArgs - arguments, key is a String, value is any suitable objekt for the key

dispose

public void dispose(Map<String,? super Object> pArgs)

Called from the dialog coordinator to tell the dialog to cleanup all resources. We only call dispose of our Pc.

Specified by:

dispose in interface Disposable

Overrides:

dispose in class AbstractDialogDc

Parameters:

pArgs - arguments, key is a String, value is any suitable objekt for the key

getVisualPresentation

public Object getVisualPresentation()

Called from the dialog coordinater in the initialized, active or passive state to get the visual representation for this dialog.

Specified by:

getVisualPresentation in interface DialogDc

Returns:

an object that represents the visual representation of this dialog