Community
Participate
Working Groups
I have an Ecore model with packages. There are elements from different packages that are related to each other. With the Ecore diagram editor : - I can create a diagram for the top level package and it will display my root element with all defined packages. But the diagram will not display the relationships between my root element and other elements from these packages. - I can create a diagram for each package and it will display all elements defined within this package. But the relationships between one of these elements and other elements from another package will not been displayed.
You can use shortcutting functionality to visualize this kind of relation. For example, if you have Ecore diagram example and you'll create a package1/Class1 and package2/Class2 you can add Class1 and Class2 as a shortcuts to the main package diagram and draw generalization link - it will be visualized on diagram. Currently the problem is: such a links will not be updated correctly. For example, if such a link existis in the model and then you add shortcuts to Class1, Class2 - corresponding link will not be visualised on diagram. Same with removing link from the model. So, this request is mostly request for a CanonicalEditPolicy implementation and could be re-formulated like this: CanonicalEditPolicy should refresh links to/from shortcuts.
Thanks for the reply. The shortcut feature works and the display of relationships seems to work almost fine : - When I add the shortcut to some elements (e.g. A1 and A2 from package A), after a save and reopening of the diagram, the relationships are displayed correctly (relationships to A1 and A2 are displayed). - Nevertheless, I cannot mask recursive relationships of A1 and relationships between A1 and A2. I want to see these relationships only in the diagram of package A. PS : The shortcut feature is only accessible from the diagram's contextual menu ! It should be included in the standard toolbar like the zoom and note elements.
Created attachment 49598 [details] Very strange behaviour with 2.0M1 I use GMF2.0M1 with the attached TestGMF.ecore file and I had very strange behaviours. If I initialize an ecore diagram for the Organization package, everything is OK. Now I initialize an ecore diagram for the main package : only the Project class and the Organization package are seen. Then I create shortcuts consecutively to the Package, SpecificationPackage, RealizationPackage, ElementPackage from the Organization package : - DUPLICATE inheritance relationships are seen between SpecificationPackage and Package - DUPLICATE relationships are seen for the "innerPackages" recursive relationship of SpecificationPackage - relationships between Project, RealizationPackage, and ElementPackage are not seen.
Since GMF 2.0 M6 was released April 5, 2007, doing a bulk move of all open Bugzillas currently on M6 to 2.0 M7. Owners will need to access if the issue really is targetted for 2.0 M7.
Moving to the next version.
Please consider fixing the issues described in the comment #3. These are not enhancements but real bugs.
Moving to 2.0.1 to investigate existing problems.
Problem described in comment #3 was fixed in 2.0.2 maintenance stream. Moving requiest to the next version. Following issues are not fixed: - Problem with updating these links - link to/from the shortcut will be created only on next update invocation (not togetehr with the shortcut). - It should be possible to hide/show links - Optionally display "create shortcut" action in a toolbar (add corresponding palette entry if it was specified in .gmftool model).
Moving to the next version
(In reply to comment #10) > Moving to the next version I just discovered the Ecore Tools sub-project from the EMF Technology project. If this project is the standard EMF diagram tool (it is included in the Ganymede Modeling package), enhancements to the Ecore sample diagram editor is no more relevant.
I am interested in this functionality as well, in particular automatically rendering relationships between shortcut elements referenced within a root node. In order to implement it on GMF 2.0.1 I manually added an EditPartProvider for the particular view that would programatically create the shortcut elements if it found they were not currently rendered. Until this is implemented, my code is described at http://www.jevon.org/wiki/GMF_Code_Samples.
[GMF Restructure] Bug 319140 : product GMF and component Samples was the original product and component for this bug
