Re: Figuring out Interface Builder 3.0
Re: Figuring out Interface Builder 3.0
- Subject: Re: Figuring out Interface Builder 3.0
- From: Monte Ohrt <email@hidden>
- Date: Mon, 29 Oct 2007 20:02:08 -0500
Jon Hess wrote:
Hey Monte -
If you declare outlets and actions in Interface Builder, you have to
manually add them to source files in your Xcode project. This is
obviously something that could be improved. I think you'll have a much
better experience if you declare all of your outlets, actions, and
classes in source files with Xcode. Since Interface Builder 3.0
automatically reads your header files, you won't have to do any
synchronization. Sticking to the 'design in Xcode' workflow will
provide a much more seamless experience.
Jon Hess
Hi Jon,
So what you are saying, it is better to type out the action/outlet code
in xcode, vs. creating them via the +/- buttons the IB. Did I get that
right?
Let's see if I can make this clear for myself :)
In xcode, create the controller class and add all the IBOutlet/Action
stuff manually into the .h/.m files. Then in IB, instantiate an object,
select the class you made in xcode, and IB automatically discovers the
outlets and actions from the class. Then you can visually connect the
outlets/actions to the interface buttons and whatnot. Is that correct?
Am I also correct in the assumption that now there is no reason to
"Write Class Files..." from IB anymore, you just "Save" ?
Monte
_______________________________________________
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