[cairo] MOZ-SVG-cairo (was: usable libsvg-cairo?)

[Liam Breck]

On closer inspection, it looks like Mozilla SVG is so tied into the Gecko
framework that detaching it would mean writing a pseudo-gecko, which is not
what I had in mind.

What we want is simply an SVG-based API for cairo, so you can write:
  XxSvgRect(aContext, aSvgParameters);
  XxSvgTspan(aContext, aSvgParameters, textbuf, textlen);
I guess we should do a standalone lib that simply borrows heavily from the
Moz-SVG cairo backend.

Would others find this useful?

I don't want to duplicate the work of libsvg-cairo or librsvg if not
necessary; is my impression that these projects are not evolving as fast as
Moz-SVG correct?

Thanks,

Liam Breck
Network Improv
http://networkimprov.net/airwrx/


At 01:38 PM 5/12/05 -0400, someone said:
>Quoting Liam Breck <svg at networkimprov.net>:
>
>> Considering the progress on Mozilla SVG, we're looking at pulling
>> the Mozilla SVG cairo backend into a standalone library, wrapped
>for
>> use outside Mozilla. It wouldn't parse the XML, but it would let
>you
>> use any parser or content model to drive rendering.
>>
>> We need this (or something similar) for SVGTerm, a mechanism that
>> continually updates an SVG scene on one or more remote screens.
>> (Embedding Gecko would be overkill for this app.)
>>
>> Is this something that others would like to have?
>
>Yes, it would lower the barrier-to-entry to writing any SVG-based
>application considerably.
>
>-mental
>
>