View controller/NIB architecture for non-navigation application with transitions?

Posted by Ben on Stack Overflow See other posts from Stack Overflow or by Ben
Published on 2010-03-24T21:30:23Z Indexed on 2010/03/24 21:33 UTC
Read the original article Hit count: 259

I'm tinkering with an app that doesn't use the UINavigation root view control system, so I don't have natural ownership for each app "view". I essentially have two basic views, a document list view, and a document edit view.

I'm playing with UIView animation for getting from a selected document to the edit view.

I also have a toolbar that exists in both "views".

Because I don't have UINavigation running the show for me, I have a tendency to just throw more and more stuff into one NIB and one view controller that owns the whole container. But now I'm trying to figure out how to segue from the document list view to the edit view if the edit view lives inside a different NIB, preserving the toolbar too.

Anyone have thoughts or experience on app structures like this? I find the docs lacking on best practices around code/UI structure for anything except trivial one-screen apps or full-on navigation apps.

Thanks!

© Stack Overflow or respective owner

Related posts about iphone

Related posts about architecture