I want to throw my hat in to the "restore Save-As" pool. Save-As actually takes 3 steps now. Not only do you need to duplicate and save, but you also need to close the old document to end up in the same state that "Save-As" would have left you in. This is exactly what I want and use many times a day.
(I'm being pedantic, but actually this is a 4 step processes because the new window is in a different location on screen and may require repositioning.)
Adding more steps to a processes costs more than just wasted time. It creates opportunities for human error. This used to be an entirely safe action: "I don't want to touch the original document; I want to start a new document that is a duplicate of the original." With one action I know I safely have a new copy and won't be screwing up the original. Now there are several failure scenarios:
1) I can accidentally edit the old document instead of the new document. Granted versions lets me roll back, but versions is still a clunky system and that is a painful operation. It may also take me a long time to realize I made this mistake. Unraveling all that could easily take an hour of precious time. Even after I unraveled it, I don't think the new copy would get all the recent edit history that would have been there had I dont the "save-as" sequence correctly the first time.
2) I could forget to save the new copy.
2a. At a minimum this means I haven't assigned it a name or a location on disk. This can take effort to figure out if I come back later and don't remember what I was doing.
2b. If I quit and restart Omni Outliner it does restore the duplicate, but the undo buffer is gone. Previously OO would prompt me to save when I quit; since Lion it no longer does.
2c. If I haven't saved, Lion's versioning doesn't kick in.
As was said before, just because Apple says it is good doesn't make it so. In this case the "Save-As" feature isn't contrary to Apple's new Versioning and Application-Restore ideas. It fits in with them nicely. This seems to just be a case of premature simplification. I don't think "consistency across applications" is a good enough reason to blindly follow Apple's guidelines in this case. Omni apps should be mutually consistent, but the consistency cost compared to other company's apps is very small. Most of them break consistency in much larger ways. On the other hand, added work-flow overhead is actually pretty large.
Please restore Save-As.
(I'm being pedantic, but actually this is a 4 step processes because the new window is in a different location on screen and may require repositioning.)
Adding more steps to a processes costs more than just wasted time. It creates opportunities for human error. This used to be an entirely safe action: "I don't want to touch the original document; I want to start a new document that is a duplicate of the original." With one action I know I safely have a new copy and won't be screwing up the original. Now there are several failure scenarios:
1) I can accidentally edit the old document instead of the new document. Granted versions lets me roll back, but versions is still a clunky system and that is a painful operation. It may also take me a long time to realize I made this mistake. Unraveling all that could easily take an hour of precious time. Even after I unraveled it, I don't think the new copy would get all the recent edit history that would have been there had I dont the "save-as" sequence correctly the first time.
2) I could forget to save the new copy.
2a. At a minimum this means I haven't assigned it a name or a location on disk. This can take effort to figure out if I come back later and don't remember what I was doing.
2b. If I quit and restart Omni Outliner it does restore the duplicate, but the undo buffer is gone. Previously OO would prompt me to save when I quit; since Lion it no longer does.
2c. If I haven't saved, Lion's versioning doesn't kick in.
As was said before, just because Apple says it is good doesn't make it so. In this case the "Save-As" feature isn't contrary to Apple's new Versioning and Application-Restore ideas. It fits in with them nicely. This seems to just be a case of premature simplification. I don't think "consistency across applications" is a good enough reason to blindly follow Apple's guidelines in this case. Omni apps should be mutually consistent, but the consistency cost compared to other company's apps is very small. Most of them break consistency in much larger ways. On the other hand, added work-flow overhead is actually pretty large.
Please restore Save-As.