Community
Participate
Working Groups
The ModelExplorer is an infinite Tree based on the EMF Facet customizable tree. Thus, the traditional exploration algorithms cannot browse correctly this tree. We should define a specific navigation strategy, and reuse it in each implementation of the ModelExplorer. Moreover, the navigation strategy should not rely on a ViewerFilter. There are two distinct cases : - Display the Tree to let the user browse it : The Tree is infinite. - Automatically search for an element in the Tree : We should have an Heuristic to find the most pertinent location (As the same element may be displayed more than once). Containment references, specific "import" references (For external resources), Facet references... In some cases, we want to display the Tree as a finite Tree. In this case, we should be able to reuse the automatic search algorithm to display the Tree. In all cases, we want to be able to remove some elements from the tree (For example when we are only interested in some specific EClasses). In such a case, the tree pruning should not rely on a ViewerFilter.
In Eclipse Papyrus Oxygen: - we have now a filter included into the browser - the tree is filtered using facets (Papyrus EMFFacet) I think this bug can now be marked as closed fixed.
