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: Jorge Salvador Caffarena <email@hidden>
- Date: Wed, 13 Jun 2001 23:19:36 +0200
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.
Hey man I am in LOVE with Cocoa! ;-) I just say it is not complete for
*today*. Maybe in the future we won't need resource forks anymore, but
for now they are all over the place. And I hoped I could work with them
using some cool NSResource class :-)'
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.
It is not a pre-requisite, if you twist your mind from a Mac freak into
NeXT or BSD freak. I do it from time to time just to enjoy the
experience of typing code full of "NS", but I think I will end up insane
mad (not 'inane', 'insane' ;) Not joking, I want to write an app that
needs access to a resource fork of a file that is in use *today* by an
Apple app launched months ago, iTunes.
Maybe more information here could get us to steer you towards Cocoa
more ...
As I said before, I am irreversible involved into Cocoa programming. But
I found this list very very interesting. When I finish my learning
period of Cocoa and start to code my apps, I will post some more
specific questions. I can bet for it :-)
Jorge Salvador Caffarena
Developing in the sands of the Sun Coast...
Jorge Salvador Caffarena
http://homepage.mac.com/eevyl/