I have a WPF MVVM application that I'd like to refactor to use MvvmCross to support a WPF and Mono for Android implementations.
Our application's views consists of:
- A toolbar that is always visible
- A navigation bar region
- A main view region
- A popup window region
Each of these regions is a UserControl on the main application window and a UiService simply swaps out the views in each region. In the case of the pop-up window, it too is just a UserControl on the main window that's visibility changes on Show or Hide calls to the UiService. The UiService also accepts a context parameter which allows state information to be passed into the view model to be shown.
The main views are typically a composite of several child views. In these cases, the main view model creates the child view models which are exposed as properties. The main view sets these properties as the data context of the child views.
I would think that MvvmCross would certainly support this style composite views, but I couldn't find an example of such. Are there any relevant MvvmCross examples? What would be the recommended approach for implementing in MvvmCross?