@Todd (2nd): I do use Interface Builder to create the GUI first.
Then, in the controller header file, declare IBObject ivars for the GUI objects I need access to from code, and the IBAction methods I want to call from the GUI. Wire them up in IB, then write the actual methods in the .m file. There's a little bit of back and forth, but now that IB auto-updates from .h file changes, its easy.
When I (long ago) learned Cocoa, learning good memory management was the main early hurdle. Oh, and figuring out how to design my 2nd app after CurrencyConverter. Then I got to learn gdb so I could attach to and debug a root process (still have trouble getting Xcode running as root (using sudo open)).
P.S. @Todd(1st): might as well embrace headers, they are here to stay, and get comfy with cmd-option-up-arrow.
by Paul Collins — May 18
Then, in the controller header file, declare IBObject ivars for the GUI objects I need access to from code, and the IBAction methods I want to call from the GUI. Wire them up in IB, then write the actual methods in the .m file. There's a little bit of back and forth, but now that IB auto-updates from .h file changes, its easy.
When I (long ago) learned Cocoa, learning good memory management was the main early hurdle. Oh, and figuring out how to design my 2nd app after CurrencyConverter. Then I got to learn gdb so I could attach to and debug a root process (still have trouble getting Xcode running as root (using sudo open)).
P.S. @Todd(1st): might as well embrace headers, they are here to stay, and get comfy with cmd-option-up-arrow.