The point I was trying to make and probably did a poor
job of as usual, is that Cocoa is fine for MacOS
development projects, those projects that use the
unique features and benefits of the Mac platform to
enhance applications beyond what could be done under
other OS platforms. However, there are many
applications that are cross-platform, therefore there
should be a simpler way to maintain both a Windows and
MacOS version of these apps. Heck, let's throw in
Linux as well! I have written a number of engineering
apps that I want to run under different OS's. How do I
do this? Well, they're all command line because
there's no way in hell I'm going to write GUIs for
three different platforms. Maybe I'm wrong, but it's
my perception that building a GUI app under Windows or
Linux is easier than doing a Cocoa app. I'd still do a
carbon app any day over Cocoa as long as Carbon is
still going to be around for a while.
--- Dave Camp <email@hidden> wrote:
>
> On Jun 13, 2007, at 5:40 PM, Tony Scaminaci wrote:
>
> > Carbon was intended as a transitional API from OS
> 9 to OS X and it
> > worked well for that purpose. Carbon's been around
> since the advent
> > of OS X so how long do you keep a transitional API
> alive? The
> > problem here is that the replacement API (Cocoa)
> is nothing like
> > carbon and as Larry has said, it's much more than
> just an API. It's
> > an entirely different philosophy of programming
> and one that is not
> > cross-platform. Hind sight is 20/20 but maybe a
> better thing to do
> > would have been to develop an API similar to
> Windows (heretic!!!)
> > given the fact that we're now transitioning to
> Intel anyway. If
> > Apple had done that instead of ramming Next's
> Cocoa API into XCode,
> > maybe we'd all be better off as Apple developers
> today. The way to
> > keep the Mac viable is for software that people
> run under Windows to
> > also run under OS X. The stumbling block has been
> Cocoa because it's
> > so different.
>
> I've seen several statements in this thread to the
> effect of Cocoa "is
> not cross-platform", thus it's bad.
>
> I fail to see how this is relevant to the subject at
> hand: no 64 bit
> Carbon UI code in Leopard. If you are writing native
> Mac OS X UI code,
> it's platform specific by definition regardless of
> which language or
> API you use.
>
> Dave
> _______________________________________________
> Do not post admin requests to the list. They will be
> ignored.
> Carbon-dev mailing list
> (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
