Summary: | [ViewMgmt] More Flexible Nested Docking | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Jacob Robertson <pepblast> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P4 | CC: | eclipse, markus.kell.r, michaelvanmeekeren |
Version: | 3.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | incubator |
Description
Jacob Robertson
2003-09-05 13:59:50 EDT
Is there anything planned in this direction? No, there is nothing planned here at this time due to other priorities (see the 3.0 plan at http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_0.html) Is this even a possibility? We are now developing an RCP application, and this would go a long way towards making it usable for the end-users, as well as allowing us to create a more modular system. Right now we are trying to decide between using sash forms within views and using multiple views. We want to be able to layout the views in particular ways, but without a way to group views together, it becomes more work for the user to maintain them. On the other hand, if we just put all our composites into one master view, we lose the functionality that the ViewPart comes bundled with, like the max/min, toolbars, docking features, etc.. Sorry, the chances of this happening for 3.2 are slim given the overall project priorities. See the 3.2 plan at http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html The closest item on the plan is bug 106189, which mentions "workbench layout should be made more flexible and configurable". Reassigning bugs in component areas that are changing ownership. Remy is now responsible for watching the [ViewMgmt] category. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |