Re: Figuring out Interface Builder 3.0
Re: Figuring out Interface Builder 3.0
- Subject: Re: Figuring out Interface Builder 3.0
- From: Jon Hess <email@hidden>
- Date: Mon, 29 Oct 2007 17:23:31 -0700
Hey Monte -
On Oct 29, 2007, at 12:17 PM, Monte Ohrt wrote:
Hello all,
I'm brand new to Cocoa development. I recently started learning with
the Hillegas book and xcode 2. I was able to do the first tutorial
(Random Number) fine in xcode 2, but I'm not exactly sure how to
handle this in xcode 3 with the new interface builder. In the IB 2,
the controller class created was automatically added to the xcode
classes group. In IB 3, I don't see how to tie them together. This
is what I've been able to make work:
In IB 3, create the controller instance, add the action and outlet
items, and connect them. Then I go to File->Write Class Files... and
browse to the project directory and save as "MyController". Then I
go back to xcode and manually Add->Existing Files... to add
MyController files to the classes group.
Another method I tried was to create the class files in xcode 3
first, then in IB 3, select the class file when I instantiate the
object. But, I still have to write out the class files by browsing
to the project folder, select the MyController.m file and prompt to
replace the files.
Both methods require me to manually create the class relationship
between xcode and IB. Is there a better approach?
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
TIA
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:
@mac.com
This email sent to email@hidden
_______________________________________________
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