• 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: Engeneering a Cocoa Application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Engeneering a Cocoa Application


  • Subject: Re: Engeneering a Cocoa Application
  • From: Sanjay Samani <email@hidden>
  • Date: Thu, 6 Apr 2006 19:53:37 +0100


Hi everyone. I was wondering how you develop a Cocoa Application. Cocoa in full of mechanisms not present in other languages, such as bindings, core data or interface design with Interface builder. So, from where you start when you develop a Cocoa Application? From the interface? Or from below, defining data and classes first? Or maybe a mix of all? And how do you test your new application while you are developing it? Thank you for all you answers. Bye.

---
Matteo Manferdini

Try this, which was added to the Developer Documentation in March. You can either access it and the related docs online, or download the Reference Library (full or update) from the Apple website (free Online Apple Developer Connection account required)


http://developer.apple.com/documentation/Cocoa/Conceptual/ CocoaFundamentals/index.html

Personally if you are new to it, I would proceed with learning Objective-C first (follow the links in the See Also section in the Introduction of the link above) and then go onto stuff about developing apps using Core Data and Bindings. Unless you're desperate to support pre-Tiger versions of OS X, using the pre- Binding & pre-CoreData methodology may not be worth while, other than a learning exercise.

Xcode supports Unit testing using OCUnit:

http://developer.apple.com/tools/unittest.html

Personally when developing a new application, I come at it first from the point of view of what functionality is required, I then think through the persistent data required to support that functionality and the interface to collect the data in the easiest way. There's some more stuff in the docs about programming methodologies (same doc as above):

http://developer.apple.com/documentation/Cocoa/Conceptual/ CocoaFundamentals/CocoaDesignPatterns/chapter_5_section_2.html

In that section, the most important thing is the Model-View- Controller concept which is pretty much fundamental to the way that Cocoa is set up and expects you largely to structure your apps.

Sanj




___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Prev by Date: Re: LSUIElement 1 still in Dock?!?
  • Next by Date: Re: NSCell with Embedded NSView
  • Previous by thread: Re: Engeneering a Cocoa Application
  • Next by thread: NSCell with Embedded NSView
  • Index(es):
    • Date
    • Thread