学步园

public interface IMXView
{
  Type ModelType { get; }
  void SetModel(object model);
  void Render();
}

The  IMXView interface defi nes the implementation contract for all MonoCross views. The interface consists of the properties, methods, and events necessary  for the MonoCross navigation framework to initialize the rendering of a view from
a controller in the shared application. This approach offers great fl exibility in defi  ning views across multiple mobile platforms. You can implement your views using whatever approach is required by the target platform, provided you implement the IMXView
interface.

using System;
namespace MonoCross.Navigation
{
  public delegate void ModelEventHandler(object model);
  public interface IMXView
  {
    Type ModelType { get; }
    void SetModel(object model);
    void Render();
  }
  public abstract class MXView<T> : IMXView
  {    
    public Type ModelType { get { return typeof(T); } }
    public virtual void SetModel(object model)
    {
      Model = (T)model;
    }
    public virtual void Render() { }
    public virtual T Model { get; set; }
  }
}

Use the MXView<T> class to create a view for your Customer model class. For simplicity in illustrating the concept, the view in Listing 4-6 has been created for the Windows Console target.
下面是控制台实现Customer view的代码

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using MonoCross.Navigation;
using MonoCross.Console;
using CustomerManagement.Shared.Model;
namespace CustomerManagement.Console.Views
{
  class CustomerView : MXConsoleView<Customer>
  {
    public override void Render()
    {
      System.Console.Clear();
      System.Console.WriteLine(“Customer Details”);
      System.Console.WriteLine();
      System.Console.WriteLine(Model.Name);
      System.Console
        .WriteLine(string
          .Format(“{0} {1}”, 
            Model.PrimaryAddress.Street1, 
            Model.PrimaryAddress.Street2));
      System.Console
        .WriteLine(string
          .Format(“{0}, {1}  {2}”, 
            Model.PrimaryAddress.City, 
            Model.PrimaryAddress.State, 
            Model.PrimaryAddress.Zip)); 
      System.Console
        .WriteLine(“Previous Orders: “ + Model.Orders.Count.ToString());
      System.Console
        .WriteLine(“Addresses:” + Model.Addresses.Count.ToString()); 
      System.Console
        .WriteLine(“Contacts: “ + Model.Contacts.Count.ToString());
      System.Console.WriteLine();
      System.Console.WriteLine(“Web: “ + Model.Website);
      System.Console.WriteLine(“Phone: “ + Model.PrimaryPhone);
      System.Console.WriteLine();
      System.Console.WriteLine(“Enter to Continue, (D)elete or (E)dit”);
      while (true)
      {
        string input = System.Console.ReadLine().Trim();
        if (input.Length == 0)
        {
          this.Back();
          return;
        }
        else if (input.StartsWith(“E”))
        {
          this.Navigate(“Customers/” + Model.ID + “/EDIT”);
        }
        else if (input.StartsWith(“D”))
        {
          this.Navigate(“Customers/” + Model.ID + “/DELETE”);
        }
      }
    }
  }
}

The  Render()  method of the  CustomerView class is where you define the logic to display your model customer instance to the user. In this case the model property values are simply displayed in the appropriate format using the  Console.WriteLine()
method. 
看完上面几个基类后，下面需要看看将他们联系起来的几个类以及方法

using System;
using System.Collections.Generic;
using System.Linq;
namespace MonoCross.Navigation
{
  public abstract class MXApplication
  {
    public string NavigateOnLoad { get; set; }
    public string Title { get; set; }
    public NavigationList NavigationMap = new NavigationList();
    protected MXApplication()
    {
      NavigateOnLoad = string.Empty;
      OnAppLoad();
    }
    public virtual void OnAppLoad() { }
    public virtual void OnAppLoadComplete() { }
    public class NavigationList : List<MXNavigation>
    {
      public void Add(string pattern, IMXController controller)
      {
        this.Add(pattern, controller, new Dictionary<string, string>());
      }
      public IMXController GetControllerForPattern(string pattern)
      {
        return this.Contains(pattern) 
          ? this.Where(m => m.Pattern == pattern)
            .First().Controller 
          : null;
      }
     public String GetPatternForModelType(Type modelType)
      {
        return this.Where(m => m.Controller.ModelType == modelType)
          .First().Pattern;
      }
      public bool Contains(string pattern)
      {
        return this.Where(m => m.Pattern == pattern).Count() > 0;
      }
      public void Add(string pattern, 
                      IMXController controller, 
                      Dictionary<string, string> parameters)
      {
#if DROID
        Android.Util.Log.Debug(“NavigationList”, “Adding: ‘” + pattern + “’”);
#endif
        // Enforce uniqueness
        MXNavigation currentMatch = this
          .Where(m => m.Pattern == pattern)
          .FirstOrDefault();
        if (currentMatch != null)
        {
#if DEBUG
          string text = string
           .Format(“MapUri \”{0}\” is already matched to Controller type {1}”,
                   pattern, currentMatch.Controller);
          throw new Exception(text);
#else
          return;
#endif
        }
        this.Add(new MXNavigation(pattern, controller, parameters));
      }
    }
  }
}

You inherit from the MXApplication  class to create your MonoCross application and register your workflow endpoints for navigation. 

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using MonoCross.Navigation;
using CustomerManagement.Controllers;
namespace CustomerManagement
{
  public class App : MXApplication
  {
    public override void OnAppLoad()
    {
      // Set the application title
      Title = “Customer Management”;
      // Add navigation mappings
      NavigationMap.Add(“Customers”, new CustomerListController());
      CustomerController customerController = new CustomerController();
      NavigationMap.Add(“Customers/{CustomerId}”, customerController);
      NavigationMap.Add(“Customers/{CustomerId}/{Action}”, customerController);
      // Set default navigation URI
      NavigateOnLoad = “Customers”;
    }
  }
} 

Adding Controllers to the Navigation Map

NavigationMap.Add(“Customers/{CustomerId}/{Action}”, customerController);

是在customController中选择一个Action操作后，再次去到另一个customController中，看会前面的customer的controller就可以看到在load方法中，有取了action参数出来，然后根据参数不同的取值，进行不同的操作。这样就把一个controller多次使用了。

Adding a Platform Container

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Text.RegularExpressions;
using MonoCross.Navigation;
namespace MonoCross.Console
{
  public static class MXConsoleNavigationExtensions
  {
    public static void Back(this IMXView view)
    {
      MXConsoleContainer.Back(view);
    }
  }
  public class MXConsoleContainer : MXContainer
  {
    public MXConsoleContainer(MXApplication theApp)
      : base(theApp)
    { }
    private class NavDetail
    {
      public string Path { get; set; }
      public Dictionary<string, string> Parameters { get; set; }
      public NavDetail(string path, Dictionary<string, string> parameters)
      {
        Path = path;
        Parameters = parameters;
      }
    }
    static Stack<NavDetail> NavHistory = new Stack<NavDetail>();
        
    public static void Initialize(MXApplication theApp)
    {
      MXContainer.InitializeContainer(new MXConsoleContainer(theApp));
      // non-threaded container, not needed as all input is blocking (old-school)
      MXContainer.Instance.ThreadedLoad = false;
    }
    public static void Back(IMXView view)
    {
      // exit if we try to go back too far
      if (!CanGoBack())
      {
        Environment.Exit(0);
      }
      else
      {
        // pop off the current view
        NavHistory.Pop();                
        // prepare to re-push the current view
        NavDetail backTo = NavHistory.Pop();
        // re-display the view
        Navigate(view, backTo.Path, backTo.Parameters);
      }
    }
    public static bool CanGoBack()
    {
      if (NavHistory.Count > 1)
        return true;
      else
        return false;
    }
    protected override void OnControllerLoadComplete(
        IMXView fromView, 
        IMXController controller, 
        MXViewPerspective perspective)
    {
      // store of the stack for later
      NavHistory.Push(new NavDetail(controller.Uri, controller.Parameters));
      // render the view
      MXConsoleContainer.RenderViewFromPerspective(controller, perspective);
    }
    protected override void OnControllerLoadFailed(IMXController controller, 
        Exception ex)
    {
      System.Console.WriteLine(“Failed to load controller: “ + ex.Message);
      System.Console.WriteLine(“Stack Dump”);
      System.Console.WriteLine(ex.StackTrace.ToString());
      System.Diagnostics.Debug.WriteLine(“Failed to load controller: “ 
                                         + ex.Message);
      System.Diagnostics.Debug.WriteLine(“Stack Dump”);
      System.Diagnostics.Debug.WriteLine(ex.StackTrace.ToString());
    }
    public override void Redirect(string url)
    {
      Navigate(null, url);
      CancelLoad = true;
    }
  }    
} 

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using MonoCross.Navigation;
using MonoCross.Console;
using CustomerManagement;
using CustomerManagement.Controllers;
using CustomerManagement.Shared;
using CustomerManagement.Shared.Model;
namespace CustomerManagement.Console
{
  class Program
  {
    static void Main(string[] args)
    {
      // initialize container
      MXConsoleContainer.Initialize(new CustomerManagement.App());
      // customer list view
      MXConsoleContainer.AddView<List<Customer>>(new Views.CustomerListView(),
                                                 ViewPerspective.Default);
      // customer view and customer edit/new
      MXConsoleContainer.AddView<Customer>(new Views.CustomerView(),
                                           ViewPerspective.Default);
      MXConsoleContainer.AddView<Customer>(new Views.CustomerEdit(),
                                           ViewPerspective.Update);
      // navigate to first view
      MXConsoleContainer.Navigate(MXContainer.Instance.App.NavigateOnLoad);
    }
  }
} 

一个controller会对应一个view 所以这里初始化view的数目要和navigationMap中德controller的一样，而且名字最好对应上，增加可读性。注意到AddView函数里面的第二个参数是ViewPerspective的，下面就说说这个参数

Working with View Perspectives

A view perspective is simply a string that describes the intended purpose of your view. 

public static class ViewPerspective
{
  public const string Default = “”;
  public const string Read = “GET”;
  public const string Create = “POST”;
  public const string Update = “PUT”;
  public const string Delete = “DELETE”;
}

View perspectives are used to uniquely register views in your container and are also used by your controllers to indicate to the container which view to render at a given point in your application.