Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Interface builder 3.0!

0 views
Skip to first unread message

Paul

unread,
Dec 11, 2007, 4:13:15 AM12/11/07
to
Hi,

WTF! Interface Builder is completely changed, how do you drive it?

I can't even get an AppControler (NSObject) and a CustomView to work.
The generated the files were not added to the project and when I added
them manually they didn't work anyway.

The IB help is totally bloody useless. Is there a tutorial somewhere
out there in the ether on driving the thing that makes sense?

Paul

Gregory Weston

unread,
Dec 11, 2007, 6:36:28 AM12/11/07
to
In article <475e54ab$0$20842$afc3...@news.optusnet.com.au>,
Paul <pa...@optusnet.com.au> wrote:

> Hi,
>
> WTF! Interface Builder is completely changed, how do you drive it?

You read the release notes. If you have specific questions, ask them.

> I can't even get an AppControler (NSObject) and a CustomView to work.
> The generated the files were not added to the project and when I added
> them manually they didn't work anyway.

You don't create classes in IB any more. You create them in your
project. IB will automatically know about them.

G

David Phillip Oster

unread,
Dec 11, 2007, 10:20:12 AM12/11/07
to
In article <475e54ab$0$20842$afc3...@news.optusnet.com.au>,
Paul <pa...@optusnet.com.au> wrote:

> Hi,
>
> WTF! Interface Builder is completely changed, how do you drive it?
>
> I can't even get an AppControler (NSObject) and a CustomView to work.
> The generated the files were not added to the project and when I added
> them manually they didn't work anyway.

Launch I.B. by opening a Cocoa project in Xcode, and double clicking on
the appropriate nib file from within the Xcode project window.

Just like before, you drag generic NSObject and NSView objects from the
palette into your I.B. project, then set the class of those instances to
your custom class using the I.B. Get Info inspector.

Also the command line tool "nibtool" has been renamed "ibtool".

Paul

unread,
Dec 16, 2007, 4:01:03 AM12/16/07
to
Hi,

Created another project and created a controller class (NSObject) and a
myview class (NSView) then launched IB and fiddled around a lot but
eventually got it to see the class files and got it to work. I like the
old way better.

What a pain in the arse.

Paul

Gregory Weston

unread,
Dec 16, 2007, 7:33:57 AM12/16/07
to
In article <4764e94f$0$32673$afc3...@news.optusnet.com.au>,
Paul <pa...@optusnet.com.au> wrote:

> Hi,
>

> Created another project and created a controller class (NSObject) and a
> myview class (NSView) then launched IB and fiddled around a lot but
> eventually got it to see the class files and got it to work. I like the
> old way better.
>
> What a pain in the arse.

Sounds like it. But it's also atypical. You shouldn't have to fiddle
around a lot to eventually get IB to see your classes. It should Just
Work, and I suspect for most people it does.

So the question is, why not for *you*?

Eric417

unread,
Dec 16, 2007, 11:57:19 PM12/16/07
to
Gregory Weston <u...@splook.com> wrote:

Yes, so far it Just Works for me.

If there is a reproducable case that does not work, I would strongly
recommend heading over to:

http://bugreporter.apple.com

and reporting the problem and also posting to Apple's Xcode mailing list
at:

http://lists.apple.com/mailman/listinfo/xcode-users

mentioning the bug # as well.

0 new messages