Subject: Re: image handling (svg)
From: Leonard Rosenthol (leonardr@lazerware.com)
Date: Sat Feb 05 2000 - 20:21:23 CST
At 7:34 PM -0600 2/5/00, Justin Bradford wrote:
>So really, we just want:
>PICT->SVG
>E/WMF->SVG
>flash->SVG
>other vector formats->SVG
It's more work than necessary and I don't know that it buys
you anything. I'd simply go vector format->PNG.
>The vector image class in AbiWord could then just be a subclass of the
>normal image class, containg a buffer with the original SVG XML. Copying,
>editing (via component), and saving would use this XML and the associated
>PNG byte buffer would be updated/generated by it and the SVG->PNG routine.
Although that prohibits bringing native PICT/WMF data into
applications that can support them. I guess if we assume that all
vector apps in the future will take SVG (a hopeful one, but I don't
know how soon), then it might be OK - but in the meantime users would
lose functionality.
>Also, does SVG describe animation or interactivity? Do we want AbiWord to
>concern itself with these things?
>
Animation and interactivity is supported in SVG via scripting
of the DOM. In other words, the SVG document contains
JavaScript/ECMAScript code that manipulates the DOM of the SVG
document to bring out the effects of animation and interactivity.
LDR
----------------------------------------------------------------------------
You've got a SmartFriend in Pennsylvania
----------------------------------------------------------------------------
Leonard Rosenthol Internet: leonardr@lazerware.com
America Online: MACgician
Web Site: <http://www.lazerware.com/>
FTP Site: <ftp://ftp.lazerware.com/>
PGP Fingerprint: C76E 0497 C459 182D 0C6B AB6B CA10 B4DF 8067 5E65
This archive was generated by hypermail 2b25 : Sat Feb 05 2000 - 21:21:33 CST