iWork and Version Control

I've been looking at the new release of iWork '09 from Apple and it's time to bring up the subject of version control and iWork documents again, after posting about it here last year.  

Maybe Apple have listened to their customers because in this release of iWork they have changed the format of Keynote, Pages and Numbers documents. These application now save your work as single files rather than document bundles. (I'd like to think somebody at Apple read my previous article, but that may be pushing it a bit!)

This is certainly good news for those with an antiquated version control system such as CVS and Subversion which, as I mentioned before, litters your working copy with version control.  To be honest, it's good news for any VCS since having to deal with one file instead of one directory. 

At igence where I work we're in the process of transitioning to git for our version control, replacing a 6 year old CVS repository. I've been getting to know git for good few months now, and I can see even it having problems with OS X bundles, especially when it comes to merging branches, since it works at the file level and would attempt to merge the contents of the bundle and most likely make a complete hash of it.

Of course, this still hasn't addressed the issue of which applications we use, but it does bring iWork back into the debate. We even have the option of OpenOffice.org as well now; the latest version of their suite (v3) is OS X native, rather than relying on the X Window System.