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

Difference between revisions of "Papyrus/Mars Work Description/Improvments/Diagram synchronization support"

(Created page with "This page describes the work that will be performed on Papyrus Mars to support synchronization. There are at least 2 kind of synchronization to implement in Papyrus: * diagra...")
 
Line 8: Line 8:
 
There is also an implementation of this framework in the tables, it could be interesting to see how it is implemented and how the 2 synchronizations mechanism could rely on the same framework.
 
There is also an implementation of this framework in the tables, it could be interesting to see how it is implemented and how the 2 synchronizations mechanism could rely on the same framework.
  
Here is a bunch of requirements, to be developed more extensively (taken from model in plugin org.eclipse.papyrus\plugins\uml\diagram\org.eclipse.papyrus.uml.diagram.synchronizeview)
+
Here are some requirements, to be developed more extensively (taken from model in plugin org.eclipse.papyrus\plugins\uml\diagram\org.eclipse.papyrus.uml.diagram.synchronizeview)
- The synchronization should be local to an element or for the whole diagram
+
* The synchronization should be local to an element or for the whole diagram
- The synchronization mechanism should alter the performances only in a reasonable way
+
* The synchronization mechanism should alter the performances only in a reasonable way
- The synchronization should take into account all features of Papyrus: drag'n'drop, copy and paste,  
+
* The synchronization should take into account all features of Papyrus: drag'n'drop, copy and paste,  
- The synchonization should be linked to CSS framework
+
* The synchonization should be linked to CSS framework
- The synchronization should share its framework with the table framework
+
* The synchronization should share its framework with the table framework
 
=== Diagram synchronized on another diagram ===
 
=== Diagram synchronized on another diagram ===

Revision as of 04:40, 16 February 2015

This page describes the work that will be performed on Papyrus Mars to support synchronization. There are at least 2 kind of synchronization to implement in Papyrus:

  • diagram content synchronized on semantic model content, called canonical mode
  • diagram content synchronized on another diagram.

Canonical mode, a.k.a. diagram synchronized on semantic model

This mode has already been partially implemented in Papyrus Luna, but never deployed as there were not as many tests as expected to be sure the feature would not slow down or even corrupt the tool. The work on canonical model could be based on that first implementation. see org.eclipse.papyrus\plugins\uml\diagram\org.eclipse.papyrus.uml.diagram.synchronizeview for that initial implementation There is also an implementation of this framework in the tables, it could be interesting to see how it is implemented and how the 2 synchronizations mechanism could rely on the same framework.

Here are some requirements, to be developed more extensively (taken from model in plugin org.eclipse.papyrus\plugins\uml\diagram\org.eclipse.papyrus.uml.diagram.synchronizeview)

  • The synchronization should be local to an element or for the whole diagram
  • The synchronization mechanism should alter the performances only in a reasonable way
  • The synchronization should take into account all features of Papyrus: drag'n'drop, copy and paste,
  • The synchonization should be linked to CSS framework
  • The synchronization should share its framework with the table framework

Diagram synchronized on another diagram

Back to the top