> For me a command line tool is good enough (but I'm a linux man ;-)
So am I, and we'll start from a command-line tool, adding GUI later.
> In my script I was working the exact opposite route.
> I.e., I was creating a rawRename oldname.crw newname.crw
I thought about this but if lzn and raw are in different directories, we can recover the full rawfile path from lzn but not vice versa :-)
To make it easier we could accept oldname.crw as well - e.g. if files provided are not .jpg, we'll check whether oldname_lzn.jpg exists. Or we can even specify basename without extension, e.g.
basename -> basename_lzn.jpg and from it we find raw file path
> What would happen with the export directory. Would this remain the old
> value or would you do some magic to handle it more like a relative path?
> I guess the latter is quite tricky to do.
> (E.g., lzrename xxx/yyy/zzz_lzn.jpg aaa/bbb/ccc_lzn.jpg
> where zzz_lzn.jpg has an export path xxx/yyy/export/zzz_exported.jpg
> this could be renamed to aaa/bbb/export/zzz_exported.jpg)
I'll experiment with this. I don't see any difficulties with converting relatives paths to absolute and vice versa - Python Standard Library has powerful functions for path manipulation. So I'll try to make the tool as universal as possible. There will be probably several iterations.
A question: when the tool is ready for beta-testing, where should I put it? We can try http://lightzone.wikidot.com/ if it supports attachments.
Regards,
Alex



Reply With Quote