| Summary: | [Fonts/Colors] Theme API cannot rely on JFaceResources. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kim Horne <eclipse> | ||||
| Component: | UI | Assignee: | Kim Horne <eclipse> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | michaelvanmeekeren, n.a.edgar, Tod_Creasey | ||||
| Version: | 3.0 | ||||||
| Target Milestone: | 3.0 M9 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=483359 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Kim Horne
As per discussion with NE: The easiest (and most transparent) way to make JFace theme enabled is to have workbench populate it's own Font/Color registries for the "base" theme instead of relying on JFaces'. The currently active theme would be mirrored in the JFace registries. When the theme changes, new values are pushed into the JFace registries. This allows listeners on the JFace registries to get the latest theme specific data as well as recieve events of changes. Created attachment 9331 [details]
Work in progress
Fix in HEAD. Verified in 200405190010 using the test suites. Closing to keep a tidy house. Pardon the spam. |