com.ibm.etools.systems.application.visual.editor.srcinfo.editparts
Class SourceInfoEditPartProvider
java.lang.Object
AbstractEditPartProvider
com.ibm.etools.systems.application.visual.editor.providers.DefaultSystemEditPartProvider
com.ibm.etools.systems.application.visual.editor.srcinfo.editparts.SourceInfoEditPartProvider
public class SourceInfoEditPartProvider
- extends DefaultSystemEditPartProvider
EditPart provider for source model elements.
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
SourceInfoEditPartProvider
public SourceInfoEditPartProvider()
getDiagramEditPartClass
protected Class getDiagramEditPartClass(View view)
- Gets a diagram's editpart class.
This method should be overridden by a provider if it wants to provide this service.
- Overrides:
getDiagramEditPartClass
in class DefaultSystemEditPartProvider
- Parameters:
view
- the view to be controlled by the created editpart
getEdgeEditPartClass
protected Class getEdgeEditPartClass(View view)
- Set the editpart class to the editpart mapped to the supplied view's semantic hint.
- Overrides:
getEdgeEditPartClass
in class DefaultSystemEditPartProvider
- See Also:
org.eclipse.gmf.runtime.diagram.ui.services.editpart.AbstractEditPartProvider#setConnectorEditPartClass(org.eclipse.gmf.runtime.diagram.ui.internal.view.IConnectorView)
getNodeEditPartClass
protected Class getNodeEditPartClass(View view)
- Gets a Node's editpart class.
This method should be overridden by a provider if it wants to provide this service.
- Overrides:
getNodeEditPartClass
in class DefaultSystemEditPartProvider
- Parameters:
view
- the view to be controlled by the created editpart
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.