I recently read an article stating that the Eclipse Package Explorer and Outline view are wasted space. Mylyn also recommends minimizing or closing the Outline view. Eclipse makes it really easy to make views go away with fast views and minimizing tab groups. An in-place Outline can be activated with Ctrl+O. All of these focus on providing maximum screen real-estate for editors. While these paradigms work really well for many editors, some editors are designed to make use of the Outline view and Properties view as integral parts of the editor. So how does a tool designer resolve this tension between editor styles?
Imagine that a developer is switching from a Java source editor -- where views should be minimized -- to an editor that makes use of the properties view and outline view. When switching back and forth the developer is going to feel friction. To try this out, try using the XSD editor in Eclipse with the properties view.
Enter the editor-controls-view paradigm.
For editors that require the outline and properties views, the editor 'restores' the views to their visible state when the editor gains focus. When such an editor loses focus, the views are minimized to their iconized state. Eclipse could support this editor-controls-view paradigm by allowing editors to declare their affinity with specific views.
This solution provides an optimal use of screen real-estate for both editing scenarios without requiring the developer to take additional action every time she switches editors. It also does not require the developer to switch perspectives, which is a heavier solution to the same problem.
- Your Team Might Not Be As Effective As You Think
- Faster Feedback Loop on Code Reviews
- Surfacing Abstractions in Code Reviews
- Architecting for the Value Stream
- Article Index
subscribe via RSS