On Sun, Sep 25, 2005 at 12:38:44PM -0400, MenTaLguY wrote:
Off the top of my head (I'm sure I'm forgetting some things), some required things for 1.0 are:
Alan started a section at the end of the Roadmap for listing our 1.0 goals. I'm adding your comments there.
- Full support for SVG Basic, excluding perhaps animation, interactivity/scripting and SVG fonts
How would you feel if we set the goal to be SVG Tiny rather than SVG Basic? SVG Tiny requires us to implement Animation, foreignObject extensibility, switch, hyperlinking, and so forth, so for us is going to be plenty ambitious, but achievable.
SVG Basic has all that, plus viewports, color profiles, masking, more advanced font stuff, scripting, and filters. Quite a bit to bite off... I'm worried we could get bogged down.
I would advocate that we set SVG Basic as our Inkscape 2.0 goal and SVG Tiny as the 1.0 goal. That gives us two really tangible and useful objectives to organize efforts towards.
- integrated PDF/PS/EPS/AI export/import (probably means hauling a
subset of ghostscript in-tree, like Scribus has done)
Yes, this is one of the areas where I think even if we didn't want to do it, we'd be strung up if we released 1.00 without it. ;-)
I think the ideal solution would be to find a way to share this functionality with scribus in some fashion or other.
- a proper layers dialog
This has been on the todo list for a while; is there a way we could break this work up into more digestible chunks?
easily editable color swatches
"paint" swatches (e.g. gradient, etc, not just solid colors)
print-via-PDF (so we can do alpha etc directly)
I've added the above. I know we're close on the editable swatches, not sure on paint swatches.
- support for SVG profiles -- i.e. tracking the current set of SVG features in use, and being able to do things like (on request) force an SVG 1.2 Full document down to SVG 1.1 Tiny
This sort of sounds like an extension sort of thing...?
Thanks for the list.
Bryce