[MonoTouch] What are the advantages of UIViewController containment of iOS5 SDK?
Krumelur
rene.ruppert at gmail.com
Wed Oct 26 04:07:22 EDT 2011
Hi,
while I ported MGSplitViewController to Monotouch I wondered why this thing
actually works. It does exactly what Apple disencourages:
* Add a couple of UIViewControllers' views to another UIViewController's
parent view
* Have different UIViewControllers manage different sections of the screen
* Deal with the issues that events (like rotation) are not forwarded to the
child controllers
The first two points are just ignored and the last point is solved by simply
calling the master and details controllers' event handlers. Problem solved?
But why would Apple then open up the API for view controller containmant
(Episode 102 of WWDC 2011)? If I rewrite MTSplitViewController to work on
iOS5 only by using this new technique, what would be the advantages?
Or asked differently: what issues can one expect with the current
implementation? As far as I can see, everybody is happy with Matt's
MGSplitViewController.
René
--
View this message in context: http://monotouch.2284126.n4.nabble.com/What-are-the-advantages-of-UIViewController-containment-of-iOS5-SDK-tp3939738p3939738.html
Sent from the MonoTouch mailing list archive at Nabble.com.
More information about the MonoTouch
mailing list