com.ibm.etools.systems.application.visual.editor.srcinfo.ui.properties
Class SourceContainerIncludeTableContentProvider
java.lang.Object
com.ibm.etools.systems.application.visual.editor.srcinfo.ui.properties.SourceContainerIncludeTableContentProvider
public class SourceContainerIncludeTableContentProvider
- extends Object
The content provider for source container's Includes table.
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
copyright
public static String copyright
SourceContainerIncludeTableContentProvider
public SourceContainerIncludeTableContentProvider()
- Constructor.
dispose
public void dispose()
- See Also:
IContentProvider
inputChanged
public void inputChanged(Viewer viewer,
Object oldInput,
Object newInput)
- See Also:
IContentProvider
getElements
public Object[] getElements(Object inputElement)
- See Also:
IStructuredContentProvider
getColumnImage
public Image getColumnImage(Object element,
int columnIndex)
- See Also:
ITableLabelProvider
getColumnText
public String getColumnText(Object element,
int columnIndex)
- See Also:
ITableLabelProvider
addListener
public void addListener(ILabelProviderListener listener)
- See Also:
IBaseLabelProvider
isLabelProperty
public boolean isLabelProperty(Object element,
String property)
- See Also:
IBaseLabelProvider
removeListener
public void removeListener(ILabelProviderListener listener)
- See Also:
IBaseLabelProvider
getCallableBlocks
protected Object[] getCallableBlocks(SourceContainer sourceContainer)
getPropertiesAdapter
protected IApplicationModelPropertiesAdapter getPropertiesAdapter(Object semanticElement)
- Get properties adapter
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.