Category Archives: Shotwell

Shotwell 0.5.0 released

Yorba has released Shotwell 0.5.0, a major update to our digital photo manager.  This release includes a host of new features, including:

* Photos can be tagged and organized by tag, creating a new tool for managing your photo collection
* Printing
* Photos can be published to Google’s Picasa Web Albums service
* Photo exposure date and time can be set and shifted
* Photos can be set as your desktop background directly from Shotwell
* Photo import runs in the background, making imports smoother and more fluid
* Publishing photos to web services is more responsive
* New or updated language support for French, Italian, German, Simplified Chinese, Bulgarian, Danish, Dutch, Estonian, Polish, and Portuguese.
* Other stability and performance improvements

We highly recommend that all Shotwell users upgrade.

Yorba would like to thank all of our bug testers and translators, without whom this release would not have been possible. We’d like to specially thank Martin Olsson, for his rigorous testing of Shotwell 0.5, and Kaj-Ivar van der Wijst, for his stylish redesign of the Yorba website.

We’d also like to think our friends at Red Hat for making Shotwell the default photo manager in Fedora 13 alpha!

You can download a source tarball from the Shotwell home page at: http://www.yorba.org/shotwell/

or grab a binary for Ubuntu Karmic or Lucid via Yorba’s Launchpad PPA at: https://launchpad.net/~yorba/+archive/ppa

Bowling as a metaphor for closing tickets

One of the features I’m proud of in Shotwell 0.4 is our undo/redo system.  (Kudos to Rob Powell for turning me on to the Command pattern.)  Thanks to abstractions in our primary data structures, it was easy to build a set of base Command classes that deal with these generic objects in generic ways.  That’s why our undoable crop command is only 13 lines of Vala code — and that includes the class boilerplate.

When Adam first spec’d Shotwell (wa-aaa-y back in February/March of last year), he generated a slew of tickets for features he knew we wanted eventually, but in no particular order of priority.  We knew we wanted undo but didn’t know when we’d add it (or even what would be undoable).

When I first attacked the problem in November, I pointed out that coding undo does not give you redo for free.  So, Adam created a separate redo ticket in case it had to go in later.

As it turned out, I implemented Redo alongside Undo.  I was elbow-deep in the code and I could see how to get redo implemented on all the various commands, and sometimes in generic ways.  (This is why crop’s so small.)

That was pretty satisfying, closing ticket #65 and #1001 in the same commit.  Now, some of those tickets in between aren’t for Shotwell, but certainly a lot of them are.  It felt like nailing the 7-10 split in bowling.  I’m a horrible bowler, and I only remember making that shot once.  Closing two tickets separated by 936 others is likewise satisfying.

If only it had been deprecated in 2001

You know that any post about deactivating HAL will, at some point, link to a bucket of bolts singing “Daisy Bell”, so I’ll do it now and get it over with.

The past couple of days I’ve been removing from Shotwell the deprecated (and despised!) HAL.  Shotwell’s reliance on HAL is minimal.  Most hardware interaction is through gPhoto.  What Shotwell needs is notification of devices being attached or detached (to run a gPhoto auto-detect) and a way of mapping USB ports to gPhoto camera objects (due to some legacy libusb port-naming stuff — see this and this).  udev is the preferred replacement (although there’s still some information out there saying to use DeviceKit; don’t).  Unfortunately, there’s no Vala bindings for gudev (a GObject-wrapper), so I had to build my own.

It turns out the Vala documentation for making bindings for GObject-based libraries has improved considerably, and I had a workable VAPI in just a couple of hours.  (It’s here for those interested in its state.)

gudev has a signal for when devices are added, removed, changed, etc.  That’s good.  However, it doesn’t provide a way to get subsystem-specific device information (i.e. whether a USB device is a PTP camera).  The solution was to walk the USB bus (via libusb) and match bus/device IDs with gPhoto’s auto-discovered port strings.  And that’s all there was to it.

HAL offered everything we needed (signalling and USB-specific device type information), so I can’t say I’m on the good-riddance bandwagon.  I’m not cheerleading for it either, though  Like a casual acquaintance with whom you don’t have much in common, it’s easy to say sayonara to HAL.

Shotwell 0.4.0 released

We’ve released Shotwell 0.4.0, Yorba’s photo organizer for the GNOME desktop.  We’ve been cranking along the past two months (has it only been two months?) to get this version out before the end of December, and the hard work paid off.

Probably our most-requested feature to date has been publishing photos to Facebook and Flickr.  Shotwell 0.4.0 now offers both.  I’m pleased with the result, especially being able to log in to these services in Shotwell itself rather than through an external browser.  We have big plans on making Shotwell play well on the Web and with other Web services, so stay tuned.

Other big additions include more language packs, thanks to the work of translators from around the globe.  Shotwell 0.4.0 features complete or all-but-complete translations for Italian, German, Polish, Estonian, and Swedish.

Finally, Shotwell 0.4.0 has been ported to Windows and a binary installer is now available.  This is an alpha release with some limits, including a lack of camera support and no Facebook/Flickr publishing.  However, we were surprised with the (relative) ease of porting Shotwell to Windows.  GTK and Vala’s portability were a huge boon in this process.

We’re always looking for feedback, so let us know what you think.  Hope you enjoy!