WHAT IS THE CORRECT PROCEEDURE WHEN USING SAVE TO SAVE A DOC IN LION?

Apple's new human interface guidelines say to all developers of document-based apps to replace Save As with Duplicate. We can only guess how many developers will be following this guideline.

But, I will hazard a guess that more and more developers will be following all of Apple's guidelines more closely than ever, especially if they expect their apps to be approved for sale through the Mac App Store.

You don't save anymore. When you close a document and want to keep it, you will have to give the document a name and put it somewhere. Otherwise, there is no need to perform any save operation unless you want to save one particular version of a document for later reference. If you don't need any versions, you don't ever need to save.

Really? Then, why this?

Yes, really. How does that invalidate anything I said above? If you want to retrieve a document after closing it, you must give it a name and pick a location. Performing any "save" operation is purely optional.

I think that people who are having a difficult time comprehending how Lion works in the regard might understand it better by remembering that they never, ever need to save a document anymore. You can continue to use Lion as if it were Snow Leopard, but you would be defeating the purpose. Your data wounldn't be any more safe and you would be clogging up your versions. Just don't save.

etresoft wrote:

If you want to retrieve a document after closing it, you must give it a name and pick a location. … they never, ever need to save a document anymore.

Maybe it's my pinheaded misunderstanding of language, but that operation is SAVING the document. Thus, to preserve your so-called version or retrieving one is what SAVE it means. Don't take those steps and nothing is saved.

baltwo wrote:

Maybe it's my pinheaded misunderstanding of language, but that operation is SAVING the document. Thus, to preserve your so-called version or retrieving one is what SAVE it means. Don't take those steps and nothing is saved.

Perhaps it might make more sense to consider "saving" to be a low-level operation in Lion. Yes, it still happens, but the end-user no longer needs to perform it. End users also don't have to worry about updating file system inodes or ensuring that virtual memory pages get swapped in or out.

Thanks for clarifying. AFAIK, your examples have never been user actions. That's why all the clamor about automating previous user actions w/o anyway to control or turn it off. The OS always did things that weren't of any concern to the user, saving stuff shouldn't, IMO, be one of them.

Well, I for one am going to be really screwed with this. If I don't save a doccument anymore, and I move to an editing system with this new habit, I will lose a ton of work and watch clients walk out the door. Of course, I am talking about "new habits" vs. old here - and older machines will be around for quite awhile, doing the production work - many still in MS XP for things like Toaster, Pinnicle, Vegas and so on.

This trend of changing things to fit iOS usage is beyond irritating - it borders on dangerous for the working environment. It is one thing to have nifty silly apps and gestures on your pad or phone, but at work it is distracting and difficult.

Before anyone says it - yes, I have a choice... and I am getting ready to take this new machine that did not give me the choice, buy a set of SL disks, wipe this HD and back up to something more production friendly (as opposed to young adult social community tageted).