Support for coexistence of Classic Xamarin MvvmCross and Xamarin.Forms

[thefex]

I am working at implementing support for coexistence of Classic Xamarin MvvmCross with Xamarin.Forms.

That would give ability for Xamarin.Forms to live along with classic Xamarin (MvvmCross).
Finally it should allow to:

1. Create Pages with Xamarin.Forms - attached viewmodel should have attribute:
   [MvxAssociatedViewType(MvxViewType.Forms)]
2. Create classic native views (Mvx...Activity/Page/UIViewController) - attached viewmodel should have attribute:
   [MvxAssociatedViewType(MvxViewType.Classic)]
   All will be handled by special MvxPresenter.

That would give us a chance to write mixed application Forms/Classic API. For things that are easy to implement with Forms (ex. list view with button) - we would go with Forms. For things that are tough/platform-specified/unimplementable in Forms we could use the old, good classic Xamarin.

Besides that in my honest opinion - support of Classic MvvmCross with Forms coexistence brings Forms to right track as a tool which "complements standard API's" instead of "do everything in that"

[thefex]

I am working on that on that branch: https://github.com/thefex/MvvmCross-Forms/tree/feature_classic-xamarin-with-forms-coexistence

Looks promising but I've just started.

[tofutim]

How is this looking? Here you are looking for a way to use non-Forms on a Forms project. Besides this, I wonder if there is a way that WPF and Mac (non-Forms) can still be supported.