DPTK设计为使用模型-视图-控制器模式。
模型-视图-控制器(MVC)模式。
用于代码生成的模型-视图-控制器模式。
重构的解决方案：应用模型-视图-控制器。
JPA：支持对象持久化的“模型-视图-控制器”。
这种假定就意味着您根本不需要担心模型-视图分离，对吗？
This assumption means that you don't need to worry about model-view separation at all, right?
WebFlow 在典型的模型-视图-控制器级别上操作。
Web Flow works above the typical model-view-controller level.
其中使用最广泛的一个模式就是模型-视图-控制器(mvc)。
One of the most widely used patterns is Model-View-Controller (MVC).
该命令将创建模型-视图-控制器(mvc)的视图和控制器部分。
This command creates the proverbial view and controller part of Model-View-Controller (MVC).
这就是模型-视图-控制器和呈现-内容被认为是好东西的主要原因。
This is much of the reason that model-view-controller and presentation-content partitions are supposed to be good things.
例如，在模型-视图-控制器(MVC)设计模式中，控制器调用方法。
For example, in the Model-View-Controller (MVC) design pattern, the controller invokes methods.
Struts鼓励在模型-视图-控制器设计范例基础上构建应用程序。
Struts encourages application architectures based on the Model-View-Controller design paradigm.
这种方法是分离关注点原则的一个变种，附在模型-视图-控制器架构中。
This approach is a variation of the separation of concerns principle embodied in the Model-View-Controller architecture.
它实现了模型-视图模型-视图-控制器这个看起来在WPF中很流行的模式。
It implements the Model - ViewModel - View - Controller pattern that seems to be popular in WPF.
“模型-视图-控制器”(MVC)就是用来帮助您控制变化的一种设计模式。
Model-View-Controller (MVC) is a design pattern put together to help control change.
模型-视图-控制器(MVC)是一种常用的设计模式，用于构建许多不同类型的应用程序。
Model View Controller (MVC) is a popular design pattern for building many different types of applications.
随着时间推移，很多框架代替了控制器的角色，而模型-视图分离也变得微不足道。
Over time, many frameworks took the role of the controller, and model-view separation became trivial.
您很可能也知道这种分离的根源要追溯到最早的设计模式之一：模型-视图-控制器。
You probably also know that the roots of this separation go back to one of the earliest design patterns: Model-View-Controller.
数十年来，程序员们使用模型-视图-控制器简化了代码结构，并使得维护任务更加容易。
Programmers have simplified their code structure and eased maintenance tasks with Model-View-Controller for decades.
这项设计技术叫做模型-视图-控制器(mvc)，它使对视图或模型的更改更容易分隔开。
This design technique, called model-view-controller (MVC), makes it easier to isolate changes to a view or model.
我们的应用开发工具支持“IBM电子商务框架”，它支持模型-视图-控制器（MVC）概念。
Our application development tools support the IBM Framework for e-business, which advocates the model view controller (MVC) concept.
例如，分布式对象开发环境中的模型-视图-驱动器(MVC)模式将模型与视图和控制器分离开来。
For example, the Model-View-Controller (MVC) pattern in distributed object development environments separates the model from the view from the controller.
所有的数据和动作(请求服务器)都属于模型的一部分，和典型的模型-视图-控制器(MVC)架构一样。
All the data and the actions (requests to the server) are part of the model, as is common in typical model View Control (MVC) architectures.
这两种方法各有优缺点，但我们认为XSL - FO模型在视图层上更适合模型-视图-控制器(MVC)架构。
Both approaches have their pros and cons, but we believe that the XSL-FO model fits better in the Model-View-Controller architecture (MVC) architecture at the view tier.
例如，假定您知道需要分离模型-视图-表示器(Model - View -Presenter)关注点。
For example, suppose you know that you want the separation of concerns of Model-View-Presenter.
图1不包括任何持久性或者系统类，但是如果包括了，您将创建一个我们的模型视图，它没有显示这些类。
Figure 1 does not include any persistence or system classes, but if it did, you would want to create a view of our model that did not show them.
图1显示了此体系结构的逻辑模型视图。
表示此区域的模型视图集合的主题是依赖关系管理。
The theme for the collection of model views that represents this area is dependency management.
哪一个单个模型视图将被处理？以及每个视图将开发出哪些工件？
Which individual model views will be addressed and what artifacts will be developed for each view?
MVC架构（或设计模式）是图形用户界面（GUI）的设计样式，由三部分构成：模型、视图和控制器。
The MVC architecture (or design pattern) is a graphical user interface (GUI) design style that consists of three parts: model, view, and controller.
应用推荐