On Thu, 2011-05-26 at 09:37 -0700, Adam Dingle wrote: > On 05/26/2011 12:45 AM, Mateusz Loskot wrote: > > On 26/05/11 03:32, Lu Timdale wrote: > >> I would like to have different level of quality of images > > > based on the perceived value of the image. > >> > >> so... > >> For a 4 or 5 star image: > >> - keep original size jpg + duplicate raw file if it exists > >> For a 1 to 3 star image: > >> - keep original jpg only (no raw) > >> For an unrated: > >> - resample jpg image (either resize or reencode with higher > >> compression) > >> > >> Is this a feature that others see value in? > > > > In my opinion (a user trying to hack Shotwell from time to time, not > > mainstream developer), there is a usability potential of this > > kind of features. > > > > (brainstorming) > > > > However, I think this is a very good candidate to implement as > > extension, a plug-in. > > Agreed. > > > I'm not sure if the current SPIT allows to extend > > managing actions, but perhaps it could. > > Then you can have a plug-in that hooks in when a photo is rated: > > > > 1. Select 1..N photos > > 2. Set rating > > 3. The plug-in post-rating processes photo using > > 3.1. For a 4 or 5 star image: > > 3.2. For a 1 to 3 star image: > > 3.3. ... > > > > In order to make it possible, the SPIT would have to provide events, > > lets's say "management events": pre-action, post-action, where action > > is rating applied, flag set, tag added, tag removed, etc. > > Right. Shotwell's plugin architecture (SPIT - see > http://trac.yorba.org/wiki/ShotwellArchWritingPlugins) currently only > lets you add a publishing destination or slideshow transition. It > doesn't yet provide hooks to let you respond to arbitrary events or > perform arbitrary actions as you suggested. It would be cool if we can > make it that general at some point, though (this is > http://trac.yorba.org/ticket/1603).
A possible solution would be to create a new SPIT extension point derived from the web publishing one: instead of having a list of Publishable objects that wrap images that you can send to a web service, you would have a list of Transformable objects that wrap images that you can transform and save back (with or without keeping the original). You could probably re-use a fair bit of the publishing code, in particular the dialog and UI infrastructure. Thinking about it, it would also be a good way to migrate the alien DB code to SPIT :-) Cheers, Bruno _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
