Rational Developer for Power Systems Software
V7.6

com.ibm.etools.systems.application.visual.editor.srcinfo.ui.properties
Class SourceInfoCalleeSection

java.lang.Object
  extended by AbstractModelerPropertySection
      extended by com.ibm.etools.systems.application.visual.editor.ui.properties.AbstractApplicationModelPropertySection
          extended by com.ibm.etools.systems.application.visual.editor.srcinfo.ui.properties.SourceInfoRelationSection
              extended by com.ibm.etools.systems.application.visual.editor.srcinfo.ui.properties.SourceInfoCalleeSection

public class SourceInfoCalleeSection
extends SourceInfoRelationSection

Default property section displays the callees of a given element.


Field Summary
static String copyright
           
 
Fields inherited from class com.ibm.etools.systems.application.visual.editor.srcinfo.ui.properties.SourceInfoRelationSection
MENU_ID_PREFIX
 
Constructor Summary
SourceInfoCalleeSection()
          Constructor
 
Method Summary
 
Methods inherited from class com.ibm.etools.systems.application.visual.editor.srcinfo.ui.properties.SourceInfoRelationSection
addActions, createControls, getControl, handleOpenSource, supportsOpenSourceAction, update
 
Methods inherited from class com.ibm.etools.systems.application.visual.editor.ui.properties.AbstractApplicationModelPropertySection
getEditor, getIconRetriever, getImage, getPropertiesSectionHelper, getSemanticObject, setHelp, setHelp, setInput, setPropertiesSectionHelper
 
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

SourceInfoCalleeSection

public SourceInfoCalleeSection()
Constructor


Rational Developer for Power Systems Software
V7.6

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.