4 ms·
Well that particular one we don't have to worry about. The expectation of having to explicitly 'save' an electronic file is (finally) on its way out.
by roc 14y ago
Well that particular one we don't have to worry about.
The expectation of having to explicitly 'save' an electronic file is (finally) on its way out.
- maaku 14y agoReally? Than what do you call the action of making particular snapshots of file state?
- shanselman 14y agoA camera? (snapshot)
- user24 14y agoIn the future, there is no such action. Everything is recorded with an infinite rollback history.
- maaku 14y agoThat doesn't fit many use cases. What if you want to preserve a particular version of the file? Yes, I understand all versions are kept in the infinite rollback history, but what about the UI element?
- roc 14y agoCopies. Save is going away. Save As is going the way of "duplicate"/"fork".
- alttag 14y ago... only in Lion. I've been using that workflow for nearly a year now, and it's still driving me batty. It's inconvenient and backward, and I hope it gets reverted.
- roc 14y agoIn anything with an auto-save-by-default workflow. Consider draft messages in modern mail clients. Some still have a manual 'save' button. But that's a transition thing. They'll go away as users learn they can trust the autosave. Most of the awkwardness in Lion came from the shortcut keys having been wrong and the effect having been jarring for its lack of vestigial commands to ease the minds of those not-yet-convinced.
- lloeki 14y agoI find this new workflow nice by itself, but what's driving me batty is having two models side by side i.e some apps use open/save/save as while others use open/autosave/versions/duplicate. My SO, though, finds it downright fantastic.