"Save As..." missing from Pages

And in addition to removing Save As…, you also don't get the little dot in the close button any more, to show you that you have unsaved work… this seems really strange to me…

The less you know the better… 🙂

That's New Apple's interpretation of "Less is More".

Peter

There is no need for this flag.

case 1 : you just create a new document. The window title doesn't embed the ".pages" name extension as long as you don't save the doc.

case 2 : you are working on a doc which was saved once. Autosave apply so you have nothing to do, your changes are automatically saved. Some users are even ranting because the autosave process may take precedence against what they are trying to achieve. If you close the document, the system automatically save it. It does that too when you quit the doc's window without closing it.

I wish to add that in this case, triggering Save… doen't change the contents of the saved file, it just store a new version in the hidden dedicated folder.

Honestly, I have some difficulties to describe that by the Mies Van Den Rohe's formula : "Less is more".

Yvan KOENIG (VALLAURIS, France) lundi 21 janvier 2011 14:46:47

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

Hmmm. it seems that the new Help files in Pages 4.1 don't reflect these changes... they still mention the 'Save As' command... unless I'm missing something...

Tim,

The Pages Help resource may be conflicted about whether to reflect the situation under Lion, or previous OS versions.

Users with Save As may still outnumber those with Duplicate.

Jerry

Yvan what happens when in Lion you have the demo version of Pages.

It has saved a series of documents in the first 3 months with both versioning, auto-save and auto resume.

Then you reach the end of your 3 month trial.

Pages tries to auto-resume, auto-save and version. But can't.

There seems to be at least one user here who has hit that thought bubble.

There is clever simplicity and there is stupid complexity. This falls into the later case where the user has to constantly think like the computer instead of like a human being, and simple tasks become a maze where the computer opens and closes gates behind your back.

Peter

Jerry, I would have thought that the Help files that ship as part of 4.1 would reflect the actual state of 4.1, wouldn't you?

PeterBreis0807 wrote:

Yvan what happens when in Lion you have the demo version of Pages.

It has saved a series of documents in the first 3 months with both versioning, auto-save and auto resume.

Then you reach the end of your 3 month trial.

Pages tries to auto-resume, auto-save and version. But can't.

There seems to be at least one user here who has hit that thought bubble.

There is clever simplicity and there is stupid complexity. This falls into the later case where the user has to constantly think like the computer instead of like a human being, and simple tasks become a maze where the computer opens and closes gates behind your back.

Peter

I guess that the engineers failed to imagine that three years after the package delivery some one will install the trial and apply the update 9.1.

Where is the problem ?

When the ONE month (exactly 30 days) trial period is finished, the app is no longer an editor but a reader.

So there is nothing to be Autosaved or to Versioned.

The docs become read only.

If for this or that odd reason a file is not locked, lock it by hand. From time to time, brains are useful.

Here is an alternate scheme:

The demo version is version 9.0.

If the user updated it as version 9.0.5 there is no problem.

If he updated to version 9.1, he use my script to remove the demo 9.1

Download the demo and apply the updater 9.0.5.

This way he will have a reader which will ignore what are AutoSave and Versioning.

It seems that the French formula "se noyer dans un verre d'eau" match perfectly what you described.

Yvan KOENIG (VALLAURIS, France) mardi 22 janvier 2011 10:42:56

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

TimDanaher wrote:

Jerry, I would have thought that the Help files that ship as part of 4.1 would reflect the actual state of 4.1, wouldn't you?

The User Guide matches the actual state.

Of course, if you read the scheme applying to 10.6 when you are running 10.7, you will get some surprises but in such case, the culprit is not the User Guide.

Yvan KOENIG (VALLAURIS, France) mardi 22 janvier 2011 10:47:24

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

argh! this is horrible. i've messed up so many documents. thank god for time machine. PAHLEEZE bring back SAVE AS....i'm begging you. and yes, i'll send a request thru the proper channels. just wanted to vent.

Ok but case 3 (my main usage) : you have keynote or pages document for client #1 and you want to use it to create a new document for an other client. You have to" duplicate" then "rename" then "move" (I have a French version so it is called "Deplacer" ) to the good customer folder. I do it 20 times a day. So if you have a solution I would thank you.

T

Since Lion or Mountain Lion every opened document gets saved instantaneously, you cannot avoid it! If you don't set it back, the old version thus getting lost forever.

This is a real bad bug!

Hello APPLE - are you listening?

😠 Please please set this idiotic new saving mode back to the old SAVE AS !!!!

Thanks

Stephan

Removing "Save As..." is a truly idiotic move. It beats the hockey puck into the weeds.

I am amazed that it got proposed, don't mind accepted.

I got caught just yesterday when it overwrote my file with changes I had made to the wrong copy.

The only redeeming feature was I could go back to the previous version even after the save and reinstate it as it was, but it got me thinking just how much of this nonsense OSX forces me though every day. Auto-"correcting" my work to the wrong version that I have to change back again. Doing so in a method that is the exact opposite to the way it does it on my phone and iPod. Inexpicable intermittent slow downs when typing. Safari losing connections and jumping in and out of my typing. Glitches in the UI. Jerkiness in the Finder when dragging and dropping that land files in the wrong spot… the list goes on and on.

OSX has reached the point that I feel I am constantly wrestling with it to get things done.

Whilst the older Classic OS may have bombed a lot more, I felt it was on my side whilst I was working, and I say this after 13 years of working with OSX.

Mention any of this to Apple and I am WRONG! No real counter argument or reasoning, just wrong for not seeing it Apple's way. Really the above is barely a smidgeon of what doesn't work or is an ongoing annoyance. I could write a very long book on what doesn't work, what is exhaustingly bad, inconsistent, cosmetic, indecipherable or just plain dumb, but it's pointless. There is no-one who is going to listen or do anything about it.

Talked to a PC user about the changes in Windows 8 that is doing similar havoc to PC Users' work, but at least they can revert back to more functional versions of their OS. Apple locks you into the Latest and Not So Greatest. Choosing something better is not an option.

Peter

How can you get Apple's attention about this? I now have to dulicate and rename it. On top of that it duplicates it in the current folder. In the past I could duplicate, rename, and move all with one menu item...Save As. What makes me mad is that I have been working with Apple products for almost 30 years. I normally love everything they do (with the exception of actually dumbing down iMovie). This has got to be the first time I actually have been mad about something. Saddly, I know Apple is not listening. Save as would have been returned to Pages in an update of some sort if they were. I guess I will fork out the money for a better product.