Linked by Thom Holwerda on Mon 6th Aug 2012 13:16 UTC
Mac OS X How this passed through Apple's Mountain Lion testing is beyond me. "If one edits a document, then chooses Save As, then BOTH the edited original document and the copy are saved, thus not only saving a new copy, but silently saving the original with the same changes, thus overwriting the original." Just goes to show: do not mess with my ability to save my stuff. There is no one-size-fits-all for this kind of delicate stuff.
Thread beginning with comment 530064
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: file versioning
by darknexus on Tue 7th Aug 2012 10:36 UTC in reply to "RE[7]: file versioning"
Member since:

From some quick googling, it seems to be storing them in /.DocumentRevisions-V100/ .

I found a detailed explanation here:
Quite cool how it was implemented, and at least it's smart enough to store the document revisions on the drive and partition that actually contains the document. I do agree though that at the moment, requiring two workflows can be jarring depending on the application you use. Still, if Apple had made it mandatory, I can only imagine the bitching that would result. With this, plus the ability to get the Save As command back even in programs that do support version control, I think everybody can be happy though at the cost of a little complexity. I rather hope that the majority of programs move over to this method in time. I won't deny that at first I absolutely hated it, however after reading up on how it actually worked and playing with it, I actually prefer using versions when possible. The drawback is, of course, that it depends on Mac-specific metadata which means you really can't share versions with non-Mac users even if you give it to them on a fat32 or NTFS formatted drive. No other os knows about Apple's versioning scheme and indeed, Windows has its own versioning mechanism for certain file types. Also, if you clean the Mac data from a drive you intend to share (something I always do before sharing it) your versions are erased from that drive. Therefore, always keep your source material on drives you don't intend to share.
It occurs to me that we really could benefit from an open standard along these lines. Of course, even if we had one, no one would implement it except *NIX. Still, a guy can dream.

Reply Parent Score: 3

RE[9]: file versioning
by henderson101 on Tue 7th Aug 2012 11:33 in reply to "RE[8]: file versioning"
henderson101 Member since:

You don't really need two workflows. You can use 1. If you always duplicate the document before you edit it, you are covered. If you don't want to duplicate it, then don't. Just assume that you are constantly saving the document in that background. That's all. This is how I've always worked and it scares me when people don't save regularly.

Reply Parent Score: 2