• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa and Carbon
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa and Carbon


  • Subject: Re: Cocoa and Carbon
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 14 May 2008 07:52:20 -0700


On 14 May '08, at 7:21 AM, Gerriet M. Denkmann wrote:

So: what is the real difference between a "Carbon application" and a Cocoa one? Why would one create a Carbon application?

Carbon applications generally don't use Cocoa or Objective-C at all. They use the High-Level Toolbox for GUI code. It's a lot more cumbersome.


In almost all cases, Carbon apps are the descendants of Mac applications that predate OS X. Carbon was created as a porting layer for this purpose, since in the early days it was crucial to get existing apps like Office, PhotoShop and InDesign running native. So there's almost no reason to create a Carbon app; it's a legacy API at this point, although for political reasons the APIs aren't marked as such.

—Jens

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Cocoa and Carbon (From: "Gerriet M. Denkmann" <email@hidden>)

  • Prev by Date: Re: Launching Cocoa Application externally
  • Next by Date: Efficient XML loading [continuation of NSString from mapped NSData thread]
  • Previous by thread: Cocoa and Carbon
  • Next by thread: Re: Cocoa and Carbon
  • Index(es):
    • Date
    • Thread