Bug 128031 - [Workbench] Identify workspace that is open somewhere in interface
Summary: [Workbench] Identify workspace that is open somewhere in interface
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0.2   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-02-15 09:53 EST by Glenn Remar CLA
Modified: 2009-08-30 02:07 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 Glenn Remar CLA 2006-02-15 09:53:00 EST 
At work we treat each release as a different workspace in different directories.  The only way to tell what release we are working on is to look at one of the files in the workspace and see what directory it is in.  Is there any easier way to see what directory you are working such as putting it in the title bar, etc?
Comment 1 Tod Creasey CLA 2006-02-16 07:44:14 EST 
Do you mean a different project (a workspace is the root of all of your files).
Comment 2 Glenn Remar CLA 2006-02-16 10:09:25 EST 
I did mean workspace.  Is there anywhere in the interface that displays the physical folder that the workspace root is?  If it could not be added to the title bar or Navigator View, could there be a hover for the physical directory for a project?

(In reply to comment #0)
> At work we treat each release as a different workspace in different
> directories.  The only way to tell what release we are working on is to look at
> one of the files in the workspace and see what directory it is in.  Is there
> any easier way to see what directory you are working such as putting it in the
> title bar, etc?
Comment 3 Tod Creasey CLA 2006-04-15 15:25:15 EDT 
You can use -showLocation
Comment 4 Denis Roy CLA 2009-08-30 02:07:19 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.