Re: Cocoa, a complete Mac OS X API?
Re: Cocoa, a complete Mac OS X API?
- Subject: Re: Cocoa, a complete Mac OS X API?
- From: Eric Peyton <email@hidden>
- Date: Wed, 13 Jun 2001 16:06:48 -0500
Almost all this things can be done using Carbon calls (making a
Carbon wrapper is one thing I do not have any idea on how to do)
buuuuut, I thought that Stevie told to us that the
state-of-the-art API for developing Mac OS X applications is
Cocoa, and Carbon is just to make the Mac OS 9 leap. But it turns
out that Carbon is more feature rich than Cocoa, in terms of Mac
friendship.
Look at those kind of features as icing on the cake. Cocoa can
provide you with the whole cake very easily. You can spend your
early development time writing your Cocoa app, getting it to work
and function the way you want and then sprinkle some Carbon (ew,
yuck, who wants carbon sprinkled on their cake :-) ) on top and you
are finished.
Oversimplification, sure, but valid none the less. Cocoa has
always been a wrapper on the 90%. In the NeXT days you still had
to drop to straight BSD code for some system things and C based PS
code for others, nothing has dramatically changed since then.
Cocoa and Carbon are complementary. Cocoa can greatly decrease
your development time. Use it, learn it, love it. And then pick
up a little carbon to finish off the things you really need.
I definitely do not consider resource forks, authorization
features, a minor hack to add a check box in the title bar (which
will take you five minutes) and usage of carbon process manager
code enough to drive ME away from OS X Cocoa development. None of
those things (except maybe, and that's only maybe, resource forks)
are necessary in standard application development on OS X. You can
use them as you wish, but you are definitely not forced to.
I work on many OS X applications without any of those features, and
most of my apps have no carbon in them at all.
So the fact is that I started learning Cocoa, and realized that
most ideas for applications involved accesing to resource forks,
but this cannot be done with Cocoa. I have to use Carbon. Maybe it
is time to spend some more bucks in "Learning Carbon" :-P
I don't know what kind of applications you are trying to write, but
access to resource forks is definitely not a pre-requisite to good
OS X development.
Maybe more information here could get us to steer you towards Cocoa
more ...
Eric
Jorge Salvador Caffarena
http://homepage.mac.com/eevyl/
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev