Puremvc

Puremvc

框架unitypuremvc

PureMVC健壮、易扩展、易维护
Many so-called Model-View-Controller frameworks today seem to include everything but the kitchen sink. We decided that basic separation of responsibilities according to the MVC meta-pattern could be expressed with a handful of actors. We gave them a built-in means to communicate with each other which reinforces the classic MVC collaboration patterns, and did so with the simplest possible language features. That's why it's been ported to so many languages from the original ActionScript. It just works, with no "magic happens here" bits.

PureMVC优缺点：

• 1.利用中介者，代理者，命令实现解耦，使得Model、View、Controller之间耦合性降低,提升了部分代码的重用
• 2.View界面可以实现重用
• 3.Model数据可以实现重用
• 3.代码冗余量大,对于简单的功能都得创建View、Mediator、Command、Facade，Proxy，Model脚本
• 4.操作过程比较繁琐的流程，Mediator中的代码会显得流程较为复杂难懂，除非你很熟悉PureMVC执行原理

PureMVC特点：

• 1.通知的传递都要经过装箱和拆箱的操作
• 2.命令/通知是以观察者模式实现，命令/通知在观察者中利用反射获取方法并执行
• 3.没有Service（可按照MVC的构造，自行添加与网络通讯的这个模块）
• 4.数据通过通知传递，SendNotification只有一个object类型参数，会感觉数据传输受限，可以将数据组合成一个类型/结构传递，或者是为Notification再拓展一个参数。

一、结构及示例

核心结构

1、PureMVC结构

• PureMVC把程序分为低耦合的三层：Model、View和Controller。
• ureMVC实现的经典MVC元设计模式中，这三部分由三个单例模式类管理，分别是Model、View和Controller。三者合称为核心层或核心角色。
  -PureMVC中还有另外一个单例模式类——Facade，Facade提供了与核心层通信的唯一接口，以简化开发复杂度。

2、层级关系

三联

PureMVC使用了观察者模式，所以各层之间能以一种松耦合的方式通信，并且与平台无关。

2.1、Model

数据层

1. public class MyData 

   ---

2. { 

   ---

3. public int DataValue { get; set; } 

   ---

4. } 

   ---

5.  

   ---

2.2、Proxy

Proxy负责操作具体的数据模型，这样保住了Model层的可移植性，Model只需维持自己的数据结构就好。

1. using PureMVC.Patterns; 

   ---

2.  

   ---

3. /// <summary> 

   ---

4. /// 通过proxy代理来进行对数据model的操作 

   ---

5. /// </summary> 

   ---

6. public class MydataProxy : Proxy 

   ---

7. { 

   ---

8. public const string proxname = "MyData01"; 

   ---

9.  

   ---

10. public MyData MyData; 

    ---

11. public MydataProxy() : base(proxname) 

    ---

12. { 

    ---

13. MyData = new MyData();  

    ---

14. } 

    ---

15.  

    ---

16.  

    ---

17. public void AddValue() 

    ---

18. { 

    ---

19. MyData.DataValue++; 

    ---

20.  

    ---

21. //Facade 和Proxy只能发送Notification，Mediators既可以发送也可以接收Notification，Notification被映射到 Command， 

    ---

22. //同时Command也可以发送Notification。这是一种“发布/订阅”机制，所有的观察者都可以收到相同的通知。 

    ---

23. //例如多个书刊订阅者可以订阅同一份杂志，当杂志有新刊出版时，所有的订阅者都会被通知。 

    ---

24. SendNotification("msg_add",MyData); 

    ---

25. } 

    ---

26.  

    ---

27. public void SubValue() 

    ---

28. { 

    ---

29. MyData.DataValue--; 

    ---

30.  

    ---

31. SendNotification("msg_add", MyData); 

    ---

32. } 

    ---

33.  

    ---

34. } 

    ---

2.3、Mediator

Mediator中介由,Mediator对象来操作具体的视图组件，包括：添加事件监听器，发送或接收Notification ，直接改变视图组件的状态。
这样做实现了把视图和控制它的逻辑分离开来。

1. using System.Collections.Generic; 

   ---

2. using PureMVC.Interfaces; 

   ---

3. using PureMVC.Patterns; 

   ---

4. using UnityEngine; 

   ---

5. using UnityEngine.UI; 

   ---

6.  

   ---

7. public class MyMediator : Mediator 

   ---

8. { 

   ---

9. public const string MediatorName = "MyMeditor"; 

   ---

10.  

    ---

11. public Text textNum; 

    ---

12. public Button AddButton; 

    ---

13. public Button SubButton; 

    ---

14.  

    ---

15. public MyMediator(GameObject root):base(MediatorName) 

    ---

16. { 

    ---

17. //持有对视图中对象的引用 

    ---

18. textNum = root.transform.Find("TextValue").GetComponent<Text>(); 

    ---

19. AddButton= root.transform.Find("BtnAdd").GetComponent<Button>(); 

    ---

20. SubButton= root.transform.Find("BtnSub").GetComponent<Button>(); 

    ---

21.  

    ---

22.  

    ---

23. // 视图中的操作 

    ---

24. AddButton.onClick.AddListener(Addbtn); 

    ---

25. SubButton.onClick.AddListener(Subbtn); 

    ---

26. } 

    ---

27.  

    ---

28. /// <summary> 

    ---

29. /// 操作视图 

    ---

30. /// </summary> 

    ---

31. /// <param name="myData">数据对象</param> 

    ---

32. private void DisplayFun(MyData myData) 

    ---

33. { 

    ---

34. textNum.text = myData.DataValue.ToString(); 

    ---

35. } 

    ---

36.  

    ---

37. /// <summary> 

    ---

38. /// 与command层通信 

    ---

39. /// </summary> 

    ---

40. private void Subbtn() 

    ---

41. { 

    ---

42. SendNotification("cmd_sub"); 

    ---

43. } 

    ---

44.  

    ---

45. /// <summary> 

    ---

46. /// 与command层通信 

    ---

47. /// </summary> 

    ---

48. private void Addbtn() 

    ---

49. { 

    ---

50. SendNotification("cmd_add"); 

    ---

51. } 

    ---

52.  

    ---

53. /// <summary> 

    ---

54. ///定义自己需要关心的消息 

    ---

55. /// </summary> 

    ---

56. /// <returns></returns> 

    ---

57. public override IList<string> ListNotificationInterests() 

    ---

58. { 

    ---

59. List<string> list=new List<string>() 

    ---

60. { 

    ---

61. "msg_add","msg_sub" 

    ---

62. }; 

    ---

63. return list; 

    ---

64. } 

    ---

65.  

    ---

66. /// <summary> 

    ---

67. /// 处理消息 

    ---

68. /// </summary> 

    ---

69. /// <param name="notification"></param> 

    ---

70. public override void HandleNotification(INotification notification) 

    ---

71. { 

    ---

72. switch (notification.Name) 

    ---

73. { 

    ---

74. case "msg_add": 

    ---

75. case "msg_sub": 

    ---

76. DisplayFun(notification.Body as MyData);  

    ---

77. break; 

    ---

78. default: 

    ---

79. break; 

    ---

80. } 

    ---

81. }  

    ---

82. } 

    ---

83.  

    ---

2.4、Command

Command命令层，Command可以获取Proxy对象并与之交互，发送Notification，执行其他的Command。经常用于复杂的或系统范围的操作，如应用程序的“启动”和“关闭”。应用程序的业务逻辑应该在这里实现。

1. using PureMVC.Interfaces; 

   ---

2. using PureMVC.Patterns; 

   ---

3.  

   ---

4. public class MyCommandAdd : SimpleCommand 

   ---

5. { 

   ---

6. public override void Execute(INotification notification) 

   ---

7. { 

   ---

8. //直接调度Proxy处理具体逻辑 

   ---

9. MydataProxy mydataProxy = Facade.RetrieveProxy("MyData01") as MydataProxy; 

   ---

10.  

    ---

11. mydataProxy.AddValue(); 

    ---

12. } 

    ---

13. } 

    ---

14.  

    ---

15. public class MyCommandSub : SimpleCommand 

    ---

16. { 

    ---

17. public override void Execute(INotification notification) 

    ---

18. { 

    ---

19.  

    ---

20. MydataProxy mydataProxy = Facade.RetrieveProxy("MyData01") as MydataProxy; 

    ---

21.  

    ---

22. mydataProxy.SubValue(); 

    ---

23. } 

    ---

24. } 

    ---

2.5、MyFacade

Facade类应用单例模式，它负责初始化核心层（Model，View和Controller），并能访问它们的Public方法。
这样，在实际的应用中，你只需继承Facade类创建一个具体的Facade类就可以实现整个MVC模式，并不需要在代码中导入编写Model，View和Controller类。
Proxy、Mediator和Command就可以通过创建的Façade类来相互访问通信。
一般地，实际的应用程序都有一个Facade子类，这个Facade类对象负责初始化Controller（控制器），建立Command与Notification名之间的映射，并执行一个Command注册所有的Model和View。

1. using PureMVC.Patterns; 

   ---

2. using UnityEngine; 

   ---

3.  

   ---

4. public class MyFacade : Facade 

   ---

5. { 

   ---

6. public MyFacade(GameObject root) : base() 

   ---

7. { 

   ---

8. //注册命令，实现消息与命令之间的绑定 

   ---

9. RegisterCommand("cmd_add",typeof(MyCommandAdd)); 

   ---

10. RegisterCommand("cmd_sub",typeof(MyCommandSub)); 

    ---

11.  

    ---

12. RegisterMediator(new MyMediator(root)); 

    ---

13. RegisterProxy(new MydataProxy()); 

    ---

14. } 

    ---

15. } 

    ---

2.6 初始化Facade

注意：除了顶层的Application，其他视图组件都不用（不应该）和Façade交互。

顶层的Application构建视图结构、初始化Façade，然后“启动”整个PureMVC机制。

1. using System.Collections; 

   ---

2. using System.Collections.Generic; 

   ---

3. using UnityEngine; 

   ---

4.  

   ---

5. public class GameManager : MonoBehaviour 

   ---

6. { 

   ---

7. public GameObject root; 

   ---

8. // Start is called before the first frame update 

   ---

9. void Start() 

   ---

10. { 

    ---

11. //初始化MyFacade启动PureMVC 

    ---

12. MyFacade myFacade = new MyFacade(root); 

    ---

13. } 

    ---

14.  

    ---

15. } 

    ---

它山之石可以攻玉

[Unity]PureMVC框架解读(上)