|
"I'd settle for SVG support in Freehand, at this point."
Thanks, that's a start. There's a couple of things that "SVG support" could be understood to mean, in a rough guess of plausible ascending cost:
-- import of SVG illustrations
-- export of SVG illustrations
-- export of SVG animations
-- export of SVG interactivity
-- export as various SVG variants (Tiny, Basic, ASV-specific, Croczilla-specific, etc)
-- conversion to SVG as native file format for the application
-- use of some SVG renderer as native renderer to visualize external SVG documents
-- shift FreeHand's focus from print to SVG
There could definitely be other things intended by "SVG support" too. What we've been wrestling with is which pieces of work would actually matter to paying FreeHand customers. After that can come a costs/benefits analysis.
Keeping in mind that saying "do it all and then some" would be more expensive than any individual engineering change, could you drop a note to the FreeHand team directly, telling them which feature(s) is most desired, and giving them an idea how much it's worth to you? That could help us in figuring if we can make money with such an investment, thanks. Here's the place: http://www.macromedia.com/support/email/wishform/
(Note that a change-request won't automatically get implemented, but these *are* useful as one means of judging breadth and width of desire for investment in a particular area.)
--
For the first paragraph, "take XML seriously" describes a perception of someone else's feeling (and a corporation's "feeling" at that!), so it's hard to translate this into an engineering change-request.
It sounds like you're then asking us to stop selling Flash, in order to help SVG along, which I *would* have trouble taking seriously...? ;-)
Regards,
John Dowdell
Macromedia Support
|