Community
Participate
Working Groups
Currently, when you use the compare action between 2 element provided by the ModelExplorer, this action opens a new CompareEditor. It is not a correct behavior for several reason : - we are comparing elements of the model, so we should stay in the PapyrusEditor to do the comparison - if we open a new editor, we should use a new EditingDomain, it will be a problem because the edited EObject are already owned by the PapyrusEditingDomain - it don't will correct to use the same EditingDomain in 2 Eclipse Editors For these reasons, Papyrus should provides a nested CompareEditor to do this action. Which should be the behavior of this editor ? - persistent : like Diagram and Table -> I think it is not the correct behavior, the compare action is not a representation of the model. - volatile : not visible in the ModelExplorer, in the HyperLinkShellEditor aso..., when you close it, it disappears when you close Papyrus or Eclipse, it disappears too. - a 3rd behavior should be possible : when you close if, it disappears, but it is stored when you close Papyrus or Eclipse, that is to say, this editor is always here when you re-open Papyrus.
In R7215 : share the new plugin oep.infra.emf.compare.instance on the SVN. This plugin provides the model for the content of the CompareEditor.
In R7766 : commit changes on : - oep.infra.emf.compare.common - oep.infra.emf.compare.ui - oep.papyrus.uml.compare -> open Compare as embedded editor in Papyrus -> Synchronize its tabs name with : - name change on one of the compared element - customization change for the editor -> correct some bugs using EditorUtil.getActiveDiagram : - at the beginning we sometimes we get the PapyrusCoreDiagram -> corrected -> warning, GetDiffElementLabel is called too early (when the new editor is not yet opened, so we use the bad LabelProvider during the opening of the editor -> corrected during the setFocus of the editor
In R7918 : UML Compare File : now inherits from EMFCompareEditor Nested Compare Editor : corrects the contents displayed content merger viewers : we don't display the full resource, but only the compared elements
In R7943 : assure that the Nested UML Compare Editor is removed from the resource when we close it. (Done By CloseEditorTriggerListener)
R8303 : Commit the test plugin oep.uml.compare.tests
(In reply to comment #4) > In R7943 : assure that the Nested UML Compare Editor is removed from the > resource when we close it. (Done By CloseEditorTriggerListener) We should write a test for that
We abandonned this feature. I close the bug
