> > 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.
Ah! If that's what you (colo) are saying, then David is exactly right. You create a class, create your source files, then tell IB that an instantiated 'object' is an instance of that class. It (IB) doesn't create *any* code. -- I.S. _______________________________________________ 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]
