Re: [mdt-papyrus.dev] Refactoring of VisualID in diagrams

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

Sounds good. Perhaps there is some underlying commonality with:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=485439

Beware: producing unique ids for Templated Operations of Templated Classes with recursively Templated Parameters is non-trivial.

     Regards

        Ed Willink

On 19/01/2016 10:42, NOYRIT Florian wrote:

Dear Papyrus contributors,

 

Maged is working on refactoring the visualID used in the various diagrams.

 

The first step that consists in using String based VisualID instead of int has been merged yesterday. Though it is mostly internal machinery, this change may impact tools external to Papyrus.

 

The second step consists in unifying the visualID among the various diagrams available in Papyrus and to move to “meaningful names”. Instead of “2008” (the visualID of a Class in the Class Diagram for the connoisseurs) it will be “Class.Shape” or alike.

As this second change will be much more impacting, appropriate migration facilities will be delivered to both migrate existing diagrams and to help migrating existing code.

 

You may find details on https://wiki.eclipse.org/Papyrus/Neon_Work_Description/Improvements/Notation_Unification and you may contribute remarks and requirements there too.

 

Best regards.

 

/Florian & Maged

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev