com.ibm.etools.systems.application.visual.editor.editparts.impl
Class SystemTreeNodeEditPart
java.lang.Object
TreeContainerEditPart
com.ibm.etools.systems.application.visual.editor.editparts.impl.TreeNodeEditPart
com.ibm.etools.systems.application.visual.editor.editparts.impl.SystemTreeNodeEditPart
public class SystemTreeNodeEditPart
- extends TreeNodeEditPart
Customzied tree node editpart that are used in Outline page.
Method Summary |
protected List |
getNodeChildren(Node node)
Collect non-compartment children of the node. |
protected boolean |
isCompartment(Node node)
Checks whether the node passed in as an argument is compartment |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
copyright
public static final String copyright
- See Also:
- Constant Field Values
SystemTreeNodeEditPart
public SystemTreeNodeEditPart(Object model)
- Constructor.
- Parameters:
model
-
getNodeChildren
protected List getNodeChildren(Node node)
- Collect non-compartment children of the node. If one of the children is a compartment then children of
this non-compartment children of this compartment child are appended to the list.
- Overrides:
getNodeChildren
in class TreeNodeEditPart
- Parameters:
node
- - the node from which children are collected
- Returns:
List
of non-compartment children of the node passed in as an argument
isCompartment
protected boolean isCompartment(Node node)
- Checks whether the node passed in as an argument is compartment
- Overrides:
isCompartment
in class TreeNodeEditPart
- Parameters:
node
- - The node to check
- Returns:
true
if node is a compartment, false
otherwise
Copyright © 2011 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.