Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Auto Save – As in iOS, documents in applications written to use Auto Save will be saved automatically so users don't have to worry about manually managing their documents

Until it saves "just playing around" changes that you didn't want to keep, and now you have to wade through versions to find the one you wanted to keep or try to remember what changes you had made so that you can fix them.

Full-screen apps – Native, system-wide support for full-screen applications. Supporting applications display a new button at the top right of application window, this button opens applications in full-screen mode

Unless you have a second monitor which becomes almost useless in Full-Screen Mode. Snow Leopard has a Full-Screen mode and SL does it better.

Launchpad – An application launcher that displays an iOS-like icon grid of installed applications. It features the ability to make multiple pages and group apps into folders that function the same as folders in iOS

The equivalent can be done better with Stacks on Snow Leopard. Yes, you have to know how to set them up, but from what I've seen with Launchpad, it throws in more than just apps.

Multi-touch gestures – Similar to iOS, additional gestures performed using a multi-touch input device

I'm sure Snow Leopard could do this with a program like MagicPrefs. True MagicPrefs might not support all the gestures of Lion, but I'm sure they could be added.
 
I thought we were on color free association. Cocoa already got the brown;)
Coffee is not a color. It's a lifestyle.

That actually could make this thread in some minor way useful!


I mean, after all, the thread title is just an awkward way of asking "What's New in Lion?" -- actually I'm not sure why it hasn't been merged with the many other threads of the same nature or at least wastelanded.
 
Until it saves "just playing around" changes that you didn't want to keep, and now you have to wade through versions to find the one you wanted to keep or try to remember what changes you had made so that you can fix them

The equivalent can be done better with Stacks on Snow Leopard. Yes, you have to know how to set them up, but from what I've seen with Launchpad, it throws in more than just apps.

Can you elaborate on these points above.
 
Nope. Cocoa is a programming language based in Objective-C. It has nothing to do with the on-screen painted images of widgets and windows. It might help arrange them but they are just typical image files (.png, .tiff etc.)
Cocoa is considered a "native" language and what Apple would prefer developers to code in through Xcode. Carbon on the other hand is a native wrapper to port older C based languages into OS X. That's about as simple as I can explain it.

Understand now .I thought it was some OS layer or thing that control the finder .

I understand now it is programming language .


So my question what controls the on-screen painted images or the widgets and windows than?


Are there any web sites with skins out there ?
 
Understand now .I thought it was some OS layer or thing that control the finder .

I understand now it is programming language .


So my question what controls the on-screen painted images or the widgets and windows than?


Are there any web sites with skins out there ?

Yes. But you have to hack them yourself. They are contained in sartbin and artbin files in the system folder.
Go through the forums here:
http://macthemes.net/forum/viewtopic.php?id=16804368
 
iCal's birthday calendar no longer just shows "John Doe's birthday", but tells you how old John will be on that birthday.
 
***
Originally Posted by WSR
Until it saves "just playing around" changes that you didn't want to keep, and now you have to wade through versions to find the one you wanted to keep or try to remember what changes you had made so that you can fix them

The equivalent can be done better with Stacks on Snow Leopard. Yes, you have to know how to set them up, but from what I've seen with Launchpad, it throws in more than just apps.
***
Can you elaborate on these points above.

I often will do a save before I do some changes I'm not sure I will want to keep. For example, experimenting with fonts, colors, layouts, etc. I can do this in Snow Leopard without hassle since I know that if I don't like it, all I have to do is simply close the file without saving and reload where I last saved. In Lion Autosave could save while I'm experimenting. Leaving me with the "fun" of looking through versions to find the save that I want. Note that Lion's Resume also makes doing what I do in Snow Leopard more difficult.

In Snow Leopard I have a folder called Stacks. In it I have sub-folders for different groups of apps, i.e. System, Audio-Video, Tools, etc. In the sub-folders I put shortcuts, aliases, to the apps that I want easy access to of that group. Finally I drag the sub-folder to the dock, and when I click on it, it shows me the apps in that sub-folder. So it's the apps that I want and organized like I want it. Launchpad in Lion puts everything in any folder you include in it unless you do the same as above, create folders with shortcuts.

This video I found shows some of the issues talking about along with other frustrations of Lion.
http://www.youtube.com/watch?v=ui9d7ZRlnBs&feature=related
 
Lion just doesn't have anything I really need.

Will be taking it off and going back to Snow Leopard which will seem like a big upgrade because stuff will actually work again...
 
Leaving me with the "fun" of looking through versions to find the save that I want. Note that Lion's Resume also makes doing what I do in Snow Leopard more difficult.

http://www.youtube.com/watch?v=ui9d7ZRlnBs&feature=related

Not to say it will take up more hard-drive space to have many versions saved.

It sounds nice but looks like computers that lack hard-drive space this is not a good option.


How does this resume thing work?
 
How does this resume thing work?

My understanding is that when you close an app, like a word processor, instead of asking you "Do you want to save?", it instead just saves the current state of the app and closes. Then when you reopen the app, it comes up in the state that you last closed it including reopening the file you had open last. I don't know if it saves the document to its file or just where it saves the state.

To me Resume has a lot of places where it could cause unexpected results. For example, if you attach the file to an email, it might not be the version you where expecting.

Note that this and what I've posted earlier comes from what I've read. I haven't updated, or downgraded as some would say, to Lion since for me Snow Leopard is the better OS. To me the downgrading of Spaces and Expose, the near uselessness of a 2nd monitor in Full-screen mode, and the loss of the "Save As..." are major problems in Lion.
 
OP, I suggest you go back to Ars' Lion review to learn more about Lion's new features. It looks like to me you are confused about what's being offered in Lion.
Ars' review has pretty much everything covered. If not, search around the forums.
 
OP, I suggest you go back to Ars' Lion review to learn more about Lion's new features. It looks like to me you are confused about what's being offered in Lion.
Ars' review has pretty much everything covered. If not, search around the forums.

The only thing I'm confused about is this resume thing and how that works and why some people hate it.
 
if you attach the file to an email, it might not be the version you where expecting.

That's what Lion's File Coordination APIs are for. You will always be attaching the current version of the file.
 
That's what Lion's File Coordination APIs are for. You will always be attaching the current version of the file.

But what if the "current version" has some playing around edits that you didn't want to keep. Since it's my understanding that the app won't ask you "Do you what to save?" anymore when it is closed, it doesn't give you a reminder that there may be changes you don't want to keep.
 
But what if the "current version" has some playing around edits that you didn't want to keep.

Then you will be sending these changes along. It's actually a pretty simple philosophy under Lion. Just imagine the document (on disk) to always be in the same state that it is displayed as. If you didn't intend to keep your edits, you should have either undone them or reverted to an earlier version, before attaching the document to an email.

Note that you run into problems on Snow Leopard as well, if you've made changes to a document, which you intended to keep but forgot to save before sending the document off.
 
Last edited:
The only thing I'm confused about is this resume thing and how that works and why some people hate it.

Besides the potential problems I've mentioned earlier, for me I want apps to come up in a clean state. If I want to reopen the file I was editing last, then I'll just open it. That's easier than always having to close out the old document, or remembering to use some key sequence when closing the app. Even on my IPod touch, I occasionally fully close all apps that are currently running. This keeps more free memory so the apps run better.
 
Then you will be sending these changes along. It's actually a pretty simple philosophy under Lion. Just imagine the document (on disk) to always be in the same state that it is displayed as. If you didn't intend to keep your edits, you should have either undone them or reverted to an earlier version, before attaching the document to an email.

Note that you run into problems on Snow Leopard as well, if you've made changes to a document, which you intended to keep but forgot to save before sending the document off.

True, but what this ultimately comes down to is I want to decide what is the current version. I don't want Lion making that decision.

Also note that the easiest way to undo a number of edits is to close the app without saving, and reload the last save. Resume and Autosave would make this harder since you would now have to hunt though Versions to find the one that you want.
 
True, but what this ultimately comes down to is I want to decide what is the current version. I don't want Lion making that decision.

I understand. But Lion doesn't really make any decision for you. It doesn't need to decide what the current version is, the current version simply is whatever the document looks like after your last change, basically by definition. It's equivalent in concept to how changes made in a real paper document you have lying on your desk work, except that you have the ability to undo changes or go back to previous versions. Apple have (more or less) eliminated or are trying to eliminate the possibility of the file on disk being different from its representation on screen.

Have a look: http://cl.ly/0g1w263z3N151i0q1R0v. At no point in that video do I manually save.
 
Last edited:
Apple have (more or less) eliminated or are trying to eliminate the possibility of the file on disk being different from its representation on screen.

But I want them to be different. I want the file on disk to be what I definitely want to keep and what is on the screen to be what I am just considering to keep or not.

We are just talking about personal preferences. Fortunately it's my understanding that Resume and AutoSave can be turned off. So each of us can use these features or not. So we don't have to agree which is better. I just hope Apple keeps the option to turn it on or off, and if you turn Resume off the app will ask "Do you want to save?"
 
Fortunately it's my understanding that Resume and AutoSave can be turned off.

AFAIK Autosave can't be turned off. Most apps aren't implementing it yet, though.

if you turn Resume off the app will ask "Do you want to save?"
No it won't. :eek:

------
(EDIT) Oh, another thing...:

I often will do a save before I do some changes I'm not sure I will want to keep. For example, experimenting with fonts, colors, layouts, etc. I can do this in Snow Leopard without hassle since I know that if I don't like it, all I have to do is simply close the file without saving and reload where I last saved. In Lion Autosave could save while I'm experimenting. Leaving me with the "fun" of looking through versions to find the save that I want. Note that Lion's Resume also makes doing what I do in Snow Leopard more difficult.

In Lion, you don't have to look through versions either. You can either select "Revert To Last Saved Version" (if you manually saved a version before experimenting, or "Revert To Last Opened Version".

Alternatively, before experimenting, you can simply choose to duplicate the document. If you like the changes, you can save the duplicate under the original name.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.