colo wrote:
Hmmm. The letting it create the files in the nib file sounds fine for me. But what about the linking and configuring? It's just all reflected in code correct? The dragging a pipe to one object to the other that just all shows up in the .m right?
No and no. Distinctly unlike C# applications you build in Visual Studio, creating the UI in Interface Builder does not just write code for you. It creates what amount to full-constructed objects and then freeze-dries them in a container from which they can be easily retrieved. You *can* supplant that pre-rolled functionality in code, and there are sometimes even reasons to do so. But that's not the general circumstance by a long shot.
Greg _______________________________________________ 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]
