Remote Systems
v6.4.1

com.ibm.etools.systems.core.ui.propertypages
Class SystemRemotePropertyPageNode

java.lang.Object
  extended byPreferenceNode
      extended bycom.ibm.etools.systems.core.ui.propertypages.SystemRemotePropertyPageNode

public class SystemRemotePropertyPageNode
extends PreferenceNode

Our version of PropertyPageNode that does not require a RegistryPageContributor input.

See Also:
Serialized Form

Field Summary
static String copyright
           
 
Constructor Summary
SystemRemotePropertyPageNode(SystemPropertyPageExtension contributor, IAdaptable element)
          Constructor.
 
Method Summary
 void createPage()
          Creates the preference page this node stands for.
 void disposeResources()
          (non-Javadoc) Method declared on IPreferenceNode.
 Image getLabelImage()
          Returns page icon, if defined.
 String getLabelText()
          Returns page label as defined in the registry.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values
Constructor Detail

SystemRemotePropertyPageNode

public SystemRemotePropertyPageNode(SystemPropertyPageExtension contributor,
                                    IAdaptable element)
Constructor.

Method Detail

createPage

public void createPage()
Creates the preference page this node stands for. If the page is null, it will be created by loading the class. If loading fails, empty filler page will be created instead.


disposeResources

public void disposeResources()
(non-Javadoc) Method declared on IPreferenceNode.


getLabelImage

public Image getLabelImage()
Returns page icon, if defined.


getLabelText

public String getLabelText()
Returns page label as defined in the registry.


Remote Systems
v6.4.1

Copyright © 2005 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.