• 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: The how and why of Cocoa.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The how and why of Cocoa.


  • Subject: Re: The how and why of Cocoa.
  • From: Scott Andrew <email@hidden>
  • Date: Sun, 1 Apr 2007 07:43:00 -0700

I had a lot of the same questions a year ago. However as you use the framework you find that it is real easy to throw together test applications and basic things. I struggled with the language (coming from 10 years of C++ & C# on Windows). I read a lot and dove into a project and things just clicked. ADC is nice, even a free membership is good to keep XCode up to date and documentation.

When stuck I use this mailing list plus the following websites:

http://cocoadevcentral.com/
http://www.cocoabuilder.com (archive of this mailing list)
http://cocoablogs.com
http://www.apple.com/developer (great apple samples)

I also work better working on a project that I want and learn as I go. The initial tries are not optimal, but they get your hands wet and start using the language, framework and tools.

As far as Carbon VS Cocoa. Carbon is a bit more difficult to get things up and running. Cocoa takes learning a new language (objective- c), however it is elegant and nice. Sure it hides a lot of things from you, but you can always go to carbon to do certain things if you need the granularity. Since Objective-C is based on C you can mix C++ and C (we do that at work a a lot to work with a crossplatform engine). The hardest things for me to get used to in Objective-C is the [msg] syntax, bindings, and addref/release/autorelease.

Scott Andrew

On Mar 31, 2007, at 7:36 PM, William Squires wrote:

While the Cocoa reference material gives the 'what', it would be nice if there were a tutorial (or online course) in programming with Cocoa/ObjC that gives the 'why' and 'how' in terms of other common computer languages/frameworks currently available out there (C/C++/REALbasic for Mac, C++/C#/VB 6 or .Net for Windows).
For example, why should one want to use; bindings, outlets, NSArrayControllers, First Responders, etc... and - given that the item in question is the one we want/need to use - how do we do it properly (code samples if applicable, or a link to an XCode project for IB-related questions)?
While books like Hillegras' are nice, I really need more theory AND hands-on exploration, so I can relate my existing programming experience (C/C++/REALbasic/VB) with the Cocoa-way of doing things.
Perhaps Apple Inc., needs to make their ADC Premier memberships cheaper so hobbyists can afford it (and WWDC! :) ) Think of it as a loss-leader for their computers. After all, today's hobbyists could well become tomorrow's entrepreneurs, bringing us new games, utilities, and other goodies to run on our Macs! And that means more people needing/wanting a shiny, new Core 2 Duo iMac!! (or MacMini, or whatever...)
Does anyone know of such resources (besides a paid ADC membership)?


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
40adelphia.net


This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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


  • Prev by Date: Re: NSTokenField come over a NSTableView
  • Next by Date: Possibly dumb NSTableView problem
  • Previous by thread: Re: The how and why of Cocoa.
  • Next by thread: Re: Core Data - SQLite persistent store file size optimization
  • Index(es):
    • Date
    • Thread