Export dialog, relative path patch
Hi,
I've written some codethat makes the export dialog leave out the directory when exporting a drawing or an object, defaulting to just the png filename (patch attached).
This is for two reasons:
1) Since the export path defaults to the SVG directory anyway, this will a) not change anyone's workflow, but b) will reduce work when you inevitably move your files around. If relative paths are an option, is there a good reason why they are not the default option? I suppose it's conceivable that people always export all pngs to a certain fixed folder that is nothing to do with the SVG directory, but then you have to type that in anyway, so this doesn't harm that use case at all.
2) I didn't even know that relative paths worked until about a week ago*, so I have to assume that at least some others don't know about it either. This patch helps to advertise to users that it is even possible, and saves them some work!
If you accept this code, please look at it very carefully, I am just a novice at these things.
Craig
* I have manually updated the export path in this dialog when my files need to be moved (at least once per file, depending on that jobs status, which seems to be unavoidable in my workflow), I dont even want to think how many hours I've spent doing this unnecessarily.
I haven't looked at the code, or tried it, but this is an excellent feature.
I assume that it also works for relative paths that are outside the document's path (eg paths like ../website/images, which is a real-life use-case for me), and that absolute paths are left intact (eg /myimages/ doesn't get turned into ../../../../myimages)?
- Bryan
On Mon, Aug 30, 2010 at 04:59, Craig Marshall <craig9@...400...> wrote:
Hi,
I've written some codethat makes the export dialog leave out the directory when exporting a drawing or an object, defaulting to just the png filename (patch attached).
This is for two reasons:
- Since the export path defaults to the SVG directory anyway, this
will a) not change anyone's workflow, but b) will reduce work when you inevitably move your files around. If relative paths are an option, is there a good reason why they are not the default option? I suppose it's conceivable that people always export all pngs to a certain fixed folder that is nothing to do with the SVG directory, but then you have to type that in anyway, so this doesn't harm that use case at all.
- I didn't even know that relative paths worked until about a week
ago*, so I have to assume that at least some others don't know about it either. This patch helps to advertise to users that it is even possible, and saves them some work!
If you accept this code, please look at it very carefully, I am just a novice at these things.
Craig
- I have manually updated the export path in this dialog when my files
need to be moved (at least once per file, depending on that jobs status, which seems to be unavoidable in my workflow), I dont even want to think how many hours I've spent doing this unnecessarily.
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Bryan
I haven't looked at the code, or tried it, but this is an excellent feature.
Thank you - I hope everyone else sees it that way too ;)
I assume that it also works for relative paths that are outside the document's path (eg paths like ../website/images, which is a real-life use-case for me), and that absolute paths are left intact (eg /myimages/ doesn't get turned into ../../../../myimages)?
That's right, it will still handle both relative and absolute paths, it just now defaults to relative (current dir, as usual) if the document or object hasn't yet been exported. Of course, that's the intention and that's how it works with my testing. It will need other people to test it out to make sure it works as advertised though.
Thanks, Craig
Perfect :-)
On Mon, Aug 30, 2010 at 09:41, Craig Marshall <craig9@...400...> wrote:
Hi Bryan
I haven't looked at the code, or tried it, but this is an excellent
feature.
Thank you - I hope everyone else sees it that way too ;)
I assume that it also works for relative paths that are outside the document's path (eg paths like ../website/images, which is a real-life use-case for me), and that absolute paths are left intact (eg /myimages/ doesn't get turned into ../../../../myimages)?
That's right, it will still handle both relative and absolute paths, it just now defaults to relative (current dir, as usual) if the document or object hasn't yet been exported. Of course, that's the intention and that's how it works with my testing. It will need other people to test it out to make sure it works as advertised though.
Thanks, Craig
participants (2)
-
Bryan Hoyt | Brush Technology -
Craig Marshall