Currently Being ModeratedJul 30, 2012 11:00 AM (in response to William Mulloy)
Sigh. I used to open up a document, make a bunch of changes, and "Save As" a new version. For this type of workflow, because of Autosave and Versions, restoring the "Save As" command is meaningless.
Try this out in (Lion/Mountain Lion) TextEdit.
1. Create a new TextEdit document and type the word "Original". Save the document and call it DocumentA
2. Close it and reopen it. Change the word "Original" to "Modified". Save As ... DocumentB. Close it.
3. Reopen both documents. The word "Original" is gone. That is because A was autosaved/versioned while you were working on it. So unless you do a "Save As" before you ever start making changes (which is not what you used to have to do) you will have to revert DocumentA to get your "Oiginal" back.
Essentially you still have to do a "Duplicate and Revert" to preserve the "Original". The new command has given us back nothing.
Currently Being ModeratedJul 30, 2012 11:18 AM (in response to ericsiegel01)
Testing using the new paradigm:
1) create a new TextEdit document and type "Original". Save it as DocumentA
2) Close and reopen it.
3) Duplicate and change "Original" to Modified. Save it as DocumentB. Close it
4) reopen both documents. DocumentA is "Original" and DocumentB is "Modified"
Duplicate the document before making edits and there is no need to revert.
True. And anyone who is happy with the new paradigm and the different steps required to achieve the previous result is ... happy. Having used both I do not think it is an improvement. To each his own. My example was a response to those who took Apple's reinstatement of the previous command to mean that it has reinstated the previous workflow.
Currently Being ModeratedJul 30, 2012 12:36 PM (in response to ericsiegel01)
Thanks, at least with regard to Save As, it sounds like it is not 100% the same, but is at least an improvement over Lion, as long as one does Save As before making changes rather than after.
Maybe we can hope that 10.9 gets it 100% right.
Currently Being ModeratedJul 30, 2012 4:04 PM (in response to William Mulloy)
this link has the answer. worked for me :-)
Currently Being ModeratedJul 31, 2012 5:24 PM (in response to ericsiegel01)
The good old functionality of the command "Save As" can be reproduced with the command "Export". At least in Mountain Lion using Preview with PDF files.
Open for example a PDF file, do some changes and "export" this file. A new file will be created - just like using "save as" in the traditional way.
Closing the open file will now pop up the menu asking if you want save the changes you have done or not - just like using "save as" in the traditional way.
That´s how I solved the problem - at least for doing changes to a PDF file without autosaving the original file when closing it.
Currently Being ModeratedAug 13, 2012 5:36 PM (in response to William Mulloy)
I actually use the "Save As.." mostly to indicate the path to the current file, and for that, I'm thankful for the return (unless there is another way to find this information).
When I actually do use Save As, it is because I want to experement, and if that experimentation (photo editing for example) turns out to be successful, I want to save a new copy without mucking with the original. The work flow to do this in the brave new world, "duplicate" before mucking, is a significant paradigm shift which 30 years of practice rebells against. But there is a greater problem...
I open a Pages file, do a "Duplicate" make changes, and quit. I go to the directory where the original file existed, and the new duplicate is no where to be found. Fortunately, Finder search finds the file in another folder. The "save" dialog, which appears in the window title, doesn't give any indication of where things will be saved. So, I'm wondering how this helps me not loose data?