![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
Cocoa books
May. 19th, 2010 03:30 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
green_knightYou probably don't learn how to program from a book, but it can help. Below is a list of Cocoa books that I have found in my local library.
( Snip seven books )
I will review the others if and when I get to them.
Over to you: anything I've missed? Any experiences? The most frustrating part for me about learning to use Cocoa is that there seem to be plenty of tutorials that let you ride the waves of 'see how many cool things you can do with a few lines of code' which really is a very cool thing indeed, but I find that most of the time I don't seem to _understand_ the basics: when do you create a new class? Which one of the three or four methods to achieve X is the one you should choose? How does one _design_ an application when all you have is an idea? How do you know which classes, functions, and interface element will best achieve your goals?
I have the advantage of having developed applications (of sorts) for many years - not programmed from scratch, but I've done, in order, Hypercard, Filemaker, Multimedia, and web applications (including PHP), with probably one or two missing; and I've actually _read_ Apple's Interface Design Guidelines, so I have a handle on many of these questions - but I don't see books or articles addressing them.
Objective C tutorials, on the other hand, exist in large numbers. and while they're a good thing, I find them often contradictory, but that's a subject for another post.
( Snip seven books )
I will review the others if and when I get to them.
Over to you: anything I've missed? Any experiences? The most frustrating part for me about learning to use Cocoa is that there seem to be plenty of tutorials that let you ride the waves of 'see how many cool things you can do with a few lines of code' which really is a very cool thing indeed, but I find that most of the time I don't seem to _understand_ the basics: when do you create a new class? Which one of the three or four methods to achieve X is the one you should choose? How does one _design_ an application when all you have is an idea? How do you know which classes, functions, and interface element will best achieve your goals?
I have the advantage of having developed applications (of sorts) for many years - not programmed from scratch, but I've done, in order, Hypercard, Filemaker, Multimedia, and web applications (including PHP), with probably one or two missing; and I've actually _read_ Apple's Interface Design Guidelines, so I have a handle on many of these questions - but I don't see books or articles addressing them.
Objective C tutorials, on the other hand, exist in large numbers. and while they're a good thing, I find them often contradictory, but that's a subject for another post.
