Hi I am planning to do an extension for renaming photos. But no promise on delevery time yet... :) So if you have time and energy :) go ahead... I would not choose the path you have done though. What I was planning to do is to rename / move the physical photo (and all its versions) to the new name/place, and then also update the database accordingly. Of course, you need to check that if anything goes wrong you revert back to the old state. Do a hard link instead of moving could also be an option. I put code for this in a bug on bugzilla for renaming photos two years ago or so. Should be possible to re-use / re-factor that code and use it. /Bengt On Thu, 2008-03-13 at 10:23 +0400, Lev Danielyan wrote: > Hi, guys, > > I'm new to this community, so let me introduce myself, I'm Lev, 27 y.o. > and work as a verification engineer. > > I've been using f-spot for a while now to organize the huge collection > of my photos, mainly my kids ;) > The only thing I am missing here is, actually, a batch rename > functionality with some fancy stuff like embedding > exif info into the file name, like date etc. > > So I started writing an extension. And this is where I need you help. > The main file operations I plan will be renaming the files inplace, > rename-copy to destination and rename-move to destination. > > The problem is that the selected files that I grab from the main f-spot > window will eventually get changed (in terms of file name) and the db > will need to be changed also, > so I plan to have a checkbox to give users an option to "reimport" the > changed files into the DB. > And the question is what would be the correct way to do it? Some code > snippet would be very valuable :) > > Thanks, > Lev > > PS. I hope I made my point clear :) > _______________________________________________ > F-spot-list mailing list > F-spot-list gnome org > http://mail.gnome.org/mailman/listinfo/f-spot-list > -- With Regards Bengt Thuree bengt thuree com
Attachment:
signature.asc
Description: This is a digitally signed message part