On Wed, May 14, 2008 at 11:35 AM, colo <[EMAIL PROTECTED]> 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? So that part can just be > bypassed and done in xcode I assume and still remain "Cocoa" style.
This is incorrect. I think you're being confused by memories of some Windows programming or the like, where interface creation actually created code for you that you then fleshed out. IB does not touch your code. All it creates is a .nib file that tells the runtime to create some stuff when it's loaded, and then to connect that stuff to objects that your code created. -- - David T. Wilson [EMAIL PROTECTED] _______________________________________________ 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]
