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:02:56 +0200
The resource fork (IMO) is very convenient, but you can avoid using it.
Are you looking at legacy code that heavily depends on resources?
Well, I plan to do a complete rewrite of one REALbasic application I
developed (eeCD 1.2 for Mac OS and Mac OS X) into Cocoa. But this app is
for managing the "CD Remote Programs" file that stores the info about
Audio CDs (artist, title and song names), this file is still in use
under Mac OS X and a very Apple app make use of it, iTunes. The info of
this file is in the resource fork, and it appears it will continue to be
in that place, so I *need* resource support from Cocoa. I just realize
that Apple forces me to make a Carbon wrapper for resource access.
Something that I suppose difficult for a Cocoa newbie. I did some "old
school" Mac OS programming in C some years ago, before Carbon, so maybe
I just can get it done sonner or later.
What I want to say (maybe I am having difficulties in expresing my ideas
in English, sorry about that) is that I do not see Cocoa as the future
"unique" Mac OS X API, as Apple want us to think. There is so much of
that called "legacy code" that will be very difficult to eliminate from
Mac OS X.
Jorge Salvador Caffarena
http://homepage.mac.com/eevyl/