org.opensubsystems.core.application
Class SeparatorModule

java.lang.Object
  extended by org.opensubsystems.core.application.ThickClientModuleImpl
      extended by org.opensubsystems.core.application.SeparatorModule
All Implemented Interfaces:
ThickClientModule

public class SeparatorModule
extends ThickClientModuleImpl

Dummy module responsible for separating other modules.

Version:
$Id: SeparatorModule.java,v 1.4 2007/01/07 06:14:39 bastafidli Exp $
Author:
Miro Halas
Code reviewer:
Miro Halas
Code reviewed:
1.2 2006/03/13 15:39:55 bastafidli

Field Summary
static java.lang.String SEPARATOR
          Well known name of the separator module.
 
Fields inherited from class org.opensubsystems.core.application.ThickClientModuleImpl
m_bInitialized, m_client
 
Constructor Summary
SeparatorModule()
           
 
Method Summary
 boolean activate(boolean bReactivate)
          Activate the module so that user can interact with it.
 java.lang.String getName()
          Get user friedly name UNIQUE name of the module.
 void pasivate()
          Pasivate the module since user no longer interacts with it.
 
Methods inherited from class org.opensubsystems.core.application.ThickClientModuleImpl
destroy, displayMessage, getClient, init, refresh
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

SEPARATOR

public static final java.lang.String SEPARATOR
Well known name of the separator module.

See Also:
Constant Field Values
Constructor Detail

SeparatorModule

public SeparatorModule()
Method Detail

getName

public java.lang.String getName()
Get user friedly name UNIQUE name of the module.

Returns:
String

activate

public boolean activate(boolean bReactivate)
Activate the module so that user can interact with it.

Specified by:
activate in interface ThickClientModule
Overrides:
activate in class ThickClientModuleImpl
Parameters:
bReactivate - - this is true if the module was pasivated but it is being immediately activated again because the other module which caused it's pasivation coun't be activated again. This is false if some other module was active and now this module is being activated.
Returns:
boolean - true if sucessfully activated false if cannot be activated and either the previously active module should remain active or no module should be active

pasivate

public void pasivate()
Pasivate the module since user no longer interacts with it.

Specified by:
pasivate in interface ThickClientModule
Overrides:
pasivate in class ThickClientModuleImpl


Copyright © 2003 - 2006 OpenSubsystems s.r.o.