Bugzilla – Full Text Bug Listing
|
Description
Celine Janssens
For information , I'm working on a specification document to have a clear overview about the state of art, the different concepts to change and maybe the side effects that could generate such modifications. This is mainly related to the Diagram; I rename the task and change the Component I propose that a consideration in this feature should be that, whereas profile applications can now be loaded and unloaded at any time while a diagram is open, the diagram must find another way to update its presentation to reflect the unloading of a stereotype than by removing the annotation/style/whatever that controls the display of that stereotype in the diagram. The situation currently is that some edit-policy removes the annotation that names the applied stereotype when the stereotype's profile application is unloaded. Consequently, when the profile application is later loaded again, the stereotype does not show in the diagram because now the annotation that presented it is absent. Hi Christian, The plan is also to display all stereotypes by default. Moreover, relying on NamedStyles gives an automatic support for CSS, which doesn't need to serialize anything. Finally, I think there is indeed no need to remove any information when un-applying a stereotype (So re-applying it later gives the same graphical results) All this (and more, probably) should be detailed in the spec document WARNING: this patchset contains 1321 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire WARNING: this patchset contains 1323 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire WARNING: this patchset contains 1315 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire WARNING: this patchset contains 1315 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire Gerrit change https://git.eclipse.org/r/41903 was merged to [bugs/457024-stereotypeDisplay]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=5ce8f39a038f850f366509f23647dd321aac17e5 WARNING: this patchset contains 1315 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire Gerrit change https://git.eclipse.org/r/42108 was merged to [bugs/457024-stereotypeDisplay]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=c0f8fe09c5b38e1b5b7aaafdd0afaaece7f2002c New Gerrit change created: https://git.eclipse.org/r/47340 New Gerrit change created: https://git.eclipse.org/r/47339 WARNING: this patchset contains 3899 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire Gerrit change https://git.eclipse.org/r/47339 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=2b11ad8627ef5d58a2ff5a90e7a577b192a75f9c Gerrit change https://git.eclipse.org/r/47340 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=db0a842e0e90d28754bfc88acd19743223515cc9 Can this bug be closed also? It seems the contribution has been merged Resolved in Release Mars 1.1.0 |