Bug 173735 - [Presentations] Better tab layout on java editor
Summary: [Presentations] Better tab layout on java editor
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-02-10 04:01 EST by Keith Whittingham CLA
Modified: 2019-09-06 15:36 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Keith Whittingham CLA 2007-02-10 04:01:26 EST
I like to have as many file names in the editor visible as possible but a lot of space is wasted with the file extension and the close icon. Currently the top of the editor window looks like this...

[J] Abc.java [x] \  [J] Def.java [x] \ [J] Ghi.java [x] \ [=] Xyz.uvw [x] \

Since the icon tells me it's java and if I mouse over the icon it could change to a close tab icon, the you could do away with the close icon and hide the file extension for file types with a iconized extension and show a tool tip on the remaining icon that says "Close xxx/com/whatever/Def.java so the file can still be idenfited and you have

[J] Abc \  [J] Def \ [J] Ghi \ [=] Xyz.uvw \

Improving the amount of file names visible by 70%...
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:31:11 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.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:36:29 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.