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: Glen Simmons <email@hidden>
- Date: Thu, 14 Jun 2001 11:12:54 -0500
I for one, am really tired of this particular holy war. This statement
shows your bias and ignorance. If you don't have anything useful to
contribute, please don't waste my bandwidth.
And before everyone else starts sharpening their swords and axes for
this particular jihad, try to accept that there are valid reasons for
using technologies that you don't like. That doesn't mean *you* have to
use them.
Glen
On Thursday, June 14, 2001, at 08:03 AM, David Herren wrote:
Why on earth would you want to use resource forks for anything?
Resource forks are at best a legacy item that should die die die...
On Wednesday, June 13, 2001, at 09:12 PM, cocoa-dev-
email@hidden wrote:
Message: 8
Date: Wed, 13 Jun 2001 20:43:54 +0200
From: Jorge Salvador Caffarena <email@hidden>
To: email@hidden
Subject: Cocoa, a complete Mac OS X API?
Hello to all!
First of all, I must say that I am enjoying a lot learning Cocoa by
examples, "Learning Cocoa" book, this list and the cool web sites
around. I am newbie in Cocoa, but not in programming and I have found
the O'Reilly book worth its money.... but that's another story :-)
The feeling I have about Cocoa right now is that it is a superb API,
with a excellent IDE (PB & IB) but that is lacking some key features
for
common Mac apps. I have read some examples of this in this list, as the
"AuthorizationExecuteWithPrivileges" lack of features, the Aqua
Interface Guidelines about NSBoxes and its titles and the actual
implementation inconsistence, the inexistent API for getting the list
of
running process, and one of the most annoying things about Cocoa for me
is its total lack of support for resources forks.
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.
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
/david
--
david herren | In an Internet without walls,
shoreham, vt | who needs Windows or Gates?
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev