Community
Participate
Working Groups
I'm currently trying to make the Model Explorer View fully functional with EMF Facet. For now, only UML elements display use EMF Facet. However diagrams are displayed with a custom IContentProvider. So I would like the diagrams to be display with EMF Facet. To do that I going to use the "Facet" part of EMF Facet. That is to say, add a "virtual" reference on some UML elements which would references the diagrams they contain. This is for now just a try so if anyone has some ideas this topic is open to discussion. (This refactoring has been needed after some work on "Collaborative work" in MDT Papyrus).
*** Bug 335424 has been marked as a duplicate of this bug. ***
Coming soon...
To do so the following changes would be necessary in the code: -> In org.eclipse.papyrus.core: Changes in the EditorIcons mechanism. It's now possible to get the URI of an icon provided by MDT Papyrus -> In org.eclipse.model.explorer Change in the double click listener (to correct the bug 335424) Change in the ContentProvider. The diagram will not be handled as children of UML element (virtually added by the content provider). This relation will be now represented by a facet. -> In org.eclipse.papyrus.uml.modelexplorer Customization on the facet: -> Customization of notation.diagram elements -> Customization of the faceted elements
To do so the following changes would be necessary in the code: -> The property tester isDiagram will now return yes if the element is an IAdaptable of Diagram -> The Abstract Common Handler will now handle IAfaptable element
The correction of this bug was committed on the: -> trunk - Commit number : 5608 -> branch 0.8.X - Commit number : 5600
In R5714 (branch) and R5715(trunk) : refactoring on oep.uml.modelexplorer to avoid duplicated code between this plugin and oep.table.modelexplorer.
Hello, The oep.uml.modelexplorer.queries.IsReadOnly query is not totally satisfying, as it brings a regression. When you browse a UML Model directly from the Project Explorer, the model isn't opened in an Editor, and doesn't have an EditingDomain. When the isReadOnly query is called, it throws an exception. This query should probably return a default value when the UML Element doesn't have an Editing Domain (I don't really know if it should be true or false...) The problem doesn't seem to occur with the other queries.
I'm looking into it today.
fixed and commited (branch only, I didn't have the time to backport the whole commandStack/read-only thing to trunk yet).
In R6008 & R6191 : change the query getContainedDiagrams into GetContainedDiagrams.
In R6247 : Undo the previous classpath modification, in order to compile correctly the query GetOwnedDiagrams.
In R6282 : modify the queries in order to avoid an Exception, when the queries are loaded in a context which is not a Papyrus Context.
In R6283 : remove unused dependencies
Merge with trunk in R6286
I suppose that this bug can be marked as closed fixed. If you don't agree, don't hesitate to reopen it.