On May 14, 2008, at 11:11 AM, I. Savant wrote:
I rather just make it in Xcode or Textmate and know what's going on
behind the scenes.
Using IB and knowing what goes on behind the scenes are not mutually
exclusive. I use IB and (because I thoroughly read the documentation)
know what's going on behind the scenes.
This is a really good point. I'd go so far as to say you *shouldn't*
use IB *without* some understanding of the nitty-gritty.
The issue could also be addressed from the other direction. How far
behind the scenes do you want to go? Should one program only with
structs and C functions because polymorphism and dynamic binding do
things for you "behind the scenes"?
I do understand it can seem like some things happen by magic that
require an uncomfortable leap of faith. The answer is to figure out
what's going on (if possible), not to avoid those things altogether.
If it helps, you can use ibtool to convert a nib file to XML and see
the gory details, and then make an informed decision about whether you
want to reproduce those gory details in code.
--Andy
_______________________________________________
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 [EMAIL PROTECTED]
