
Building iPhone Applications without Interface Builder
10 months ago
For me, the biggest stumbling block when making the transition from cocoa desktop application development to iphone development has been the use of xib files and interface builder. I get it. I just dont like it. Theres something very Dreamweaver about it.
It wasnt until I attempted to remove xib files from the development process that I realised Interface Builder wasnt really doing anything I couldnt do just as efficiently programmatically. In doing so, everything became instantly clearer. I now felt more in control of the system design, and no more create xib, create view controllers, initWithNib, repeat.
The purpose of this tutorial is to show you how to get your xcode iphone project to a hand-coder friendly starting point.
It wasnt until I attempted to remove xib files from the development process that I realised Interface Builder wasnt really doing anything I couldnt do just as efficiently programmatically. In doing so, everything became instantly clearer. I now felt more in control of the system design, and no more create xib, create view controllers, initWithNib, repeat.
The purpose of this tutorial is to show you how to get your xcode iphone project to a hand-coder friendly starting point.
-
Vimeo: About / Blog / Developers / Jobs / Community Guidelines / Community Forums / Help Center / Site Map / Merchandise
/ Get Vimeo

Previous Week
Just one insignificant nit to pick at... In theory, shouldn't the view controller be retained (perhaps by the delegate) and then released when the app exits? It's obviously not going to hurt anything, but in principle, it looks like a leak to me. Am I right?