One of the things that I really liked about MvvmCross for iOS and Android was the typed access to view models and creating bindings between the view and view model through a binding set.
This pull request attempts to bring these features to MvvmCross for forms. There are two main classes, MvxContentPage and MvxPageRenderer which both have parametrised versions that offer typed access to the view model. MvxContentPage is intended to help building Xamarin.Forms cross-platform pages with the power of MvvmCross. MvxPageRenderer is intended to be a base class for custom renderers. A MvvmCross binding set can be employed to create the bindings between iOS or Android custom renderers and a MvvmCross view model.
There might very well be that these classes can be improved or re-factored in a way that is more consistent with the MvvmCross code base. Discussion and suggestions are most welcome.
One of the things that I really liked about MvvmCross for iOS and Android was the typed access to view models and creating bindings between the view and view model through a binding set.
This pull request attempts to bring these features to MvvmCross for forms. There are two main classes, MvxContentPage and MvxPageRenderer which both have parametrised versions that offer typed access to the view model. MvxContentPage is intended to help building Xamarin.Forms cross-platform pages with the power of MvvmCross. MvxPageRenderer is intended to be a base class for custom renderers. A MvvmCross binding set can be employed to create the bindings between iOS or Android custom renderers and a MvvmCross view model.
There might very well be that these classes can be improved or re-factored in a way that is more consistent with the MvvmCross code base. Discussion and suggestions are most welcome.
Regards, Martin