Re: Bypassing Interface Builder
Re: Bypassing Interface Builder
- Subject: Re: Bypassing Interface Builder
- From: "I. Savant" <email@hidden>
- Date: Wed, 14 May 2008 12:05:23 -0400
> > 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 (email@hidden)
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:
This email sent to email@hidden