Alternatively a Flex importer (sth. like the Flash Video Importer back then) could be an idea. In reverse logic this could also serve as part of the FlexJS exporter.
*** I am no genius in XSLT, but let me share what I already got: In my converter (http://www.realcreation.com/SVGtoFXG.dmg) I am using the xslt file I found here: http://svg2fxg.blogspot.de/2012/03/svg-2-fxg-conversion-step-1.html I just used the xslt part of it and modified it a little. - I commented out the initial <mask> tag as it only serves to give the fig file the same measures as the svg file. This is nice to have, but i still took it out, as this causes problems with ‚unclean‘ svg, where objects may be moved outside the mask area. - I added: <!-- ignore text content of nodex --> <xsl:template mode="forward" match="text()" /> This strips out text values in the svg file, what leads to a corrupt fxg. Inkscape is good in placing additional values and text. - I set joint and cap conditionally, since empty values causes errors: <xsl:if test="$stroke_linejoin != ''"> <xsl:if test="$stroke_linecap != '‘"> - For the rest I just packed the xslt with my air application that fires an applescript to call xsltproc (it seems to have restrictions in being called directly). I think you could do the same in Windows with Command Line Transformation Utility installed: http://www.microsoft.com/en-us/download/details.aspx?id=21714 *** The good news however is, that I’ve just found inkscape’s own xslt conversion file, so you can easily try to apply it in the same manner as described above (I will also try out.): https://github.com/piksels-and-lines-orchestra/inkscape/blob/master/share/extensions/svg2fxg.xsl Please let me know about your progress, Sascha Am 06.08.2014 um 18:50 schrieb Jason Taylor <ja...@dedoose.com>: > perhaps then we should work on an FXG exporter for Inkscape that does the job > properly? > > -----Original Message----- > From: Sascha Ahrend [mailto:sahr...@icloud.com] > Sent: Wednesday, August 06, 2014 4:06 AM > To: users@flex.apache.org > Subject: Re: Design tools for creating Flex 4 skins > > Sorry, but I don't think we should replace FXG as main skinning language. > > Nothing against extending SVG support, but FXG is much nearer to Actionscript. > > Also the SVG files created by most Illustration Software have to be cleaned > up in the same manner as you say about FXG. > > E.g. if you draw an object and reposition it, Inkscape (i guess Illustrator, > too) just adds a transform attribute to the path instead of updating the path > itself. > (You may find the object in a completely different position than expected in > the SVG output, even when optimized). > > I got the best results with a tiny piece of software for Xcode/Quartz > developers: https://itunes.apple.com/de/app/ivinci-express/id607900811?mt=12 > Purely SVG based, it is really WYSIWYG - even Illustrator and Inkscape files > are cleaned up thoroughly (text is rendered as well). > > I then built a SVG -> FXG converter for Mac OS (based on an xslt-Script i > slightly modified): > > http://www.realcreation.com/SVGtoFXG.dmg > > Used with a 'clean' SVG it virtually gives me everything as 'clean' FXG (no > gradients yet, but that's easy to add manually or with e.g. 7jigen fxgeditor. > I may update.) > > (In addition, I wouldn't get too irritated about Adobe having abandoned FXG, > as they also donated the FXG standard to Apache before, so they'd always be > bound to changes implemented by Apache. Same reason they gave up FB Design > View.) > > > Rgds., > > Sascha > > > Am 06.08.2014 um 12:04 schrieb Kessler CTR Mark J <mark.kessler....@usmc.mil>: > >> Side bar note, here are the soon to be release notes for the new Inkscape >> 0.91 [1] >> >> [1] http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91 >> >> -Mark >> >
