On Sep 7, 2012, at 10:54 AM, Kyle Sluder wrote: > On Fri, Sep 7, 2012, at 10:49 AM, Charles Srstka wrote: >> On Sep 7, 2012, at 10:01 AM, Kyle Sluder <k...@ksluder.com> wrote: >> >>> I must stress that this is nothing more than an educated guess on my part. >>> But if people find Lion Autosave confusing enough by itself, do you think >>> Apple really wants two saving paradigms forever? >> >> There are certain types of apps for which autosave doesn't really make >> sense, though: >> >> - An app that's primarily a viewer rather than an editor doesn't have >> much use for autosave. > > If it doesn't make any edits, then nothing will be saved.
Not true. XCode is a prime example of this: open an ancient 3-file format nib that you haven't got round to converting yet, and suddenly you have a 2-file format nib. Which is especially annoying because it's under source code control and it's *locked*. XCode's concept of what constitutes a "change" to a nib isn't the same as mine and undo or revert don't work. It's not the only app that's changed its underlying formats over the years, and sometimes you don't want to update a file's format just because you did something by accident and didn't undo in time. My contribution to the list of things that should not autosave: Virtual machines. But then we aren't using NSDocument save at all, because we're writing to it constantly. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
