Community
Participate
Working Groups
It will be good enhancement to be able to decorate Part's just like any Tree or Table Item. Decorating Parts will help the user identify where he/she should look at for his/her immediate attention.
I'm not clear on what you're suggesting. Can you give an example?
Created attachment 72434 [details] decoration support for part title Red ovals show what we need to decorate. Red square shows what we already support.
The decoration facility is used for more than just error markers. Are you only requesting error markers for part titles? Note that editors are currently already decorated with error markers in their tab titles (but views are not).
This is a pretty big feature. We would need for it to make it to the plan for us to support it.
We have an RCP application which contains some tools for Collaboration between members. (http://www.collaber.com) Each tool will be a Workbench Editor. I want the decoration support to show how many members are actually working in that tool at that time. I am sending another attachment to show my exact requirement.
Created attachment 72556 [details] what exactly is needed I know it is very very big feature. And not possible in in 3.4 or 3.5 But if I have decoration feature, then I can use overlay and label decoration to show the same information. And I want to know if I can contribute to the development of this feature in anyway.
If it is an RCP app you are doing you don't need us. Just write yourself a custom presentation. The presentation controls how the tabs are rendered and you can do the custom work there. it is fairly simple if you are just solving the problem for yourself. This is't a priority for us right now so we likely won't have a lot of cycles to give you for integration into the SDK.
Oleg is now responsible for watching the [Decorators] category.
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.
