Bug 175715 - [Decorators] Meaning of decorators not always apparent and hard to discover
Summary: [Decorators] Meaning of decorators not always apparent and hard to discover
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-02-27 11:06 EST by Evan Hughes CLA
Modified: 2019-09-06 16:05 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Evan Hughes CLA 2007-02-27 11:06:19 EST
Build ID: I20070209-1006

The meaning of some decorators is not always apparent. There doesn't seem to be a systemic way of revealing the meaning of decorators. The user is forced to rely on the context that the decorator appears in, which doesn't always provide enough information, or potentially misleads the user. 

It would be nice if there was a standard way of revealing the meaning of a decorator, such as a hover that shows the meaning of each contributed portion of the icon, a properties page that shows the meaning of each portion, or a key combination that would provide an explanation. 

For example the exact meaning of the inheritance decorators in the JDT is hard to determine with pausing to test. (By inheritance decorators I mean the up-pointing triangles that appear beside class members shown in search view, package explorer, and outline view. They are occasionally empty, occasionally green, and occasionally blue.)
Comment 1 Boris Bokowski CLA 2009-11-17 10:53:47 EST
Oleg is now responsible for watching the [Decorators] category.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:05:29 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.