49
edits
FutureGfxWhiteboard: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 42: | Line 42: | ||
* When do we switch Thebes on by default? Should we delay until performance is as good as today for most users? | * When do we switch Thebes on by default? Should we delay until performance is as good as today for most users? | ||
tor: We should wait until we have good performance, as we've made this particular promise at the start of the cairo work. In particular, if we switch too soon Mac is going to suffer performance-wise. | |||
== Cairo Quartz/ATSUI work == | |||
Cairo needs work on the Quartz backend if we plan on using that instead of glitz. ATSUI font backend needs lots of development. | |||
== SVG switch to Thebes == | |||
SVG currently uses the cairo context directly from Thebes and promises to leave it in good condition when it's done. | |||
We eventually want to get SVG using Thebes so that we can get rid of the renderer layer in the SVG code and get better font selection/usage. The easiest way of doing this is probably in two stages: write a svg renderer with the existing layering that uses Thebes instead of cairo, then start removing the SVG renderer layer. | |||
Thebes will need some changes for SVG. Most of these will be minor cairo API wrapping, but we might have more extensive needs for efficient textPath implementation. | |||