<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"  xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">
	<channel>
		<title>TidBITS: Comments on The Very Model of a Modern Mountain Lion Document</title>
		<link>http://tidbits.com/</link>
		<description>Mountain Lion brings some changes to the interface whereby users interact with documents in autosaving applications. These changes might well overcome user objections to the Modern Document Model introduced in Lion.</description>
		<language>en-us</language>
		<copyright>Copyright 2012 TidBITS Publishing Inc.</copyright>
		<pubDate>Thu, 20 Sep 2012 00:00:00 EDT</pubDate>
		<lastBuildDate>Thu, 20 Sep 2012 00:00:00 EDT</lastBuildDate>
		<managingEditor>editors@tidbits.com (TidBITS Editors)</managingEditor>
		<webMaster>editors@tidbits.com (TidBITS Editors)</webMaster>
		<creativeCommons:license><![CDATA[http://tidbits.com/terms/]]></creativeCommons:license>
		<image>
			<title>TidBITS</title> 
			<url>http://tidbits.com/images/tb_logo_152x55.png</url> 
			<link>http://tidbits.com/</link> 
			<height>55</height>
			<width>152</width>
			<description>TidBITS badge</description> 
		</image>
		
		<item>
			<title><![CDATA[Comment from Matt Neuburg]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15746</link>
			<pubDate>Thu, 20 Sep 2012 11:46:05 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15746</guid>
			<author><![CDATA[comments@tidbits.com (Matt Neuburg)]]></author>
			<description><![CDATA[See now <a href="http://tidbits.com/article/13284.">http://tidbits.com/article/13284.</a> This problem is solved.]]></description>
		</item><item>
			<title><![CDATA[Comment from joaquin]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15742</link>
			<pubDate>Thu, 20 Sep 2012 09:39:39 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15742</guid>
			<author><![CDATA[comments@tidbits.com (joaquin)]]></author>
			<description><![CDATA[Thanks, Peter Waslowski, for keeping attention on the major change in SaveAs: it no longer discards changes to the originally opened document since the last Save.  <br><br>Thanks, Slim, for calling attention to the work-around.<br><br>The work-around ain't easy.  <br><br>To get back the behavior we have been relying on for decades--separating a changed document from the original--which was accomplished in one step by using SaveAs without first saving the open document, the process is now: don't Save; SaveAs; reopen the original; invoke Versions; find the version that is the last explicitly saved version; Save.<br><br>Won't that be error prone?  Or is the last saved version easily found using Versions?]]></description>
		</item><item>
			<title><![CDATA[Comment from Dah•veed]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15521</link>
			<pubDate>Wed, 29 Aug 2012 23:25:33 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15521</guid>
			<author><![CDATA[comments@tidbits.com (Dah•veed)]]></author>
			<description><![CDATA[The command to duplicate files in the Finder is Command+D.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15520</link>
			<pubDate>Wed, 29 Aug 2012 23:22:47 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15520</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Very cool! That does seem to work in TextEdit, Preview, and Pages here.]]></description>
		</item><item>
			<title><![CDATA[Comment from Dah•veed]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15519</link>
			<pubDate>Wed, 29 Aug 2012 23:10:37 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15519</guid>
			<author><![CDATA[comments@tidbits.com (Dah•veed)]]></author>
			<description><![CDATA[You can return the Save As… command to the File menu with it's traditional key command by adding it as a Keyboard Shortcut. By using the traditional key command I am not aware that it effects other commands.<br><br>1. Open System Preferences from the Apple menu and go to Keyboard/Keyboard Shortcuts <br>2. Choose Application Shortcuts from the list on the left <br>3. Click the plus button [+] at the bottom to add a new shortcut <br>3. Type Save As… with the ellipsis for the Menu Title <br>4. Use the traditional Command+Shift+S (or anything to your liking) for the Keyboard Shortcut <br>5. Finally, click Add <br><br>You should now see Save As… in the File menu in apps throughout OS X. It should push Duplicate farther down in the File menu rather than replacing it, as it did using the Option key.]]></description>
		</item><item>
			<title><![CDATA[Comment from William H Boyd Jr]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15480</link>
			<pubDate>Sun, 26 Aug 2012 22:57:56 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15480</guid>
			<author><![CDATA[comments@tidbits.com (William H Boyd Jr)]]></author>
			<description><![CDATA[I just discovered that, with the "Ask to keep changes when closing documents" option checked, if I edit a file on a network volume, as soon as I make a change to the file, the black dot appears, as you'd expect.  However, the dot doesn't disappear when I do a File &gt; Save, as happens when I'm editing a local file.]]></description>
		</item><item>
			<title><![CDATA[Comment from Peter Waslowski]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15424</link>
			<pubDate>Tue, 21 Aug 2012 03:21:41 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15424</guid>
			<author><![CDATA[comments@tidbits.com (Peter Waslowski)]]></author>
			<description><![CDATA[I have already tested it and it seems to work this way.]]></description>
		</item><item>
			<title><![CDATA[Comment from Slim]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15418</link>
			<pubDate>Mon, 20 Aug 2012 19:49:03 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15418</guid>
			<author><![CDATA[comments@tidbits.com (Slim)]]></author>
			<description><![CDATA[It seems that way as you suggest, if autosave continues to function the way you would expect (save your "old" document when you do "Save as"), so you haven't really lost the "old document" when you quit.<br><br>I'm not 100% sure if autosave would save your "old document" when you do "Save as" though; I guess you can do a test to check it.]]></description>
		</item><item>
			<title><![CDATA[Comment from Peter Waslowski]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15413</link>
			<pubDate>Mon, 20 Aug 2012 05:28:01 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15413</guid>
			<author><![CDATA[comments@tidbits.com (Peter Waslowski)]]></author>
			<description><![CDATA[I was also concerned about the Save As behavior. Having read your excellent article I understand what's going on. Thanks! <br>Now please tell me if I am missing something: When I save a doc via Save As… and give it a new name, the "old" document is closed. Unlike before, it is saved in the state it has at the moment I perform the Save As… command. This seems to be a problem because unwanted alterations are kept and not, like before, discarded. <br>BUT NOW: When I open the "old" document again and select "Revert to…/Previous Save" in the File menu I get the last version of the document before I did the Save As…, don't I? So, nothing of the functionality is really lost, isn't it?]]></description>
		</item><item>
			<title><![CDATA[Comment from Padre Cohen]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15360</link>
			<pubDate>Tue, 14 Aug 2012 18:14:07 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15360</guid>
			<author><![CDATA[comments@tidbits.com (Padre Cohen)]]></author>
			<description><![CDATA[Mountain Lion's document handling is a solution in search of a problem.]]></description>
		</item><item>
			<title><![CDATA[Comment from Al]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15359</link>
			<pubDate>Tue, 14 Aug 2012 11:41:30 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15359</guid>
			<author><![CDATA[comments@tidbits.com (Al)]]></author>
			<description><![CDATA[I read this nicely thought out article. Now my head hurts. Where's my coffee?]]></description>
		</item><item>
			<title><![CDATA[Comment from Jason]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15357</link>
			<pubDate>Tue, 14 Aug 2012 09:52:18 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15357</guid>
			<author><![CDATA[comments@tidbits.com (Jason)]]></author>
			<description><![CDATA[OMG! I never noticed that black dot in the red close button before. After how many years? It's so useful, so unobtrusive and so frustratingly Apple - elegant to the point of obscurity:|  It's like their whole user interface is composed of Easter eggs.]]></description>
		</item><item>
			<title><![CDATA[Comment from Jason]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15358</link>
			<pubDate>Tue, 14 Aug 2012 09:42:19 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15358</guid>
			<author><![CDATA[comments@tidbits.com (Jason)]]></author>
			<description><![CDATA[Whoah!  The rest of this article made my head spin, which is, by no means, the author's fault.  Methinks I'll stay with Snow Leopard a little longer after all:(]]></description>
		</item><item>
			<title><![CDATA[Comment from Michael  Warshauer]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15355</link>
			<pubDate>Tue, 14 Aug 2012 02:02:34 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15355</guid>
			<author><![CDATA[comments@tidbits.com (Michael  Warshauer)]]></author>
			<description><![CDATA[Yes; what ever happened to "Macintosh-the computer for the rest of us."?]]></description>
		</item><item>
			<title><![CDATA[Comment from Richard Fairbanks]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15353</link>
			<pubDate>Mon, 13 Aug 2012 20:48:57 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15353</guid>
			<author><![CDATA[comments@tidbits.com (Richard Fairbanks)]]></author>
			<description><![CDATA[Thank you, Matt, for such a vital article!!<br><br>I commend Apple for restoring “Save As . . .  ” (and adding the two System Preferences/General prefs) as a means to honor the dictum:<br><br>“Never alter a user’s data without their permission.”<br><br>Imposing auto-save upon users violates this dictum to an extreme degree, thus the restoration of “Save As . . . ” is critical.<br><br>As Matt has so painstakingly noted, the glaring flaw in the current (OS X 10.8.0) implementation is that edits to a file, in an app that allows auto-save, are ALSO saved to the original file when “Save As . . . ” is selected from the “File” menu.<br><br>This is absolutely unacceptable and must be remedied ASAP. Until then, OS X 10.8 is unreliable and thus unusable in a production environment.<br><br>Apple needs to be relentlessly (lovingly!) impressed upon about this, and the means is via: <a href="http://www.apple.com/feedback/macosx.html">http://www.apple.com/feedback/macosx.html</a>]]></description>
		</item><item>
			<title><![CDATA[Comment from David Morrison]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15350</link>
			<pubDate>Mon, 13 Aug 2012 19:19:42 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15350</guid>
			<author><![CDATA[comments@tidbits.com (David Morrison)]]></author>
			<description><![CDATA[I think you are being a bit optimistic here. VMS file names had a version number as part of the name. Each time you edited a file, the default was to save a new file with the same name and the version number increased by one. So you did have versions, but only from the end of each editing session. You couldn't go back to part way through an edit.<br><br>Secondly, the autosave behaviour was a feature of certain text editors. It was not built into the operating system and did not apply to all editors or any other applications.<br><br>But you are right that VMS had features that are still missed.]]></description>
		</item><item>
			<title><![CDATA[Comment from samadore]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15338</link>
			<pubDate>Sat, 11 Aug 2012 22:57:59 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15338</guid>
			<author><![CDATA[comments@tidbits.com (samadore)]]></author>
			<description><![CDATA[Having not upgraded beyond Snow Leopard, I cannot choose a side in this debate yet. I have however been reading numerous articles on the issue in an attempt to prepare myself. I'd like to commend and thank Matt for being the first to explain the issues clearly enough that I believe I understand things. Kudos!]]></description>
		</item><item>
			<title><![CDATA[Comment from George]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15332</link>
			<pubDate>Sat, 11 Aug 2012 14:25:56 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15332</guid>
			<author><![CDATA[comments@tidbits.com (George)]]></author>
			<description><![CDATA[Apple should have left everything exactly as it was but have the document autosave for versions, that's all. And the option to turn it on/off... and when enabled the save item would be greyed or something. Instead they went crazy.]]></description>
		</item><item>
			<title><![CDATA[Comment from MoT]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15323</link>
			<pubDate>Fri, 10 Aug 2012 22:13:55 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15323</guid>
			<author><![CDATA[comments@tidbits.com (MoT)]]></author>
			<description><![CDATA[I've held off of upgrading to Lion or ML for the very reason that the "save" function has been crippled.  The idea that I first of all have to save a duplicate copy BEFORE doing any possible changes, out of fear that the original will be auto-saved and thus corrupted, is so asinine as to beggar belief.  I've been in IT for well over thirty years and this is the most idiotic thing I've seen in all of that time.]]></description>
		</item><item>
			<title><![CDATA[Comment from MoT]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15324</link>
			<pubDate>Fri, 10 Aug 2012 21:09:00 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15324</guid>
			<author><![CDATA[comments@tidbits.com (MoT)]]></author>
			<description><![CDATA[Agreed.  This has to be the most ignorant thing Apple could have ever done.  It's the equivalent of switching the brake and gas pedals and telling your users to "get over it"]]></description>
		</item><item>
			<title><![CDATA[Comment from rasmusdotse]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15318</link>
			<pubDate>Fri, 10 Aug 2012 16:08:24 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15318</guid>
			<author><![CDATA[comments@tidbits.com (rasmusdotse)]]></author>
			<description><![CDATA[I'm surprised Apple managed to create a stupid autosave, since there are several very useful and rational models for autosave in professional, but often expensive software.<br><br>One model for autosave is that autosaves are never done to the original document but to a separate trail of autosave copies that can be reached when needed. The original document is only changed when an explicit save is done by the user.<br><br>Another model is the session model where a document is always copied on opening and autosaved as long as its open, effectively creating session versions. Usually a session can also be saved explicitly in this model anytime a document is open.<br><br>It's a mystery how the current version of autosave managed to pass apples usability lab without complete rejection.]]></description>
		</item><item>
			<title><![CDATA[Comment from Mike]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15315</link>
			<pubDate>Fri, 10 Aug 2012 09:21:33 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15315</guid>
			<author><![CDATA[comments@tidbits.com (Mike)]]></author>
			<description><![CDATA["Bottom line: new functionality that requires the user to change his or her behaviour will annoy 90% of all users because 90% of all users are incapable of any behavioural change."<br><br>Again I point out -- you give us grief when we complain about functionality *being taken away* by the new saving/Save As paradigm.<br><br>And yet, you give a pass to the legions of irresponsible Mac users who were so "incapable of any behavioral change" when it came to saving regularly that a nanny system (Auto Save) had to be put in on their behalf. <br><br>The rest of us responsible Mac users wouldn't have a complaint about this if its implementation hadn't taken functionality *away* from us in the process.]]></description>
		</item><item>
			<title><![CDATA[Comment from Mike]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15313</link>
			<pubDate>Fri, 10 Aug 2012 01:41:12 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15313</guid>
			<author><![CDATA[comments@tidbits.com (Mike)]]></author>
			<description><![CDATA[If Auto Save and Versioning are the default, as I propose, then the "end user" has to do exactly nothing for them to work exactly as advertised.<br><br>Your fears about "complicating" the Mac experience are unfounded. Why would an inexperienced user go mucking about in Preferences in the first place, or even know to do so? And even if they did, any changes made to this default behavior could be put into effect only after the user clicks through one or more warning dialogs that clearly articulate what he/she is about to do (e.g., "You are about to turn off Auto Save. You will have to manually save your files from now on...otherwise you will be at risk for losing your data. Are you SURE you want to do this?").<br><br>Of all the items currently in Preferences, none controls an aspect of the everyday Mac experience more profoundly that the way in which data is saved. I think there's more than enough room to add this one.<br><br>Sorry...yours is NOT a rational argument.]]></description>
		</item><item>
			<title><![CDATA[Comment from Tom Robinson]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15312</link>
			<pubDate>Fri, 10 Aug 2012 00:50:33 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15312</guid>
			<author><![CDATA[comments@tidbits.com (Tom Robinson)]]></author>
			<description><![CDATA[The rational argument is that Apple likes to keep things looking as simple as possible to the end user, and this includes having the bare minimum of preferences.  A new preference here, a new one there... they all add up.<br><br>Notice how the Recent Items preference was coalesced from 3 settings to 1?  Apple's annoying a few power users (not me), but the strategy is working extremely well for them.]]></description>
		</item><item>
			<title><![CDATA[Comment from Mike]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15296</link>
			<pubDate>Fri, 10 Aug 2012 00:01:38 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15296</guid>
			<author><![CDATA[comments@tidbits.com (Mike)]]></author>
			<description><![CDATA[1) You asked a specific question about Duplicate. I gave a specific answer. What's the problem?  Save As in Mountain Lion does not function in the same way it does in Snow Leopard (and earlier...a total of 27 years earlier, to be exact). The larger point is that I (and millions of others) had a perfectly functional workflow for all those years, and it has now been taken away from me by those who think they know better than I do how I should work.<br><br>2) My methods have worked quite well for me in 24+ years of Mac computing. I consider myself to be quite able to determine the saving intervals that work best for me. And if I have ever lost data due to not saving, I blame myself, not my operating system. Where is your disdain for the bozos who are "not in their right mind" and who are so Save-challenged they need an Apple nanny to do it for them? THAT'S irresponsibility.]]></description>
		</item><item>
			<title><![CDATA[Comment from Mike]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15310</link>
			<pubDate>Thu, 09 Aug 2012 23:15:09 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15310</guid>
			<author><![CDATA[comments@tidbits.com (Mike)]]></author>
			<description><![CDATA["So when Lion introduced Versions and AutoSave, I immediate disabled them."<br><br>May I ask how you accomplished this? I would be overjoyed to find a method for disabling Auto Save and Versions that did not play havoc with the rest of my system.<br><br>I've seen reference to Terminal commands that can do this, but they've been accompanied by warnings that they screw up other aspects of the system's operation.<br><br>As I've said from the moment Lion was introduced, Apple could make 100 percent of its users happy if they retained Auto Save and Versioning as the default, but gave experienced users a simple means in Preferences to disable them. (This assumes that when they're disabled, true "Save As" as it has always worked is automatically restored.)<br><br>In all my running debates on this subject in many forums, not a single soul has advanced a rational argument as to why this would be a bad idea.]]></description>
		</item><item>
			<title><![CDATA[Comment from Marc]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15306</link>
			<pubDate>Thu, 09 Aug 2012 19:21:30 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15306</guid>
			<author><![CDATA[comments@tidbits.com (Marc)]]></author>
			<description><![CDATA["Save As" has worked the same way for as long as I've been using computers, which is a long time. One develops muscle memory for doing certain tasks. You can't just change overnight. Also, how many applications use this new paradigm? A small fraction, I'd venture. So now we have two entirely separate paradigms for document saving and revisioning. Pardon me for vocalizing how inconvenient this is.]]></description>
		</item><item>
			<title><![CDATA[Comment from Marc]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15307</link>
			<pubDate>Thu, 09 Aug 2012 18:39:06 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15307</guid>
			<author><![CDATA[comments@tidbits.com (Marc)]]></author>
			<description><![CDATA[Mike, thanks for this. "El Aura" seems to be one of these Apple loyalists who will brook no criticism, as if 100% of what Apple does is completely perfect and anyone who voices a concern is just a bone-headed whiner who can't keep up.]]></description>
		</item><item>
			<title><![CDATA[Comment from David Emme]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15301</link>
			<pubDate>Thu, 09 Aug 2012 17:36:26 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15301</guid>
			<author><![CDATA[comments@tidbits.com (David Emme)]]></author>
			<description><![CDATA[I agree. And frankly, I like the "old" saving behavior, which is part of why I'm still on 10.6<br><br>I think part of the problem under discussion here is that Apple shot themselves in the foot by bringing back a "Save As" menu item which behaves differently then the original. That menu item name comes with a set of expectations for anyone who has used a Mac for any period of time. Apple should have invented a new menu item name for this similar but not identical functionality.]]></description>
		</item><item>
			<title><![CDATA[Comment from mamablair]]></title>
			<link>http://db.tidbits.com/article/13187?rss#comments_15300</link>
			<pubDate>Thu, 09 Aug 2012 17:28:33 EDT</pubDate>
			<guid>http://tidbits.com/article/13187#comments_15300</guid>
			<author><![CDATA[comments@tidbits.com (mamablair)]]></author>
			<description><![CDATA[IMO, the key for using Save As properly is to always make sure you first do a regular Save, so the current document is truly saved. Then, and only then, Save As under a different name. This worked perfectly well from System 6 through Snow Leopard. So when Lion introduced Versions and AutoSave, I immediate disabled them. I was happy when Mountain Lion put Save As back for us old-timers. The only time I ever use Duplicate is when I'm in the Finder (using Command-D), although I suppose I might eventually start using the File menu to invoke it.]]></description>
		</item>	
		
	</channel>
</rss>