[cairo] cairo design
otaylor at redhat.com
Sat Apr 24 09:07:02 PDT 2004
On Fri, 2004-04-23 at 17:37, Jon Smirl wrote:
> --- Keith Packard <keithp at keithp.com> wrote:
> > As you correctly surmise, doing this efficiently below the cairo API would
> > require a cairo wire protocol and a full cairo server on the far side of
> > the wire -- there's no other representation which could capture the
> > correct results. You can't just capture the tesselation and re-use that,
> > you have to retesselate at each transformation to ensure that the
> > pixelization of the result was accurate.
> Another solution to this is to introduce display lists into the Cairo API. xlib
> Cairo would keep doing things like it does currently and implement the display
> lists locally. Glitz could use OpenGL displays lists (which get stored on the
> server) and eliminate the net traffic.
> Shared display lists could also really speed up toolkit drawing. It would be
> good to get these in Cairo early and explain why you need them so that apps will
> take advantage of them.
Or maybe instead we should do some apps and see if they are actually
necessary? Presumably a display list looks a whole lot like a
"stored group" - I don't imagine that introducing them later compatibly
would be a problem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/cairo/attachments/20040424/6edf868a/attachment.pgp
More information about the cairo