Quote:
Originally Posted by PhoneyDeveloper
There is a way for one nib to reference another nib so that the second nib is automatically loaded when the first is loaded. The navbar template is set up this way. There's a MainWindow.nib and a RootViewController.nib and the main nib references the rootview nib and both are loaded when the app starts.
Regarding the app controller, it is possible to make the navbar hidden and still use the nav controller to manage the appearance of views and their view controllers. Alternatively you could use a tabbarcontroller. If you don't use either of these you will be duplicating their functionality in some way. I won't say you can't do an app without one or other of these classes. I will say that for your first app you will have problems figuring out how to duplicate their functionality, rather than working on the interesting parts of your app.
|
Daisy chaining sounds like an interesting option, but i'd be concerned about the memory implications.
I hear what you're saying about the tab and nav controllers, but won't i spent a lot more effort just getting rid of all of the nav/tab elements? The requirements for my app include full screen views w/o the navigation elements - is this easy to rig up with the existing controllers?
I'm starting to get the feeling that whatever this whole auto-loading thing is, it doesn't sound like something that anyone who replied here counts on, and that manual NIB loading is the rule, not the exception.
