Community
Participate
Working Groups
Please add preview of the task context highlighters to the prefs page. It could be similar to the one used by Universal Label Decorations Plugin. http://www.jave.de/eclipse/labeldecorator/index.html
Under the root Mylar prefs page there is a table that lets you choose and preview highlighters using a color picker. Does that suffice? It could use some improvement, and should allow setting of RGB values...
I know about that table/configuration. However it is hard to see how choosen highliter will look like in the views. It would help if we'd have a small preview area that will show highlited and non-highlited nodes for selected higliter. The preview UI can be similar to the one at http://www.jave.de/eclipse/labeldecorator/preferences_page.gif it would help.
Gotcha. Thanks for the clarification. That would be nicer.
(In reply to comment #3) > Gotcha. Thanks for the clarification. That would be nicer. You're welcome :-)
This should also allow the decoration policy to be configured, in particular whether landmarks go bold in order to address bug 104783.
The point regarding bug 104783 can be addressed by turning off the decorator.
This might be resolved via our all-in-one legend idea: 152820.
Highlighters are now back in the Sandbox, and unsurprisingly nobody has complained. Marking this for later in case we expose highlighters again in some way.
Mik, can we have those highlighters applied only on the task list, but not promoted to the resource decorators?
I tried that out, and see a couple of problems. We are trying as much as possible to make colors correspond to some kind of semantics about tasks (e.g. red foreground = overdue). When adding another coloring scheme (e.g. user-defined background colors) the Task List can start to be so colorful that it looks like a Christmas tree, causing the colors to lose meaning. Also, people can only distinguish a relatively small number of colors from each other in a view like this (under a dozen if I recall), meaning that colors are likely to be better for categorizations of kinds of tasks than a per-task mechanism. We are currently doing these kind-categorizations with icons (e.g. red for severe), and I think we should leave the background color open in case extensions want to use it for other kinds of categorizations (e.g. past the deadline on a release plan).
I just don't see why can't used to his own categorization? It would be more flexible then forcing some predefined categories, that not necessarily match user needs.
The benefit of categorization with color is that if you assign a color to some category, then all things that match that category show up in that color. What's the use case for being able to assign colors per-task in the Task List?
Note that in the next dev build this menu will be available in the Sandbox plug-in (it was previously but disappeared temporarily).
Mik, to give you one example... I mark tasks I am being paid for as red and those I am doing for fun in blue. Both of those scatter over several projects.
That's indeed an interesting use case, since it crosscuts repositories and is a user specified thing.
Another possible classification (somehow alike Coad's Modelling in Color) is to use 3..4 color to mark issues related to specific subsystems. In case of Mylar it could be UI, Jira, Bugzilla, Web.
Right--but that's the property-based categorization that I was referring to in my above comments. Ensuring that extensions can do things like that is part of the reason that I want to avoid promoting the manual highlighting unless we have compelling reason.
That would be a property-based categorization only if project is using these as components...
Here is few other markers when highlighters are useful: "my patch" and "review patch". I use those for traching my own patches and patches I need to review later.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
