Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Graphical Modeling Framework/Versions/GMF 2.1

< Graphical Modeling Framework‎ | Versions
Revision as of 06:48, 24 October 2006 by Dstadnik.borland.com (Talk | contribs) (Double-click support for diagrams in navigator)

Graphical Modeling Framework 2.0 New and Noteworthy items

...broken down by milestones, (see GMF Project Plan for more details)

Back to Graphical Modeling Framework


GMF Release 1.0 (June 30, 2006)

GMF 1.0 New and Noteworthy

2.0 M1 (September 04, 2006)

Merging for plugin.xml and plugin.properties

Protected region is defined in plugin.xml where users may add their extensions. These extensions will be preserved on diagram editor regeneration. Properties file plugin.properties is merged using EMF merger for property files.


ProtectedRegionPluginXML.png


Add custom edit policies in gmfgen model

Custom behaviour may be added to diagram element using CustomBehaviour object. In generated code this means inserting custom edit policy in edit part of diagram element.


GMFCustomBehaviour.png


Default mapping creation wizard creates canvas mapping

Mapping wizard generated by EMF is enhanced by adding pages to select domain model, diagram canvas and palette. If specified domain, graphical and tooling definition models are loaded and canvas mapping that binds them is added.


GMFMappingWizardResult.png


Unit-testing

Unit-tests covering following parts of generated code were implemented:

- toolbar tools

- diagram and model resources saving

- diagram node hierarchy creation

- compilation test for user models with “instance class name” property specified

2.0 M2

Wizards to reconcile graphical and tooling definition models

Wizards that infer graphical and tooling definitions from domain model now can reconcile results with existing models. One may start such wizards explicitly using File -> New -> Other menu or use GMF Dashboard where 'Derive' actions switch wizards to reconcile mode if graphical and tooling definitions are selected for the project.


GMFDefReconcile.png


Diagram Content Navigator

Diagram content could be provided below diagram file node in standard Project Explorer Eclipse view. Read-only properties of underlying semantic element available for single-element selection.

GenNavigator metaclass was added to GMF GenModel. Default Navigator structure will be created automatically by GMF MapModel - GMF GenModel transformer, so it is necessary to run this transformation and regenerate the code from newly created GMF GenModel to get Navigator generated.


GMFEcoreDiagramNavigator.PNG


ILinkHelper implementation generated

Project Explorer selection could be synchronized with open diagram selection if "Link open editors with content in the Navigator" button pressed on Project Explorer toolbar. To implement this functionality additional class <DiagramPrefix>NavigatorLinkHelper will be generated.


NavigatorLinkHelper.PNG

Option to create a GenModel if it's missing

If during transformation appropriate .genmodel was not detected, toolsmith could browse for existing with an option to either create a new blank model with regular defaults or to launch EMF wizard to create .genmodel manually.

Gmf-missed-genmodel-dialog.png


Basic support for diagram partitioning

GMFMap's MappingEntry has a link to other CanvasMappings now. Once it's defined, transofrmation attaches OpenDiagramBehaviour to appropriate GenNode, and there's OpenDiagramEditPolicy generated that tries to open editor for the diagram.


Do not generate superfluous code in few particular cases

CanonicalEditPolicy is no longer generated for elements without immediate children to be updated. GraphicalNodeEditPolicy is generated only when there are links with inverted direction. You may notice that these policies are no longer registered within node's createDefaultEditPolicies() method after regeneration and remove respective classes. Alternatively, if you didn't change the edit policies' code, you may remove all classes extending CanonicalEditPolicy and GraphicalNodeEditPolicy in your plug-in and regenerate the code. This will leave only those policies that are needed.

2.0 M3

Double-click support for diagrams in navigator

Corresponding diagram will be opened in editor (activated if already opened) on double-clicking to the diagram node in diagram file content sub-tree provided to the Project Explorer Eclipse view. Useful for the situation then several diagrams are stored in the same diagram file (see Basic support for diagram partitioning).

Mapping Model Visual Editor

Diagram editor that uses GMF mapping model as domain model. In other words now you may design diagram editor in diagram editor ))) You need org.eclipse.gmf.map.editor plugin.

GMFMapDE.png

2.0 M4

2.0 M5

2.0 M6/RC0

Back to the top