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: Thu, 14 Jun 2001 00:37:01 +0200
For instance, you mention you need do resource fork manipulation, and
there are no Cocoa APIs for this. You can easily use the Resource
Manager APIs, which are actually in a low-level service in
CoreServices.framework, already automatically available to all apps.
Sometimes making the C calls might be inconvenient --- especially if
there is a mismatch between types (for instance, converting FSRefs to
paths or URLs); but it's just a bunch of C calls in the end. If you
have to manipulate resource forks, you can. (Just note that for new
document formats, we do not recommend using resource forks, as they
tend to be fragile in many circumstances.)
I agree with almost all you say Ali, but I think Apple should "eat their
own dog food" about resource forks. iTunes use a resource fork only file
to store Audio CDs artist, title and song names and info. I want to
develop a Cocoa app that needs to use that file, so I need to use Carbon
calls. Maybe Apple should transform the "CD Remote Programs" file from
resource fork type into XML.
But I got it, resource forks are a dead legacy feature soon to be
removed (or not?) from Mac OS X. It makes me sad to say farewell to
resource forks :''-(
Jorge Salvador Caffarena
http://homepage.mac.com/eevyl/