"Programming In Objective-C 2.0" was just published this year (2009)... i just got my copy from Amazon... lots of stuff in this book... certainly can't hurt: http://www.amazon.ca/gp/reader/0321566157/ref=sib_dp_pt#reader-link
On Sun, Jan 18, 2009 at 2:14 AM, Quincey Morris <quinceymor...@earthlink.net> wrote: > 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 (Cocoa-dev@lists.apple.com) > > 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: > http://lists.apple.com/mailman/options/cocoa-dev/chunk1978%40gmail.com > > This email sent to chunk1...@gmail.com > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
