I know this has been mentioned before. Some people think it would be handy to save an SVG file from Inkscape as an XCF maintaining layers. I was going to have together a quick output extension in python and an accompanying script-fu for the gimp to make this happen, but I don't think we have the appropriate export options.
It would be really fun to have a single command to export all the layers at once to something like filename-0001-layername.png, but I don't know how widely applicable that would be. According to the man page, --export-id forces the object's bbox for --export-area. I think this makes what I want to do impossible. I would suggest we make canvas size ALWAYS default and add an --export-bbox option. This would mean more typing for the people who already use this functionality, but it would IMHO make more sense overall.
Aaron Spike
On Feb 21, 2006, at 6:06 PM, Aaron Spike wrote:
I know this has been mentioned before. Some people think it would be handy to save an SVG file from Inkscape as an XCF maintaining layers. I was going to have together a quick output extension in python and an accompanying script-fu for the gimp to make this happen, but I don't think we have the appropriate export options.
It would be really fun to have a single command to export all the layers at once to something like filename-0001-layername.png, but I don't know how widely applicable that would be. According to the man page, --export-id forces the object's bbox for --export-area. I think this makes what I want to do impossible. I would suggest we make canvas size ALWAYS default and add an --export-bbox option. This would mean more typing for the people who already use this functionality, but it would IMHO make more sense overall.
Aaron Spike
Well...
Given some of Bob's progress and roadblocks doing ODF, we might need to hook in some things more directly sooner than thought. This can benefit what you're looking at also.
And for robust XCF output, each layer can be a different size and location.
Jon A. Cruz wrote:
Well...
Given some of Bob's progress and roadblocks doing ODF, we might need to hook in some things more directly sooner than thought. This can benefit what you're looking at also.
Well, I wouldn't say 'roadblocks,' more like challenges. Simply that since the ODF <drawing> graphics model does not match our SVG tree, the mapping from one to the other will not be perfect, and that ODG output will be weak at first and will gradually grow. I can do the conversion mechanism just fine, but once it is in place, I will need some help on the actual context and semantics of the conversion.
I put a .odg-output stub in /extensions/internal last week. You can see it in SaveAs. I am hoping to have some initial file saving ready by Saturday night.
bob
On 2/22/06, Aaron Spike wrote:
It would be really fun to have a single command to export all the layers at once to something like filename-0001-layername.png, but I don't know how widely applicable that would be.
+ some people might like to have original paths in that XCF ;)
Alexandre
On 2/21/06, Aaron Spike <aaron@...749...> wrote:
It would be really fun to have a single command to export all the layers at once to something like filename-0001-layername.png,
Agreed, that would be a nice option to have. More generally, not all layers, but all objects that are directly below the root - typically they are layers but not necessarily.
but I don't know how widely applicable that would be. According to the man page, --export-id forces the object's bbox for --export-area. I think this makes what I want to do impossible.
Yes, I agree that --export-area should not be ignored with --export-id. We just need to add another option, --export-area-canvas, which is the default in the regular export anyway, but is not the default with --export-id and therefore needs to be settable.
I would suggest we make canvas size ALWAYS default and add an --export-bbox option.
Hmm, no, I still think it makes more sense to export an object's bbox if you tell it to export that object. My solution with --export-area-canvas also requires adding one more area option, but it has the advantage of not changing the current defaults, which is a plus. Also, my new option makes sense with any export, whereas yours only with --export-id, which is slightly less logical.
All these changes are easy to do, the entire export/area logic is in one function. Just please test your changes extensively, with all possible combinations of options, etc.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On 2/22/06, Aaron Spike wrote:
I know this has been mentioned before. Some people think it would be handy to save an SVG file from Inkscape as an XCF maintaining layers.
There is a discussion on common multilayered raster images exchange format in gimp-developer@ today. The plan seems to be introducing another OpenDocument file format. As for developers, at least Boudewijn Rempt from Krita team is about to take part.
Is any of Inkscape's developers interested to take part in such a file format?
Alexandre
On Thu, 2006-03-02 at 18:42 +0300, Alexandre Prokoudine wrote:
On 2/22/06, Aaron Spike wrote:
I know this has been mentioned before. Some people think it would be handy to save an SVG file from Inkscape as an XCF maintaining layers.
There is a discussion on common multilayered raster images exchange format in gimp-developer@ today. The plan seems to be introducing another OpenDocument file format. As for developers, at least Boudewijn Rempt from Krita team is about to take part.
Is any of Inkscape's developers interested to take part in such a file format?
Alexandre
How can Create Project participate?
Jon
On 3/2/06, Jon Phillips wrote:
On Thu, 2006-03-02 at 18:42 +0300, Alexandre Prokoudine wrote:
On 2/22/06, Aaron Spike wrote:
I know this has been mentioned before. Some people think it would be handy to save an SVG file from Inkscape as an XCF maintaining layers.
There is a discussion on common multilayered raster images exchange format in gimp-developer@ today. The plan seems to be introducing another OpenDocument file format. As for developers, at least Boudewijn Rempt from Krita team is about to take part.
Is any of Inkscape's developers interested to take part in such a file format?
How can Create Project participate?
Since CREATE is meant to be place where developers meet, it has basic infrastructure to work on spec draft (ML,wiki, etc) to be submitted to OASIS.
I created http://create.freedesktop.org/wiki/index.php/General_multilayered_bitmap_exc... just 10 minutes or so before OpenDocument was mentioned. If anyone has better suggestions, please stand up high and speak loudly :)
Alexandre
participants (6)
-
Aaron Spike -
Alexandre Prokoudine -
Bob Jamison -
bulia byak -
Jon A. Cruz -
Jon Phillips