Bug 334742 - [breadcrumb] should never hide project and package information
Summary: [breadcrumb] should never hide project and package information
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-19 03:46 EST by Deepak Azad CLA
Modified: 2011-05-25 04:49 EDT (History)
2 users (show)

See Also:


Attachments
screenshot (28.30 KB, image/png)
2011-01-19 03:46 EST, Deepak Azad CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Deepak Azad CLA 2011-01-19 03:46:49 EST
Created attachment 187080 [details]
screenshot

The class name is visible in the editor tab, and you obviously know in which method/field you are in. What you do *not* know is the project and package information. (see screenshot)

It would be nice if in case of lack of space instead of the leading part, the trailing part of the breadcrumb is hidden. 

...at the very least there should be a preference to control this behavior.
Comment 1 Markus Keller CLA 2011-05-24 13:00:17 EDT
I agree that the class name is redundant in this case and could be compressed. But the current member is not always visible in the editor (think of a method or Javadoc that spans more than one page), so this info should stay.

The project is already visible in the workbench window title. The package and the file name are also there, but harder to parse.

Order of importance is IMO:
- enclosing members (except for main type in file)
- package
- project
- main type
- source folder / JAR / class folder

That's quite a jumpy list, and I'm sure others have other priorities. A separate preference page would also be overkill. But we could allow the user to set priorities in-place, e.g. by adding a context menu to the triangles or via drag-and-drop. The category of the last item that the user expanded/collapsed could be stored as the most/least important category (thus decreasing importance of the other categories).
Comment 2 Dani Megert CLA 2011-05-25 04:49:19 EDT
I personally never had an issue with that so far, but I'm working with a maximized workbench window and the Java Browsing perspective which gives the entire width to the editor.