Hello again,
First, thanks all for the help --- this is one of the wonders of Free Software: you actually do get answers to your questions. :o)
I'll be forwarding the replies to my friend, to see if they help him. I believe he was looking for an application that could readily (or within a relatively short time) produce TinySVG graphics, but this could interest him nonetheless... I'll try to heed Jon's suggestion and persuade him into working with the Inkscape team to get the SVG TIny spec done.
From the comments that Dwain and Andreas wrote, I take it that we
could get a first, crude approximation to producing TinySVG graphics with Inkscape by avoiding the unsupported features (filters, markers, etc.) and by translating the way style is assigned to elements, right? Doesn't sound like a lot of work... I may give it a try.
Thanks once more everyone for your help, Denís.
2008/3/4, Jon A. Cruz <jon@...204...>:
On Mar 3, 2008, at 6:27 AM, Denís Fernández Cabrera wrote:
Hello,
I have a friend working on mobile devices, and he needs to use the SVG
Tiny specification. He was asking me wether Inkscape could produce
that kind of files, and when it would reach version 0.5.
Of course I know that trying to predict when 0.5 will come out is
pretty much impossible, but (keeping in mind that I don't know
anything about the SVG Tiny spec) I was thinking that one could
possibly create SVGs with Inkscape (avoiding the effects or resources
not contained in the Tiny spec) and then use a small script to strip
out whatever doesn't match the spec.
Does anyone know if this is feasible? And what differences are exactly
between the SVG and the SVG Tiny?
Hi,
First of all, you should be aware that the roadmap is only a suggestion. It is not a hard target list. Rather, it's where the developers list out their guesses on what might go on in the future, but it is very fluid and subject to change.
For doing SVG Tiny, or any other targeted subset of SVG, we have a few different things that could be done. I'm guessing that his questions about 0.5 were to be able to get SVG Tiny support. Given some active user interest and feedback, features are often brought in sooner than expected.
So if we get a user who can work with the developers to refine the needs and to test out and give feedback, then there is a better chance of something happening sooner rather than later. And in the case of SVG Tiny there are a few things to be done that might not even need to go into the core code.
Being able to get end-goals and details on how a user might work are good things. Especially any details on *which* SVG Tiny platforms might be targeted, expected workflow, etc.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user