Community
Participate
Working Groups
Actually label decorations for warning/errors/cvs conflicts are only represented by a small icon or a ">" sign. Sometimes it's really difficult to see such small labels, expecially if you have more decorations. Allowing users to select a backgroung/foreground color for labels will really improve user experience. A similar feature is currently implemented in instantiations codepro, but only using custom views (they call them package explorer+, resources+). It sound strange to reimplement views only to add a (also if useful) background color... it would be really great to have a support for this feature available in the base UI framework, so that could be used in any view. This is a screeshot from codepro colored view: http://www.instantiations.com/codepro/ws/docs/images/package_explorer_plus_view. gif And the preference page where users can choose colors: http://www.instantiations.com/codepro/ws/docs/images/preferences_browsers.gif This would be a nice addiction in the new [workbench]->[colors and fonts] preference page just added with the new look'n feel.
I'm all for nice addictions <g>.
Actually, once the ILightweight decorator implements IColorProvider and IFontProvider we could possibly allow customization of these for the CVS decorator. Until then, since our decorator is an ILightWeightDecorator, we can't do anything about it.
We won't be doing this in the 3.0 timeframe.
Marking later
Reopening now that 3.0 has shipped
Related to Bug 61869
This is actually not that hard. We would need to change IDecoration to also allow colours but as no one is meant to implement that this would not be a breaking change. Likewise IDecoratorManager could add a getColorProvider method and a getFontProvider method which would not break anyone. Jean-Michel is this something you would do in the 3.1 timeframe?
This has been released to HEAD - it is now possible to decorate colours and text in an IDecoration. Please note that this API is expermental and may be adjusted during the viewer work in 3.1.
Also if the APIs are been released I still can't see any of the existing decorator make use of this new feature (which actually was the subject for this rfe). I expected to see an option to choose background/foreground color for dirty/new files for team providers in preferences->team->CVS->label decoration and an option somewhere to choose background/foreground color for files with warnings or errors in the package explorer (something like the screenshots provided). Do I have to open addictional bug report for those? To which component should I assign them: team, cvs, jdt ui?
I'll move this to Team as they will provide the CVS support (sorry - should hav renamed this).
You can know configure the font/color for ignored and outgoing resources. Moving to JDT to consider something similar for markers in the packages view.
Tod, how is arbitration done when multiple label decorators want to set colors/font? Is it just random which one is used? I think there should be some sort of defined prioritization or "merging" of colors, such that we can ensure that e.g. error color is always more important than team color. Note that the old decoration types allows multiple decorations for the same element: text can only be added, but not replaced; images should only be small overlays and let the rest of the icon alone.
We don't intend to change the suffix/prefix addition algorithm - replacing the text was not something people wanted to happen whenthey had no control over it due to a contributed decorator from another plug-in. If there is conflict between the decorator and the font or color provider of the viewer the decorator takes precedent. If two decorators are trying to do the same thing or decorate the same quadrant we do not currently do any conflict resolution. See Bug 36007
BTW you could add a color or font provider to the packages view and then allow the CVS decorator to override it when they are on as the decorator takes precedence.
Closing are there is nothing else to do on our part.
Verified that our support is in M3 (thanks for moving it back - I missed it in my test pass).
