@Kevin Walzer: I'm not sure I agree with the Cocoa interface purity (or snobbery, depending on your point of view) that I'm seeing here
I was painting with broad strokes mentioning Cocoa. I didn't at all mean to say that Carbon apps can't provide a real Mac experience. Final Cut Pro is very much a real Mac app, and certainly it is based on Carbon. Really the point of the post is the nature of cross-platform development, not Cococa or Carbon.
Seven Carbon apps, four Cocoa apps..., a Java/Aqua port of an X11 app, and two X11 apps deployed as standalone app bundles
I count five Cocoa apps: Safari, Mail, Terminal, Vienna and Preview. For what it's worth.
Honestly, I really don't care if it's written in Cocoa or Carbon if the experience is pleasing. The point of this thread is what new developers should look at. In most cases, the best bet is a Cocoa-centric UI layer which can optionally call into existing "business logic" C and C++ libraries.
I simply don't think Cocoa is essential to providing a good user experience; understanding the HIG *is* essential
I don't know if you need to understand the wording of the guidelines specifically, but certainly the ideas that they describe. In a sense, I think it's also just as important to know when to go outside of what they suggest.
by Scott Stevenson — Mar 22
I was painting with broad strokes mentioning Cocoa. I didn't at all mean to say that Carbon apps can't provide a real Mac experience. Final Cut Pro is very much a real Mac app, and certainly it is based on Carbon. Really the point of the post is the nature of cross-platform development, not Cococa or Carbon.
Seven Carbon apps, four Cocoa apps..., a Java/Aqua port of an X11 app, and two X11 apps deployed as standalone app bundles
I count five Cocoa apps: Safari, Mail, Terminal, Vienna and Preview. For what it's worth.
Honestly, I really don't care if it's written in Cocoa or Carbon if the experience is pleasing. The point of this thread is what new developers should look at. In most cases, the best bet is a Cocoa-centric UI layer which can optionally call into existing "business logic" C and C++ libraries.
I simply don't think Cocoa is essential to providing a good user experience; understanding the HIG *is* essential
I don't know if you need to understand the wording of the guidelines specifically, but certainly the ideas that they describe. In a sense, I think it's also just as important to know when to go outside of what they suggest.