[cairo] cairo internal design ideas
jost2345 at yahoo.de
Wed Sep 22 12:52:29 PDT 2004
I think we can leave out the font/glyph problem, which
is a completely different issue.
> Hence, supporting
> higher level output devices like PS, PDF and SVG in
> a good way
Can you please explain this? At least for PDF and SVG
it is not a problem to render trapezoids. If you are
concerned about the document size, just compress the
streams. -- I have to say that I have experience only
with postscript which does not support alpha.
> 2. The software fall-back path for patterns is
> messed up right now.
How is that related to your suggestion to make the
backends independent of the tesselator?
> 3. Clipping is inflexible and the way it's done
> right now is not efficient for all backends.
Probably. But I don't see how your suggestion would
help to improve this.
> [cairo] should push high
> level objects to the backends and the backends
> should be able request
> appropriate representation of these objects.
I don't think this is necessary. -- Well, it depends
on what exactly you mean with "high level objects".
Probably not a GObject, and not a shape, either. The
only thing you can pass down is the path. But what
would this be good for? Should all backends implement
their own tesselator?
Gesendet von Yahoo! Mail - Jetzt mit 100MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
More information about the cairo