Bug 34949 - [Fonts] Font preference page could indicate inheritance of fonts
Summary: [Fonts] Font preference page could indicate inheritance of fonts
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 3.0   Edit
Assignee: Kim Horne CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2003-03-13 14:30 EST by Randy Hudson CLA
Modified: 2004-10-08 10:51 EDT (History)
0 users

See Also:


Attachments
mockup (23.02 KB, image/gif)
2003-03-13 14:32 EST, Randy Hudson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Randy Hudson CLA 2003-03-13 14:30:21 EST
I noticed that when changing the Java Editor font, the Java Compare font 
changed too. I didn't know I was affecting both settings. Oh, ok, I just 
noticed now that there is a pane that says "Currently mapped to Java Editor 
Font". But I have no way of changing that mapping, so "Currently mapped"
seems misleading.

Why not display the inheritance of fonts?  You might also indicate in this 
inheritance tree which entries are user-specified, and which are inheriting 
from their parent entry.  See attachment.
Comment 1 Randy Hudson CLA 2003-03-13 14:32:25 EST
Created attachment 4111 [details]
mockup

This is also a scalability issue.  In WSAD, the "mapped to" could get very
confusing with 50+ entries.
Comment 2 Nick Edgar CLA 2003-03-16 13:39:12 EST
Deferring for consideration in 2.2.
Comment 3 Randy Hudson CLA 2004-02-27 13:25:13 EST
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.
Comment 4 Kim Horne CLA 2004-03-01 11:23:05 EST
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.
Comment 5 Randy Hudson CLA 2004-03-01 11:27:26 EST
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.
Comment 6 Kim Horne CLA 2004-03-12 19:29:29 EST
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.
Comment 7 Kim Horne CLA 2004-04-12 12:44:22 EDT
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.
Comment 8 Kim Horne CLA 2004-10-08 10:50:47 EDT
Not sure why this is still marked as later... reopening...
Comment 9 Kim Horne CLA 2004-10-08 10:51:08 EDT
...to mark as fixed.
Comment 10 Kim Horne CLA 2004-10-08 10:51:19 EDT
(and verified)