To view parent comment, click here.
To read all comments associated with this story, please click here.
That's like saying PDF/OpenGL/Postscript is only targeted at <stuff it works on>
No its not. the fact that you had to use <stuff it works on> shows that there's no real comparison. PDF, OpenGL and Postscript are at the cairo frontend level, they are basically a lit of commands, move here, draw a line to there, use these coordinates for a Vertex. Cairo goes further by saying how these lines should be drawn using what ends up as a thin wrapper around XRender the same way that GDK 0.1 - 2.8.x were thin wrappers around X11. Oooops. that mistake you said they won't make, to late already have.
On Linux cairo goes
cairo-> tessellation -> XRender
OSX would have to go, given a proper backend.
cairo->tessellation->quartz drawns trapezoids->decompose to primitives -> compositor.
By having the tessellation as part of the cario front end instead of the backend they've doomed every other backend bar glitz not being the very poor relative. Proper OSX and win32 end up decomposing the graphics twice Glitz only works well because the trapezoids can be represented easily as a quad. but that means you've got a GL context not a CGContext or a Win32 context . Quartz2d and Avalon or whatever it's called now could well be better off with a wrapper rather than a backend.





Member since:
Riiight...
That's like saying PDF/OpenGL/Postscript is only targeted at <stuff it works on>. Cairo does _not_ make the same misstake as GDK did.
Sure, a lot of the backends need improving but that will happen in due time.