I'd like to get some opinions on handling navigation without having your view controllers modify the navigation stack directly. I'm currently working on an app where I've subclassed UINavigationController, which in turn has custom methods for showing the various views of the app. Each of my app's view controllers has no sense of the other pieces of the app, and do not push directly on the navigation controller. I'm thinking this a much better method since it decouples view controllers from each other and allows the flow of the app to be updated more easily. I'm using a lot of NSNotifications to signal commands to the navigation controller, and it's getting a bit messy. I love the idea of a centralized, decoupled navigation controller, but I haven't seen any good examples of this yet. I would love to get some feedback as to if this is a good idea in the first place, or techniques you've implemented to handle this sort of thing.
Cheers, James _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
