Bug 149349 - [IDE] Way to "highlight" a Workspace configuration.
Summary: [IDE] Way to "highlight" a Workspace configuration.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-06-30 20:02 EDT by Gabriel Klein CLA
Modified: 2019-09-06 16:11 EDT (History)
0 users

See Also:


Attachments
Show the example of such a GUI (83.26 KB, image/jpeg)
2006-06-30 20:16 EDT, Gabriel Klein CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriel Klein CLA 2006-06-30 20:02:32 EDT
I work with multiple workspace.
Each of these workspace represents a "release" of our applications.

For exemple I have "MyApplication Release 1.5 - Geneva", then "MyApplication Release 2.0 - Zurich", then "MyApplication Release 3.0 - Paris".

Sometime when I fix a bug on the release 1.5, I have to fix this bug on release 2.0 and 3.0. So I work with multiple instances of Eclipse open (and with a similar layout).

It would be nice to have a way to differentiate these differents layout. For exemple in the "title of the windows", a "logo" that is included in the workspace configuration, a "title" in the background of the Navigator or Explorer windows.
Comment 1 Gabriel Klein CLA 2006-06-30 20:16:32 EDT
Created attachment 45631 [details]
Show the example of such a GUI

Example
Comment 2 Gabriel Klein CLA 2006-06-30 20:24:16 EDT
Similar but different to https://bugs.eclipse.org/bugs/show_bug.cgi?id=131566
Comment 3 Boris Bokowski CLA 2006-07-05 07:07:14 EDT
For now, the only feature addressing this is the -showLocation command line argument.
Comment 4 Susan McCourt CLA 2009-07-15 12:07:16 EDT
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:11:10 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.