You know nothing about which you speak. Carbon and cocoa have nothing to do with the color of icons.
pssh....carbon is black like graphite and cocoa is brown like coffee
You know nothing about which you speak. Carbon and cocoa have nothing to do with the color of icons.
pssh....carbon is black like graphite and cocoa is brown like coffee
Well, you gotta ask somewhere
So what color is Java then? Orange?
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
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
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
Multi-touch gestures Similar to iOS, additional gestures performed using a multi-touch input device
Java usually refers to coffee.
I thought we were on color free association. Cocoa already got the brown
Coffee is not a color. It's a lifestyle.
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 ?
***
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
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
How does this resume thing work?
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.
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.
But what if the "current version" has some playing around edits that you didn't want to keep.
The only thing I'm confused about is this resume thing and how that works and why some people hate it.
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.
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.
Fortunately it's my understanding that Resume and AutoSave can be turned off.
No it won't.if you turn Resume off the app will ask "Do you want to save?"
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.