On 07/09/2012, at 8:37 AM, Kyle Sluder <[email protected]> wrote: > Opting in to > +autosavesInPlace doesn't seem like it's there so you can decide whether > to adopt it based on user feedback;
We've also had a lot of feedback from users who dislike this feature. Once again Apple are foisting things upon Mac users that they like, but which are widely disliked. Whatever happened to 'the user is in charge'? While I can see the benefit of Autosave, I think the degree of disruption to the UI it creates is throwing out years of well-established familiarity for users and introducing behaviours that don't make much sense for many of them. The feedback we've received is that a lot of users just haven't got any idea what's going on: why things suddenly open unbidden, odd messages that they are unsure how to respond to, and menus they aren't familiar with hiding behaviours that don't make sense. Many of these new features and behaviours have been called out as bugs in the app. Fact is, grafting on something that does make sense on a phone onto a desktop OS with a long tradition of doing things in a different way is confusing a lot of people. Apple might be pretending it isn't happening, but they've become the sort of company that no longer listens anyway. For developers, NSDocument has become quite a muddle, and was always a fairly complex class to deal with (in terms of what gets called when). With sandboxing, autosave becomes effectively compulsory. Has Mac OS X/Cocoa "jumped the shark"? I hope not but it's not clear that it hasn't. --Graham _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
