To view parent comment, click here.
To read all comments associated with this story, please click here.
They would have to totally change the backend API to make OSX and Win32 backends efficient. The graphics have already been tesselated by the time they are passed over to the backend. Here's the quartz how the API to the quartz backend to show where the API lays
static const struct _cairo_surface_backend cairo_quartz_surface_backend = {
NULL, /* create_similar */
_cairo_quartz_surface_finish,
_cairo_quartz_surface_acquire_source_image,
NULL, /* release_source_image */
_cairo_quartz_surface_acquire_dest_image,
_cairo_quartz_surface_release_dest_image,
NULL, /* clone_similar */
NULL, /* composite */
NULL, /* fill_rectangles */
NULL, /* composite_trapezoids */
NULL, /* copy_page */
NULL, /* show_page */
_cairo_quartz_surface_set_clip_region,
NULL, /* intersect_clip_path */
_cairo_quartz_surface_get_extents,
NULL /* show_glyphs */
};
Its not at line_to, curve_to level but much lower and very much tied to XRender.






Member since:
2005-07-06
If you read this
http://lists.freedesktop.org/archives/cairo-announce/2005-August/00...
you will see that while the API is frozen for this release many of the backend work is considered experimental and there is more work needed on it. It is too early to form opinions
If any of these does require a API change a new parallely installable major version would be releases similar to GTK 1.x and 2.x series.