Bug 497112 - Evolution of editors state (dirty)
Summary: Evolution of editors state (dirty)
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 4.0.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-06-30 11:43 EDT by Axel RICHARD CLA
Modified: 2016-07-01 03:57 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel RICHARD CLA 2016-06-30 11:43:51 EDT
Today, if several editors (diagrams) from the same session are opened, then an action in one editor (diagram) will make it dirty if it changes the corresponding semantic model or if it changes the diagram itself. Furthermore, all others opened editors will become dirty too.

I understand the technical reasons for such a behavior (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=497080)

From a strictly user point of view, I think only the opened editors that have been modified by the user action should become dirty.
If the user action only change the semantic model, then may be the semantic model should become dirty in the model explorer.

An alternative solution would be to only set the dirty state to the project that contains the semantic model and the aird file that contains the diagrams, not to the editors.

That are just ideas, I don't pretend this is the way the tool should evolve.
Comment 1 Laurent Fasani CLA 2016-07-01 03:35:17 EDT
Thanks for your detailed enhancement submit.
We agree that it would be an interesting improvement.
Nevertheless, the specification may be difficult to define and the change will be very impacting. 
We have currently not planned to work on it in the following releases.
Comment 2 Cedric Brun CLA 2016-07-01 03:57:43 EDT
For the record, Bug 493367 and Bug 494766 are going into this direction by offering the possibility to decouple the representations from the ResourceSet which might then get their own dirty state lifecycle.