Re: Carbon vs. Cocoa
Re: Carbon vs. Cocoa
- Subject: Re: Carbon vs. Cocoa
- From: Nick Zitzmann <email@hidden>
- Date: Sun, 8 Feb 2009 12:02:25 -0700
On Feb 8, 2009, at 2:14 AM, Dieter Oberkofler wrote:
What are the known plans for Carbon?
You already know what everyone else does. Carbon is not dead, and is
not going to die. However, all of the drawing stuff in Carbon, such as
QuickDraw and the entire HIToolbox, was not ported to PPC64 or X86-64.
Neither was the C API in the QuickTime framework. I can only guess
that such ports would have been too much of a hassle. And QuickDraw
has been obsolete for eight years now in any case.
So you can continue to go Carbon-only for the near future, but you
won't be able to port your application to PPC64 or X86-64. I'd suggest
you start moving now, though, because 64-bit applications are the
future, and although I don't know what applications we'll be using ten
years from now, I know they won't be 32-bit.
Is it true that Apple is going to drop Carbon support after 10.6?
Only Apple knows the answer to that question, and they won't tell. But
between us, that would be suicide if they did that, since even the
AppKit framework relies on Carbon to work.
What would the proper migration path from Carbon to Cocoa be, if
there is any?
Start moving all of your QuickDraw stuff (if any) to CoreGraphics, all
of your HIViews to NSViews, all of your WindowRefs to NSWindows, and
all of your QuickTime code (if any) to QTKit. You can keep using non-
GUI Carbon code, such as the file manager, if you wish, because all of
it (except for _really_ old stuff such as FSSpec) is not going away.
Nick Zitzmann
<http://seiryu.home.comcast.net/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden