| Summary: | [Fonts] Font preference page could indicate inheritance of fonts | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Randy Hudson <hudsonr> | ||||
| Component: | UI | Assignee: | Kim Horne <eclipse> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | Keywords: | usability | ||||
| Version: | 2.1 | ||||||
| Target Milestone: | 3.0 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Randy Hudson
Created attachment 4111 [details]
mockup
This is also a scalability issue. In WSAD, the "mapped to" could get very
confusing with 50+ entries.
Deferring for consideration in 2.2. The "mapped to" property is something that the user cannot edit. So by showing inheritance, you can get rid of this box and simplify the page. I'd like to do this, but the situation is somewhat muddied by the introduction of categories. If the font you map to is not in the category you are displaying, then what do you show? Still, your points are valid and I will investigate. Maybe the introduction of categories was unnecessary and could be removed. But, with categories, this sounds like the same as opening the hierarchy view on a package. If the superclass is not in the package, it still shows that class in the tree. Category is more than a way to better group the items - it's also capable of rendering a preview for a set of contributions. I'm going to mark as LATER and revisit post 3.0. I may be able to simplify the 'Comment' control for 3.0, however. Inheritance is now shown in the tree view. If your parent is in the same category, you are a child tree node. If your parent is in another category then your label indicates who your parent is. Not sure why this is still marked as later... reopening... ...to mark as fixed. (and verified) |