Re: After Hillegass
Re: After Hillegass
- Subject: Re: After Hillegass
- From: Quincey Morris <email@hidden>
- Date: Sat, 17 Jan 2009 23:14:16 -0800
On Jan 17, 2009, at 22:18, Brian Bruinewoud wrote:
Secondly: I've read the 3rd edition of Hillegass and it has gotten
me a fair way. What book should I move to next?
I searched the archives and the latest dated e-mails I could find
were from 2006 and mentioned a "Cheeseman" book, is this the "Cocoa
Recipes for Mac OS X"? That book is from 2002 is there a more up to
date or better choice?
I'd suggest you start writing applications now and not look for more
books until you know what you're looking for (i.e. until you're
stuck). If you're desperate to read, read more of Apple's documentation.
To help with your suggestions:
I think I got the hang of Objective-C as a language and probably
don't need a book for that (though feel free to suggest).
When I open an example project, I'm not quite sure how to start
reading it to understand it.
The examples are more use when you have a question you need to find
the answer for. How about you pick one whose functionality interests
you and which sort of sounds not incredibly daunting, and first try to
write it yourself without looking at the code in the example project?
Or something else whose functionality has some attraction for you
personally.
(I'm begging you not to start a project that manages bank account
transactions or controls iTunes. We've had so many of those on this
list in the last few months that it would nice to see questions about
something else. :) )
When I read the documentation for a class, I'm not quite sure how to
read them (they tell me what all the functions are but don't give
much indication of how to use them or why, what are the dependencies
of one on the other, etc).
In the box at the top of the document, there's often a "companion
guide" list. Read those first.
A few of the companion guides are pretty much essential reading.
Memory management, design patterns, collections, events, windows,
views, drawing and documents are ones you should read multiple times.
Objective-C language, Objective-C runtime, garbage collection, KVO and
KVC are also important, though more technical.
(I'm also begging you to stay away from Core Data until you have a lot
of the other basics well in hand, in particular KVO and bindings. By
all means do the Core Data tutorial in the documentation to see what
it's like, but Core Data is definitely the deep end of the pool.)
FWIW
_______________________________________________
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