Community
Participate
Working Groups
I believe it will be very convenient feature to have kind of "fish eye" feature for Eclipse views. Imagine that you can fold, shrink and expand each view... but whithout dragging split bars between views. The idea behind this is that Eclipse should remeber sizes for active and passive view state and change it authomatically when view is activated. Actually it could be a good addition to a "Fast View" feature. Other convenient improvement will be to allow to expand or shrink view size without dragging its borders (e.g. use something like right-click-drag, or ctrl-click-drag).
The new look allows views to be collapsed to their titlebar.
Nick, that is sound interesting. However I believe that my idea have a better flexibility. Basically the same effect will be achieved if you resize neighbours of that inactive view, so that inactive view will only show its titlebar. Because inactiev size and active size are saved independently, view vill restore size upon activation. Another interesting feature will be to temporary restore active size on mouse over event (probably with some keyboard modifier, e.g. Ctrl-mouse over). By the way, there are another somehow related request, that is asking for the feature to hide a view title. http://bugs.eclipse.org/bugs/show_bug.cgi?id=45109
Any chance to get this feature implemented in 3.1 release? Thank you.
Nick, can you please give me a hint how to listen on view events such as get/lost focus and resize/move and also how to programmatically resize area of the active view? Thank you in advance.
Eugene, the UI team has no plans to investigate this for 3.1. If you'd like to experiment with this on your own, here are some pointers. Resizing views: there is an internal method WorkbenchPage.resizeView(IViewPart part, int width, int height) which can be used, but it has some issues and is not ready to become API. See bug 51580 for more details. Tracking part activation: use IWorkbenchPage.addPartListener(IPartListener) and implement IPartListener.partActivated(IWorkbenchPart). See also IPartListener2. For hiding the view titlebar, this cannot currently be done after the view has been created, but the perspective can add a view as a standalone view (other views can't be docked with it) and specify that it should have no title. See IPageLayout.addStandaloneView(...). For tracking resize and move, there is currently no workbench API for doing this. When a part is activated, you could get its internal PartPane object via: ((PartSite) part.getSite()).getPane() and then get the pane's control and hook a n SWT ControlListener on it. Note that most of the above is talking about UI internals, which may change in the future without notice. However, it may be enough to allow you to prototype something.
Great. Thanks a lot Nick. The only question left is how/where to persist two current active and current inactive sizes for all views? Any suggestions?
Look at the LayoutPart hierarchy. Probably should keep the sizes in PartStack or ViewStack, since the size is really a property of the stack (folder), not the view itself. ViewPane is 1:1 with the view and is shared across multiple perspectives in the same page if they contain the same view, whereas the PartStacks are created separately for each perspective. PartStack also has saveState/restoreState for persisting state between sessions.
Reassigning bugs in component areas that are changing ownership.
Eugene, are you still planning to contribute something like this, or can I close the bug?
It is on my very long todo list and not too far from the top. Please keep it open for now.
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.
