Bug 54952 - [EditorMgmt] Show fully quailfied name of current edit-module, in titlebar
Summary: [EditorMgmt] Show fully quailfied name of current edit-module, in titlebar
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-16 05:09 EST by Leif Erik Larsen CLA
Modified: 2019-09-06 15:31 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Leif Erik Larsen CLA 2004-03-16 05:09:47 EST 
When I use the Eclipse IDE for my Java development I strongly miss an easy way
to see the fully qualified name of which Java class that I have open in my
current edit-window. For instance in JBuilder, this is always shown in the
titlebar. Eclipse shows just the short classname it self in the titlebar. Can
you please add an option to display the fully qualified class name in the titlebar?
Comment 1 Michael Van Meekeren CLA 2006-04-21 13:19:30 EDT 
Moving Dougs bugs
Comment 2 Susan McCourt CLA 2009-07-09 19:04:07 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Boris Bokowski CLA 2009-11-17 13:05:35 EST 
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 4 Remy Suen CLA 2009-12-12 16:58:12 EST 
(In reply to comment #0)
> Eclipse shows just the short classname it self in the titlebar. Can
> you please add an option to display the fully qualified class name in the titlebar?

We currently show the path to the file relative from the workspace. Per Java package specifications, this would include the package name, such as testProject/src/org/eclipse/ui/Test.java. Is this sufficient for you, Leif?
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:31:51 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.