Bug 76888 - [Presentations] Hitting the minimize button on a view collection is pointless when column tiled
Summary: [Presentations] Hitting the minimize button on a view collection is pointless...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0.1   Edit
Hardware: All All
: P5 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on: 58945
Blocks:
  Show dependency tree
 
Reported: 2004-10-23 18:41 EDT by Gregory Gerard CLA
Modified: 2019-09-06 16:13 EDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregory Gerard CLA 2004-10-23 18:41:55 EDT
I have two major column groups on my screen:
======================|============================================|
PE\Hierarchy\Outline-+|Foo.java\Bar.java\Baz.java\blah.properties-+|
<<Package Explorer    |package stuff;                              |
  Tree Here>>         |public class Foo {                          |
                      |...                                         |
======================|============================================|

Hitting the minimize (the '-' in the ASCII art above) just make the package
explorer tree go to all white. While consistent, this does the user nothing as
the source code on the right can't grab any more space.

Feature request:
On minimize, draw the tabs vertically along the side so that the contents of
other views can grow.
Comment 1 Stefan Xenos CLA 2004-10-26 12:14:22 EDT
This is partially fixed. In the 3.1 stream, stacks will shrink horizontally when
minimized.

The layout code could now handle the tabs being drawn vertically as you
describe. However, I haven't made this change because I couldn't think of a way
to actually draw the CTabFolder vertically (CC'ing veronika in case she has any
seeds of wisdom).

I tried replacing the CTabFolder with a vertical toolbar when it is minimized as
a column. That was quite effective at saving space, but it looked... well... stupid.
Comment 2 Stefan Xenos CLA 2004-10-26 12:14:46 EDT
BTW, this is a dupe, but I'm leaving it open because I can't find the original. :-)
Comment 3 Tom Hofmann CLA 2006-04-19 10:47:26 EDT
Too bad this does not have high priority... IMO, nice minimization behavior is one of the one most annoying missing features of the workbench.

- see bug 97124 for a dup
- see bug 88239 comment 7 for a mock up
- see bug 107819 for an idea on how to make it look even better
Comment 4 kgrot CLA 2006-04-19 12:13:22 EDT
I agree.  We have been requesting something like this since late 2004.  One of the most common types of UI feedback that we get in usability tests is that the workbench is complex and overwhelming, and I think this would help address that problem.  
FYI, here's one more related request: 30780
Comment 5 Paul Webster CLA 2006-04-19 13:33:23 EDT
It's not that it doesn't have value, but we're at the end of 3.2 and bug fixing is a priority.

Anything I'm not working on now is P4

PW
Comment 6 Tom Hofmann CLA 2006-07-07 10:35:38 EDT
Adding minimize discussion group.
Comment 7 Paul Webster CLA 2006-09-13 10:58:12 EDT
3.3 will include a new "minimize" behaviour, which will minimize stacks to the outside trim and reclaim the space for the views/editors that are still visible.

PW
Comment 8 Paul Webster CLA 2006-09-28 11:00:34 EDT
There are currently no plans to work on this feature.

PW
Comment 9 Denis Roy CLA 2007-06-22 09:32:43 EDT
Changes requested on bug 193523
Comment 10 Eclipse Webmaster CLA 2019-09-06 16:13:45 EDT
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.