On 26 Apr 2010, at 17:49, David Rowland wrote:
On Apr 26, 2010, at 8:15 AM, ML wrote:
How about a good book that explains what IB does, how to set
delegates, first responders, connect things up, etc
I think that misunderstanding prevents me from using IB as much as
I really should.
...
I'm going to have to agree with Rick, IB is the way to go.
I have avoided IB because I find its operation peculiar and its
terminology abstract. When I create objects in code I have a much
firmer idea of where they are, when they come into existence and
what I can do with them. IB is yet another language to master. and
you still have to write a fair amount of custom code.
One more reason to follow the advice above. And: Apple's documentation
clearly states the how, where, when, what, etc. of objects created via
Interface Builder. Read the fine manual! May be, you will recognize
that IB is not a language but a tool -- it's easier to get a grip --,
and that you do not have to write a fair amount of custom code. In
your current situation you just don't know, you only assume.
Klaus
_______________________________________________
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
