• 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: Super Newbie
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Super Newbie


  • Subject: Re: Super Newbie
  • From: Dave Rosborough <email@hidden>
  • Date: Tue, 4 Nov 2003 18:26:47 -0800

A few comments:

1. If you're interested in books on Cocoa, search the list archives (http://cocoa.mamasam.com/) for "Cocoa AND book" or something like that. There have been some good threads in the past year on good books for Cocoa. The only problem is that, to my knowledge at least, there are no books released that include the latest version of the Cocoa framework in Panther (OS X 10.3). Personally, I have used the books from O'Reilly (www.oreilly.com) called "Learning Cocoa" and "Building Cocoa Applications", and found them acceptable if a little weak in some areas.

2. Cocoa and Carbon are frameworks, while Objective C and Java are languages. Carbon applications are generally written in C++, while Cocoa applications can be written in either Objective C or Java. Most developers here use Objective C, for various reasons. For a more detailed diatribe, search the list archives at mamasam for "Objective C and Java" or something.

3. While it is true that Carbon was designed as a nice migration path for OS 9 developers' existing applications, there are a number of features of Mac OS X that can only be got at through Carbon. My experience has generally been that when I say "hmm... can't find any classes in Cocoa that do ...", it's time to dig through the Carbon API because it's probably in there somewhere. Fortunately, a Cocoa application can make Carbon calls, since they're just C functions and Objective C is a superset of C. So while a Cocoa programmer may spend most of his time in the Cocoa framework, every now and then you'll probably need to make a Carbon call in one of your Cocoa classes.

4. Applescript is definitely slower. I've also found it extremely frustrating when trying to do anything complex. However, some people really like it and for some straightforward apps, it is a good choice (for example, writing GUI's for shell commands seems to frequently be done using Applescript Studio).

5. Check out Alastair Houghton's FAQ (http://www.alastairs-place.net/blog/blog/CocoaDev-faq.txt). It's excellent, and it has answers to lots of typical "newbie" questions.

TTYL
DaveR
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Super Newbie
      • From: "Alastair J.Houghton" <email@hidden>
References: 
 >Super Newbie (From: Timothy Johnson <email@hidden>)

  • Prev by Date: String conversion problem from web
  • Next by Date: Notification error
  • Previous by thread: Re: Super Newbie
  • Next by thread: Re: Super Newbie
  • Index(es):
    • Date
    • Thread