Community
Participate
Working Groups
Do we want to provide full Tree editor support? This isn't in the model design as it stands, but I think it would be important for EMF modeling community. It's also somewhat a good step on the way to support of diagram editors.
Do tree editors use JFace StructuredTreeViewer controls? If so, it should be straight forward to add focusing once the structure bridge is in place.
(In reply to comment #1) > Do tree editors use JFace StructuredTreeViewer controls? If so, it should be > straight forward to add focusing once the structure bridge is in place. They're TreeViewers with a structured selection. However, this isn't really just about tree editors per se. there is a whole abstraction layer for this through ItemProviders. Also, because the same children providers can be used in many other contexts it might make sense to work with the item providers directly. There is a chance that this could actually get us a lot of the diagram editing bits as well. There could be issues with simply chopping out tree item children in the viewer itself as the EMF.Edit clients will be expecting a correspondence between it's model and what the user is presented with. OTOH all of this would require adapting existing editors whereas the simple tree approach would gloss that over. So it's not quite straightforward. I think at this point it makes sense to experiment a bit with both approaches. It may be that\ other projects have worked with model view filtering so I'll look for that as well. I've basically got the structure bridge wired so I'm starting to dive into this a bit now.
Jan, let me know if you're planning to take a whack at this. I'm looking at the 3.7 dependencies now.
*** Bug 351887 has been marked as a duplicate of this bug. ***
Removing as blocked for initial release options. This will be a very cool thing to do, but was never part of initial plan.
