Lee Braiden wrote:
But if you start inkscape from your home directory on the command line, or from just running it via a menu entry, and then load and save a file in another location, the PNG slices will end up in your home directory (at least on unix; windows might save then in C: or "C:\Program Files\Inkscape", or something like that.
At the moment, there's nothing I can do about that, since inkscape doesn't CD to the output directory before calling the extension, and doesn't seem to provide the extension with any idea of where it is actually saving stuff.
Personally, I'd like to see that issue fixed for 0.43.
I'm not really for this at all. One of the big reasons is that it is going to be difficult to handle issues like filename conflicts. Inkscape currently handles this for extensions, but if you are writing files that are not specified by the file dialog, there is no way to help here. Plus, how would "nfs://user/myfiles" be handled as a path?
All in all, I really think outputting something like .chm is much better. It should be easy to implement also. Just generate all of the slices and the xhtml files in a temporary directory, the zip them up and output that.
--Ted