mvvm

  • 网络视图模型
mvvmmvvm
  1. Extends data binding to methods , making MVVM architectures simple and intuitive .

    将数据绑定扩展为方法,使得MVVM架构更加简单和直观。

  2. This is simply intrinsic to the separation provided by MVVM .

    这正是MVVM所提供的分离的本质。

  3. Collections are one of the most difficult and least satisfactory aspects of the MVVM design pattern .

    集合是MVVM设计模式中最难、最不能让人满意的方面之一。

  4. The MVVM design pattern is a powerful and useful pattern , but no design pattern can solve every issue .

    MVVM设计模式是一种强大而实用的模式,但是没有任何一种设计模式能够解决所有问题。

  5. When is the MVVM design pattern applicable , and when is it unnecessary ?

    MVVM设计模式什么时候是适用的,什么时候又是不必要的?

  6. Adds pre / post execution filters and rescues to MVVM actions .

    为MVVM动作添加了前置/后置执行过滤器和修复程序。

  7. The separation of the View from the Model promoted by the MVVM design pattern is an important and valuable aspect of the pattern .

    MVVM设计模式将View从Model分离,这种做法是该模式的一个重要且有价值的方面。

  8. A screen is a unit of work , with no shared data between screens , and they are created following the MVVM pattern .

    一个屏幕就是一个工作单元(aunitofwork),在屏幕之间没有任何共享数据,并且它们都是遵循MVVM模式创建的。

  9. Controller – The MVVM pattern does not mention a controller but WAF contains one , having the responsibility to direct the flow of the application .

    Controller–MVVM模式中没有提到控制器,但是WAF中包含了一个,它的职责是指引程序的流向。

  10. However , the answer to the most basic questions when should you consider the MVVM design pattern and when is it unnecessary is often found in your domain model .

    但是,一些最基本问题(MVVM设计模式什么时候是适用的,什么时候又是不必要的)的答案经常包含在您的域模型中。