Bug 170437 - [Model Sync] Coloring of changed packages, classes and methods
Summary: [Model Sync] Coloring of changed packages, classes and methods
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-01-15 04:27 EST by Peter Repinc CLA
Modified: 2019-09-06 16:18 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Repinc CLA 2007-01-15 04:27:26 EST
Instead of an small icon when a class/file or package is changed it would be nice to be able to display the name of package/class in a different user defined color. It would also be nice, if the text editor and/or "member view" (or any other view that displays members) would also be able to display changes in used defined background/text color depending if the method has been changed or not (with the ability to define to track changes from local history or from the latest "checkout").

See example from SmallTalk: http://img453.imageshack.us/my.php?image=examplelt7.png
Comment 1 Martin Aeschlimann CLA 2007-04-24 05:25:52 EDT
You can already color files with outgoing changes on 'Team > CVS > Label Decorators'.
Comment 2 Michael Valenta CLA 2007-04-24 08:20:18 EDT
I believe there is enough functionality available in the model support to do this.  It's too late in 3.3 to investigate so perhaps in 3.4. If someone wanted to contribute a patch, I would be happy to provide pointers on where to look (at least from the Team side since I don;t know much about the Java Outline view or editor).
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:18:45 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.