Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320258 - Color coded source tabs
Summary: Color coded source tabs
Status: CLOSED DUPLICATE of bug 179453
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-19 09:34 EDT by Eclipse Webmaster CLA
Modified: 2010-07-29 07:23 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eclipse Webmaster CLA 2010-07-19 09:34:12 EDT
From the Webmaster inbox:

>I found that when opening old and new version of same source classes, you cannot >be sure which src belong to which project unless you click on it. A better >solution is to color the name of the source in the tab with different color for >each project so without pressing on the tab you know   which is old code and >which is new code.
>In project setting you can select color schema for the project.

-M.
Comment 1 Remy Suen CLA 2010-07-19 09:52:05 EDT
It is difficult for us to gather requirements without being able to communicate with the person in question. Does this person's email address correspond to a bugzilla account?
Comment 2 Eclipse Webmaster CLA 2010-07-19 10:07:17 EDT
No.  I sent them a link to the bug so they could follow the discussion and post as required.

-M.
Comment 3 Adi Lev CLA 2010-07-19 11:17:15 EDT
Any question can be forward to me.
The suggestion is to color tab name of source with a color schema that can be set on project property, e.g, on editor set tab background and foreground colors.
This will help users who edit old and new version of source to know which is old and which is new without clicking on the tab.
Comment 4 Prakash Rangaraj CLA 2010-07-29 06:36:48 EDT
Remy,
   Any idea of where this bug belongs to?
Comment 5 Remy Suen CLA 2010-07-29 07:19:01 EDT
(In reply to comment #4)
> Any idea of where this bug belongs to?

Pretty hard to say. It'd probably require some API additions to editors (or at least a new constant for a property string key). And then some stuff will need to be done in the IDE side. Make changes to the property page and then have editors/editor inputs set that value. This is certainly a cross-component request.

Setting individual tab colours aren't supported yet by SWT (see bug 280969 for the foreground issue) unless we spin our own renderer (which I doubt we will).
Comment 6 Remy Suen CLA 2010-07-29 07:23:58 EDT
Actually, I guess this is pretty much a duplicate of bug 179453.

*** This bug has been marked as a duplicate of bug 179453 ***