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?
Denís.
On 3/3/08, Denís Fernández Cabrera <denis@...2126...> wrote:
And what differences are exactly between the SVG and the SVG Tiny?
this should get you started. the only program that i know of that produces rather converts to tiny svg is adobe illustrator. now how standards compliant the code is another subject in itself.
http://www.w3.org/TR/SVGMobile12/
dwain
SVG Tiny 1.2 is a subset of the upcoming SVG 1.2 Full (or the core if you want). You can think of it as a subset of SVG 1.1 full (compared to SVG 1.1 full it doesn't have filters, it doesn't have clipPath, no patterns, no markers, fewer DOM calls, an a few other tings). On the other hand it has a different DOM (the uDom (or Micro-Dom)) which allows easier and typed access to the SVG DOM and it introduces a few new methods, e.g. network connections, timers, etc. required for application development.
One other fundamental change to SVG full is that it doesn't support CSS (class) and style attributes. All the styling is done with presentation attributes. This simplifies the XML processing of SVG tiny. As an example, instead of using <path style="fill:red;stroke:blue;stroke-width:0.5" d="..." /> (the way Inkscape does it) you would write in tiny: <path fill="red" stroke="blue" stroke-width="0.5" d="..." />
I think it would really be great if Inkscape would support the output to SVG tiny. Alternatively, one could write a script for post-processing the regular output of Inkscape. I don't like the style="...." way Inkscape uses for presentation attributes. I think it would also make sense for SVG 1.1 full to have either presentation attributes or support for CSS classes.
To convert some of the more advanced SVG full features to tiny, Inkscape would have to do geometric processing, like converting markers to individual path elements, filtered graphics to rasters, patterns to path elements, etc.
Hope this helps, Andreas
On 3/3/08, DenÃs Fernández Cabrera <denis@...2126...> wrote:
And what differences are exactly between the SVG and the SVG Tiny?
this should get you started. the only program that i know of that produces rather converts to tiny svg is adobe illustrator. now how standards compliant the code is another subject in itself.
http://www.w3.org/TR/SVGMobile12/
dwain
-- dwain alford "The artist may use any form which his expression demands; for his inner impulse must find suitable expression." Kandinsky
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
for completeness:
Ikivo offers two tools for SVG tiny development:
* Ikivo Animator (works together with Adobe Illustrator), for adding SMIL animations and interactivity * Ikivo IDE (an Eclipse plugin) for scripting/debugging interactive/scripted SVG content - works for javascript or java developers
Andreas
On 3/3/08, DenÃs Fernández Cabrera <denis@...2126...> wrote:
And what differences are exactly between the SVG and the SVG Tiny?
this should get you started. the only program that i know of that produces rather converts to tiny svg is adobe illustrator. now how standards compliant the code is another subject in itself.
http://www.w3.org/TR/SVGMobile12/
dwain
-- dwain alford "The artist may use any form which his expression demands; for his inner impulse must find suitable expression." Kandinsky
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
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.
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
On Mar 4, 2008, at 8:13 AM, Denís Fernández Cabrera wrote:
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.
Yes.
And then an XSLT stylesheet to convert from stock SVG to SVG Tiny might be doable in a short timeframe.
participants (5)
-
Aaron Spike -
Andreas Neumann -
Denís Fernández Cabrera -
dwain -
Jon A. Cruz