stefano67 wrote:
even simpler: avoid Lion and pages altogether
Well, I've taken a hybrid approach to this.
Pages is my word processor of choice, and has been ever since it came out. When the Classic environment breathed its last and I had to give up my beloved WriteNow, Pages came the closest as a logical replacement. I would give up writing altogether before I would use Word.
Because of the loss of Save As, I have "avoided" Lion in my work environment, and will continue to do so unless the option to restore Save As and eschew Auto Save and Versioning is made available.
I was unable to avoid Lion at home, as I had to replace an aging Mac and had no choice when buying a new one — Lion was pre-installed, and I don't feel confident enough nor I do I have the will to jump through the many hoops that would be necessary to get Snow Leopard running on it.
As I seldom do critical word processing at home, I've managed OK. But I have thousands of legacy documents in Pages at work, and furthermore, I like Pages and want to continue working in it.
I refuse to go through the nonsense necessary in Lion to arrive at the same result Save As gives you in Snow Leopard (i.e., six steps vs. two steps). For now, I can carry on as before in Snow Leopard, as there are no other Lion features so compelling that I feel the need to upgrade.
At some point down the road, though, my work computer will have to be replaced, and I honestly don't know what I'll do then if Apple has persisted in forcing Auto Save/Versioning upon its apps, with no option to disable it.
In the course of this long debate, both here and in other threads (and it other forums as well), I have repeatedly asked for anyone to point out another change in the history of working on a Mac that is as radical as the change in Saving paradigm introduced in Lion. I have repeatedly asked for anyone to point out a change that has resulted in a greater uproar from the Mac community than this one.
Not a single one of Lion's defenders has answered these questions — including the loudest of the bunch, whom we've just heard from again here. While they talk big otherwise, they don't have the courage to address these questions...they just ignore them. (Watch now as this happens yet again.)
Similarly, when people come forth with real-world examples of how this change has wreaked havoc with their workflows and actually resulted in destruction of their data, Lion's defenders just whistle and look the other way, rather than acknowledging that their "perfect" system has some very obvious flaws.
What's disturbing is that, to-date anyway, Apple itself seems to be taking this same approach — that is, to ignore the uproar and carry on with their "we know what's best for you" attitude.