Community
Participate
Working Groups
Few classes listed below perform complex initialization of graphical viewer with sole purpose to obtain DiagramEditPart: PrintHelper.createDiagramEditPart(Diagram,PreferencesHint) CopyToImageUtil.createDiagramEditPart(Diagram,Shell,PreferencesHint) OffscreenEditPartFactory.createDiagramEditPart(Diagram) Besides, similar initialization takes place in DiagramEditor.configureGraphicalViewer() which we opt for being generated. It seems reasonable to allow "toolsmith" to have control over that process and to keep that functionality in a single place with explicit API. Using IAdaptable mechanism to get DiagramEditPart (or some new dedicated interface that might respect possible uses/extra features) from Diagram would be (an Eclipse-style :) solution, e.g. existing code will change to: DiagramEditPart createDiagramEditPart(Diagram diagram) { return (DiagramEditPart) Platform.getAdapterManager().getAdapter(diagram, DiagramEditPart.class); }
Changing component to "Runtime Diagram"
would be nice to have it ASAP
This is not currently in our plans for 3.2. Contributions welcome...
Not yet assigned to a release (assigned to a milestone with the Plan keyword). Moving to the next release, GMF 2.1.
[GMF Restructure] Bug 319140 : product GMF and component Runtime was the original product and component for this bug