Bug 27405

Summary:	Should consider using the new font propogation support
Product:	[Eclipse Project] Platform	Reporter:	Tod Creasey <Tod_Creasey>
Component:	Compare	Assignee:	Andre Weinand <andre_weinand>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	2.1
Target Milestone:	2.1 RC2
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Tod Creasey

2002-11-29 10:53:12 EST

20021126

As of build 20021203 the eclipse workbench will now support declarative fonts. 
This will eliminate the need for the PropogatingFontFieldEditor.

There is a new extension point fontDefinition for defining fonts so that they 
can be viewed and managed by the workbench fonts preference page. There is 
also a defaultTo attribute which when set keeps the entry for the 
fontDefinition consistent with the defaultsTo entry if the preference for the 
fontDefinition is not set.

For example if a font called org.eclipse.myplugin.textfont had a defaultsTo of 
org.eclipse.jface.textfont the value in the font registry for 
org.eclipse.myplugin.textfont will be the same as the value for 
org.eclipse.jface.textfont until the user sets a preference for 
org.eclipse.myplugin.textfont .

see the org_eclipse_ui.fontDefinition doc for more details

Comment 1 Andre Weinand

2003-01-20 06:26:07 EST

*** Bug 26985 has been marked as a duplicate of this bug. ***

Comment 2 Andre Weinand

2003-02-19 16:36:10 EST

Not for RC1

Comment 3 Andre Weinand

2003-03-03 12:53:37 EST

Waiting for better fix...

Comment 4 Tod Creasey

2003-03-03 12:58:35 EST

What do you mean by a better fix? Is there a requirement of the font support 
you have?

Comment 5 Andre Weinand

2003-03-03 14:32:55 EST

See bug 32921.

Comment 6 Andre Weinand

2003-03-03 14:43:27 EST

[Oops, made comments to wrong bug. My last two comments were for bug 26990.
For this one I don't need a better fix :-]

Comment 7 Andre Weinand

2003-03-04 10:22:50 EST

reopened for 2.1

Comment 8 Andre Weinand

2003-03-04 12:53:19 EST

fixed > 20030304