Mvvm cross – going portable

MvvmCross – Going Portable

Going Portable
@slodge

MvvmCross MvvmCross MvvmCross MvvmCross
.WP7 .Touch .Droid .WinRT

MyApplication MyApplication MyApplication MyApplication

MyUI MyUI MyUI MyUI
MvvmBinding MvvmBinding
.Touch .Droid


Core MvvmCross MyApplication
MyApplication Library contains: MyApplication MyApplication

• Mvvm interfaces and base classes
• Simple DI container and IoC controller
MyUI MyUI MyUI MyUI
• Platform specific navigation• and presentation logic
.WP7 .Touch M .Droid .WinRT
• Platform specific implementations of MvvmBinding
MvvmBinding
.Touch .Droid
file, location, camera, etc

MvvmCross MvvmCross • M MvvmCross MvvmCross


MyApplication Library contains:
MyUI MyUI MyUI MyUI
• Application startup logic
MvvmBinding
.Touch
MvvmBinding
.Droid
• Models and Services • M

• ViewModels
• ValueConverters

Identical code across platforms – just cut-and-paste projects

MyUI Executable contains:
• M
• Platform Specific Views and Controls
• Some adaption for ValueConverters

MyUI MyUI MyUI MyUI
MvvmBinding MvvmBinding
.Touch .Droid

Problems
• MvvmCross is a “fat” library – contains more than just
mvvm!
• Compiled image sizes can be large – especially on
MonoTouch
• Application libraries are cut and paste – a boring, error
prone manual job
• Automated cross-platform refactoring is impossible
• No common way to extend the platform
• Each new platform added requires manual cut-and-
paste duplication of projects

MvvmCross
.Portable

MyApplication
.Portable
Plugin1 Plugin2
…
.Portable .Portable

MyUI MyUI MyUI MyUI
.Adapter.Wp7 .Adapter.Touch .Adapter.Droid .Adapter.WinRT

Plugin1 Plugin1 Plugin1 Plugin1
.Wp7 .Touch .Droid .WinRT


… … … …

MvvmCross
.Portable

MyApplication
MvvmCross is a single Portable library containing:
.Portable
Plugin1 Plugin2
…
.Portable .Portable
• Mvvm base classes
• Simple DI container and IoC controller
• Plugin Loader base interfaces
MyUI MyUI MyUI MyUI
MvvmCross MvvmCross
• M MvvmCross MvvmCross



… … … …

MvvmCross
.Portable

MyApplication
.Portable
Plugin1 Plugin2
…
.Portable .Portable

MyUI MyUI MyUI MyUI
MyApplication is a single Portable library containing: .WinRT
.WP7 .Touch .Droid

• Application startup logic

• Models and Services Plugin1 •
Plugin1
.Wp7 .Touch
M Plugin1
.Droid
Plugin1
.WinRT
• ViewModels
•
ValueConverters

… … … …

MvvmCross
.Portable

MyApplication
.Portable
Plugin1 Plugin2
…
.Portable .Portable

MyUI MyUI MyUI MyUI
The Portable part of each Plugin:

• Provides the interface for that plugin

• e.g. for Location it provides Start, Stop, and an
Plugin1
.Wp7
Plugin1 • M
.Touch
Plugin1
.Droid
Plugin1
.WinRT
OnLocationChanged event.
• Provides an EnsureLoaded() call for initialisation at runtime

… … … …

MvvmCross
.Portable

MyUI executable provides:
MyApplication
.Portable
• Platform Specific Views and Controls
• Some adaption for ValueConverters Plugin1
.Portable
Plugin2
.Portable
…

• M

MyUI MyUI MyUI MyUI



… … … …

MvvmCross
.Portable

The MvvmCross.Adapter for each platform provides:
MyApplication
.Portable
• Platform Specific Mvvm Helpers – e.g. binding Plugin2
Plugin1
• Platform Specific View and navigation
…
.Portable .Portable

• M
• Platform Specific Plugin Manager/Loader
MyUI MyUI MyUI MyUI



… … … …

Plugin Implementations: MvvmCross
.Portable

• Provide platform specific implementations of each Plugin
Interface MyApplication
• e.g. for Location a platform specific service will provide
.Portable
Start, Stop, and OnLocationChanged. Plugin1
.Portable
Plugin2
.Portable
…

• Are initialised at runtime using a mixture of:
• M
• Project references
MyUI
• Convention-based dynamic assembly loading MyUI
MyUI MyUI
• Setup Helpers on platforms that don’t support
Assembly.Load()



… … … …

Plugins – Portable Interfaces
In the Portable Library – Plugins.Email.dll:

public interface IMvxComposeEmailTask
{
void ComposeEmail(string to, string cc, string subject, string body, bool isHtml);
}

public class PluginLoader
: IMvxPluginLoader
, IMvxServiceConsumer<IMvxPluginManager>
{
public static readonly PluginLoader Instance = new PluginLoader();

#region Implementation of IMvxPluginLoader

public void EnsureLoaded()
{
var manager = this.GetService<IMvxPluginManager>();
manager.EnsureLoaded<PluginLoader>();

}

#endregion
}

Plugins – Portable Use

The plugin can be used in a Portable ViewModel as simply as:

protected void ComposeEmail(string to, string subject, string body)
{
Cirrious.MvvmCross.Plugins.Email.PluginLoader.Instance.EnsureLoaded();
var task = this.GetService<IMvxComposeEmailTask>();
task.ComposeEmail(to, null, subject, body, false);
}

Plugins – Platform Specific
Implementations
In one platform specific implementation – Plugins.Email.WindowsPhone.dll:
public class MvxComposeEmailTask : MvxWindowsPhoneTask, IMvxComposeEmailTask
{
public void ComposeEmail(string to, string cc, string subject, string body, bool isHtml)
{
var task = new EmailComposeTask() { To = to, Subject = subject, Cc = cc, Body = body };
DoWithInvalidOperationProtection(task.Show);
}
}

public class Plugin
: IMvxPlugin
, IMvxServiceProducer<IMvxComposeEmailTask>
{
#region Implementation of IMvxPlugin

public void Load()
{
this.RegisterServiceType<IMvxComposeEmailTask, MvxComposeEmailTask>();
}

#endregion
}

Advantages
• Core MvvmCross is now a much smaller library
• Compiled image sizes can be much smaller – especially
on MonoTouch
• Each Application is now a single library
• Cross-platform refactoring now a reality
• Manual cut-and-paste between projects eliminated
• Plugin technique allows easy extensibility for everyone
• New portable architecture makes it easier to add ans
support new platforms –
Silverlight, WPF, MonoMac, PlayStationSuite, …

Progress…

Working now: In progress:
• WP7 • MonoTouch
• Mono for Android
• WinRT

Mvvm cross – going portable

Recommandé

Recommandé

Contenu connexe

En vedette

En vedette (10)

Similaire à Mvvm cross – going portable

Similaire à Mvvm cross – going portable (20)

Plus de Stuart Lodge

Plus de Stuart Lodge (17)

Dernier

Dernier (20)

Mvvm cross – going portable