Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 27406

Summary: Should consider using the new font propogation support
Product: [Eclipse Project] JDT Reporter: Tod Creasey <Tod_Creasey>
Component: TextAssignee: Dani Megert <daniel_megert>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: 2.1   
Target Milestone: 2.1 M5   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on: 28725    
Bug Blocks: 31067, 31156    

Description Tod Creasey CLA 2002-11-29 10:53:34 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 Dani Megert CLA 2002-12-19 02:45:08 EST
Tod,

what is the best way to be informed about font changes? Normally an editor from
plug-in X only listens to preference changes of plug-in X's store. Is there an
easier way than adding an additional listener to the Workbench's store (just for
the font)?
Comment 2 Dani Megert CLA 2002-12-19 03:05:17 EST
I guess best way is to add a listener to the font registry - right?
Comment 3 Dani Megert CLA 2002-12-20 08:25:13 EST
Fixed.
Available in builds > 20021218

Note: I had to add a little hack in UIPlugin (see bug 28725).
Comment 4 Dani Megert CLA 2003-01-06 05:17:53 EST
Verified that workaround has been removed.