[cairo] Extending Cairo API to support reusable paths
robert at ocallahan.org
Wed Mar 31 15:39:19 PDT 2010
On Thu, Apr 1, 2010 at 10:18 AM, Bill Spitzak <spitzak at gmail.com> wrote:
> I think even the device-specific ones are going to have to contain all the
> info in a cairo_path_t. This is probably the only reliable way to add them
> to a different device than the one they are on.
Some SVG examples contain megabytes of path data, so requiring that data to
be available in cairo_path_t format as well as the native path object would
commit us to a significant increase in memory usage. We'd prefer to avoid
This may mean that creating a retained path in one context and using it in
another context presents some quality degradation, if the platform's native
path representation is imprecise. I'm not sure if that's a real problem, and
even if it is, it doesn't seem worth fixing at the cost of increased memory
usage for the common case.
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cairo