Hi Mark, Your import scenario could be supported by the alien database framework that the import from F-Spot is built upon. The documentation on it is quite sparse as I never found the time to extend on my original blog post, which you will find here: http://brunogirin.blogspot.com/2010/09/adding-support-for-alien-database.html Also, this blog post is a bit old and the code has been refactored since then but it should give you a good idea of what it entails.
For your export scenario, you could maybe write a publishing plugin as explained here: http://trac.yorba.org/wiki/ShotwellPrelimPublishingAPIDoc Although the interface is designed for web publishing, it may be possible to use it to export locally. Failing that, you could always query the Shotwell database with a python script to find all pictures that have a given tag, although that method would break the day the database schema is changed. Cheers, Bruno On Mon, 2011-05-16 at 22:04 +0200, Mark wrote: > Hi, > > before I moved to shotwell (thanks for this great program!), I have been > using gqview for managing my photos and for defining collections. gqview > stores collection definitions in text files in a very simple format. The > following shows an example for selected images from a trip to Venice. > > The collection file is > > /home/mr/.gqview/collections/Venedig.gqv > > with the following contents (reduced to two images for brevity): > > #GQview collection > #created with GQview version 2.0.4 > #geometry: 68 67 491 1002 > "/home/mr/photo/lib/2009/20090405-venedig/dpp/20090406-094212-00.jpg" > "/home/mr/photo/lib/2009/20090405-venedig/dpp/20090406-103400-00.jpg" > #end > > A gqview collection file basically just contains a list of path names. I > use these collection files as input for a python script that > post-processes collections, for example, to produce various kinds of web > gallery formats. > > Now that I'm switching from gqview to shotwell, I was wondering how I > could continue to use my old collection files and my python script. I > would like to be able to > > 1. Reuse the (work put into the) existing collection files. > 2. Continue to use my python script for post-processing of new > collections defined in shotwell. > > My first idea was to to extend shotwell so that it can import and export > gqview collection files: > > 1. Import a *.gqv file and tag each photo in the collection with the > collection name. In the example above, the two photos would get a tag > "collection-Venedig". That way I can carry over the information from the > existing collection files to shotwell. > > 2. Select tags in shotwell and for each tag, say t, create a file t.gqv > containing the list of tagged files. That way I can define new > collections in shotwell as usual and I am able to post-process them with > scripts. > > What do you think? Would that be useful for shotwell in general? Or is > this functionality too specific? What would be the best way for > implementing it? > > Thanks, > Mark > _______________________________________________ > Shotwell mailing list > [email protected] > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
