Bugzilla – Full Text Bug Listing
| Summary: | Old Fast View bar hogs space which FVB trim can't use | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kevin McGuire <Kevin_McGuire> | ||||
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | Keywords: | helpwanted | ||||
| Version: | 3.3 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Kevin McGuire
Created attachment 67332 [details]
Screen cap showing extra space which new FVB trim can't use
Kevin, the space is there to provide a drop target into which clients can drag views. Do you have suggestions on what we might do ? I'll mark this for 3.4 so we can revisit it next cycle. There are two things going on: 1. Its more space than it needs for a drop target 2. There is no visual indication of where that drop area stops. I am curious if people use it in this anyway, since (2) makes it somewhat hit or miss. Since this is our old fast view support which we are trying to move away from, could we make the drop area smaller? We have the "bar+" icon to create the fast views, maybe its enough as a drop target? I can take a look. Are you proposing this for 3.3 or can it wait? If it was a simple fix to snug in the drop area we should consider for 3.3. The thing is, this was never a problem in past because you generally didn't move things around in the trim. But with the cool new min/max support we'll be seeing a lot more of this and in Jazz in particular. Lets decide once we know what the code change looks like. Btw, a more complex solution (not for 3.3) is to provide some kind of "tray" look to the old fast view area, so that the drop area can be seen. I mention it only to enumerate the possibilities but don't actually like that solution because for one it draws more attention to something we want to downplay and for another could create some confusion with the new FVBs. That's why I removed the 'Outline' affordance in 3.2...;-). At first glance I'm not sure how the extra area is actually allocated (perhaps it's the minimum width of a ToolBar?). I'd be glad to do this in 3.3 if I can get to it but I don't have cycles to dig too deep yet (I'm currently fighting with legacy presentation support issues). 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. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |