Community
Participate
Working Groups
The fact that the Notation Views do not have a category attribue and they are too abstarct means we can not write generic code to hadle all labels or compartments on the diagram surface unless we write this code on the Edit Part level which is not possible in all cases, specially when the edit part are not there. This could be solved by adding a kind attribute to the View, the kind will be an enumeration of Shape,Label,Compmartment ..
Did we get this into the notational changes in 2.0?
I don't think so. This looks like a request for having Shape, Compartment and Label views in the metamodel. These views will simply implement interfaces common to shapes, labels and compartments. Is this correct, Mohammed?
(In reply to comment #2) > I don't think so. This looks like a request for having Shape, Compartment and > Label views in the metamodel. These views will simply implement interfaces > common to shapes, labels and compartments. Is this correct, Mohammed? This issue can be handled by 2 solutions 1- introducing the a kind enumeration in the notation meta model, then introducing an attribute on the notation View for the kind where the enumeration will be used 2- The second solution whihc is the better solution and it will open the door for other good improvmenets in the fututre is to introduce subClasses of the Node class for Lables, Compartments and so one. The only thing with this approach is that it will be a file format change
[GMF Restructure] Bug 319140 : product GMF and component Runtime Diagram was the original product and component for this bug
