On 18-8-2011 4:28, Nikita Kitaev wrote:
2011/8/17 Alexandre Prokoudine<alexandre.prokoudine@...400...>:
Как и просили :)
---------- Forwarded message ---------- From: Johan Engelen<jbc.engelen@...2592...> Date: Wed, Aug 17, 2011 at 11:34 PM Subject: Re: [Inkscape-devel] inkscape to synfig studio To: inkscape-devel@lists.sourceforge.net
On 14-8-2011 21:04, Alexandre Prokoudine wrote:
Hi,
FYI, for a few weeks now Nikita Kitaev has been working on an svg2sif extension that allows exporting SVG to Synfig Studio animation editor documents.
https://github.com/nikitakit/svg2sif
He hopes that it will eventually replace the existing SVG importer in Synfig.
Discussion forum is here: http://www.synfig.org/forums/viewtopic.php?f=1&t=2953
(After a very brief look) Apparently, the extension requires all shapes to be converted to paths. Because it is implemented as a python script, an extra Inkscape subprocess is launched to convert the non-path shapes to paths. I see the benefit of having a Python script, but is it not easier/faster in this case to write it in C++ in Inkscape's codebase ? Or, alternatively, we could add an option for extensions to request SVG's with path-shapes only...?
(Alexandre, can you forward this to Nikita? Thanks)
Ciao, Johan
Hi everyone,
I agree that having direct access to Inkscape's features would save some code repetition and subprocess calls. C++ is probably faster/easier if you're already very familiar with Inkscape's codebase. I'm not.
Having extensions request path-only SVGs would help in this case, but hopefully it can be something more flexible. For example, svg2sif also uses Inkscape to get rid of<use> elements -- but at some point in time I plan to use Synfig's linking/clone features instead.
You can have a look at the dxf_outlines extension in trunk to see how I handled <use> elements for DXF export. Might save you an Inkscape call :)
Ciao, Johan