[Swede]

Could someone post a Cocoa "Hello World", that brings up a window, the menubar, some buttons and maybe some static text, without using Interface Builder.
It would be even cooler if it includes the way you initalize and display an NSOpenGLView too, without IB, of course.

It would be very useful. :-)

/Joel Edström

[IamBob]

Just curious...why?

Why would you want to drop IB and do it all by hand?

[parallax]

Just go to Google.com and type in all the classes you want to use.

It'll show you results from Apple first. From these, it's easy to find out how do initialize and display windows, views, &c. &c.

Really, it is a waste of time though. Use IB. IB rocks.

[This message has been edited by parallax (edited 02-19-2001).]

[IamBob]

The only reason I could come up with for wanting to do an IB-less Cocoa app is to make it GUI-hacker unfriendly.

Even then there's ways to still use IB and make it nearly impossible to hack the GUI without breaking the application. Like, drop everything onto your windows, create the outlets and resize and place in code, for instance. I think OmniWeb does(did?) this to a certain extent with a few of their UI elements. It's not that uncommon, anyway.

Well, still curious.

[LordJavac]

I think that the most likely reason to want to know how to create GUI elements without IB, othre than intellectual curiosity, is for the creating of dynamic interfaces where the elements aren't known until runtime.

[IamBob]

Okay, there's another reason. I guess I hadn't thought of that (yet).

Even still you could do some of that with IB. Instead of starting all from scratch you could subclass NSObject (or whatever is appropriate), get your menu bar and an initial window(or not) in IB and then create the rest manually. That would give you starting point with little coding effort.

You can still create things by hand after that but I guess we're not going for The Easy Way Out(tm).

[Dalgo]

One reason to create windows programmatically is if it isn't used much and you don't want it to be loaded every time you launch the program. Why waste the memory? I create lots of sheets programmatically, but I do it the easy way with the functions in AppKit. I haven't had a good reason to create a window programmatically. Usually I have lots of stuff in it so I just save the window in it's own nib and load that everytime. that way it's easy to have lots of instances of it.