> Cocoa is where you should go eventually (in every case), it's just if you
> want to make a quick pit stop on Carbon so that people can use your app in
> OSX instead of Classic.
I disagree with the "in every case".
Cocoa is the clear winner if:
1) You're writing a new application
2) You won't be supporting MacOS Classic
But as much as Apple likes to talk about "just change 5% to 20% of your
code", it's all not-quite-a-lie. Cocoa, done right, is a rewrite, in
another language (Objective C). Don't get me wrong, it's a great
application development environment. But if you're just changing 5% of your
code, you're almost certainly not really taking advantage of Cocoa.
*AND*, if you want your app to support both Classic and OS X, Cocoa provides
no joy.
But give it 18 months, if there's sufficient demand, someone will create a
framework that allows Cocoa apps to run under MacOS Classic.
mikel
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
