Re: [LONG] Making the right choice (was Re: How viable is Cocoa development?)
Re: [LONG] Making the right choice (was Re: How viable is Cocoa development?)
- Subject: Re: [LONG] Making the right choice (was Re: How viable is Cocoa development?)
- From: David Niemeijer <email@hidden>
- Date: Sun, 27 Jan 2002 10:52:02 +0100
At 9:03 +0100 27/1/02, Marcel Weiher wrote:
On Sunday, January 27, 2002, at 03:03 , Erik M. Buck wrote:
1) If I want to take full advantage of OSX, and have fastest access to
the latest and greatest capabilities of the operating system as it
evolves, should I use Cocoa or Carbon??
Carbon.
Wrong: Carbon is easily usable from Cocoa, the other way around is
much more difficult (plus: if you do the main job in Cocoa, you
will actually have TIME to do the little bits of Carbon)
Ok, so how is Carbon easily accessible from Cocoa?
1) Can I call Carbon from an Obj-C, Obj-C++, C, or C++ file that is
part of a Cocoa application? If so, what special steps need to be
taken?
2) Can I, from a cocoa application, easily access a plug-in or shared
library containing Carbon based code? If so, what special steps need
to be taken?
3) Can I easily share Cocoa Foundation Framework objects with
"equivalent" Carbon Core Foundation objects, i.e. pass them along
between Cocoa and Carbon code? If so, what special steps need to be
taken?
4) How easy or difficult is it to put a Cocoa front-end (i.e. User
Interface) on a Carbon based core? Would everything have to be done
in PB or could the Carbon core be done in CW and "exported" to
PB/Cocoa?
5) Did I forget an important question on this issue...
Other issues for us are:
1) How integrated multiprocessing and threading are in Cocoa?
2) How integrated AppleScript is in Cocoa?
3) How large the speed penalty under Cocoa is when working with
extremely large files and large numbers of objects (instead of plain
data records/structs).
David.