用于代码生成的模型-视图-控制器模式。
WebFlow 在典型的模型-视图-控制器级别上操作。
Web Flow works above the typical model-view-controller level.
所有的数据和动作(请求服务器)都属于模型的一部分，和典型的模型-视图-控制器(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.
这个问题的解决方案是使用一种修改过的、更适合基于servlet编程的模型-视图-控制器来进行重构。
The solution to this problem is to refactor with a modified model-view-controller that is more appropriate for servlet-based programming.
Servlet构成典型的模型-视图-控制器（MVC）体系结构的控制器层，并充当表示层和模型层的接口。
Servlets form the controller layer of a typical Model-View-Controller (MVC) architecture and serve as an interface between the presentation and the model layers.
如果您通过像Struts这样的模型-视图-控制器框架来调用这些服务，那么您最终将会得到如图2所示的mvc膨胀。
If you invoke these services through some model-view-controller framework like Struts, you wind up with MVC Bloat as shown in Figure 2.
第5章向您介绍了在Rails中所包含的模型-视图-控制器架构的详细内容，以及如何让这三部分按您想要的方式进行交互。
Chapter 5 gives you the details of the Model-View-Controller architecture embodied in Rails and how to get the three parts to interact the way you want to.
这个策略与流行的模型-视图-控制器（Model-View-Controller，MVC）设计模式相兼容（见图3）。
This strategy is easily compatible with the popular Model-View-Controller (MVC) design pattern (see figure 3).
这个方法违反了JSF的模型-视图-控制器(MVC)架构(请参阅参考资料)，MVC架构要求使用模型bean保存应用程序数据。
The approach violates JSF's Model-View-Controller (MVC) architecture (see Resources), which requires the use of model beans to hold application data.
在几年前，PHP一直缺乏一个良好的、功能完善的模型-视图-控制器(Model - View - Controller,mvc)框架。
Until a few years ago, PHP lacked a good, functional Model-View-Controller (MVC) framework. MVC frameworks let programmers organize their code into three distinct functional areas.
因此，一些Portlet框架得到支持，并且应该遵循一些最佳实践，例如，优秀的模型-视图-控制器(Model - View - Controller)设计。
Therefore, portlet frameworks are supported and should follow best practices such as a good Model-View-Controller design.
目前基本的模型-视图-控制器(Model - View - Controller,mvc)框架已经准备就绪，我将加入一些外部技术，具体来讲，我将加入地图功能。
Now that the basic Model-View-Controller (MVC) framework is in place, I'm ready to mix in some external technologies. Specifically, I'm going to add a map.
依赖注入让您将应用程序的主要层次编织到一起，从而，这使您产生一个具有视图、模型和控制器层的松散耦合应用程序。
Dependency injection lets you weave together the main layers of your application, which, in turn, lets you produce a loosely coupled application with view, model, and controller layers.
您很可能也知道这种分离的根源要追溯到最早的设计模式之一：模型-视图-控制器。
You probably also know that the roots of this separation go back to one of the earliest design patterns: Model-View-Controller.
将对视图和控制器的引用放在模型之外，可以使模型更易于开发和测试。
Keeping view and controller references out of your model makes it much easier to develop and test.
另一个重大变化是实现视图所用的技术与实现模型或控制器的技术不同。
Another noticeable change is that the view USES different technology for implementation than the model or controller.
该命令将创建模型-视图-控制器(mvc)的视图和控制器部分。
This command creates the proverbial view and controller part of Model-View-Controller (MVC).
这项设计技术叫做模型-视图-控制器(mvc)，它使对视图或模型的更改更容易分隔开。
This design technique, called model-view-controller (MVC), makes it easier to isolate changes to a view or model.
控制器——控制器是模型和视图间的粘合剂。
Controller - the controller is the glue between the Model and the View.
这种方法是分离关注点原则的一个变种，附在模型-视图-控制器架构中。
This approach is a variation of the separation of concerns principle embodied in the Model-View-Controller architecture.
其中使用最广泛的一个模式就是模型-视图-控制器(mvc)。
One of the most widely used patterns is Model-View-Controller (MVC).
控制器和视图是完全自动基于模型的。
The controller and view are fully automated based on the model.
它实现了模型-视图模型-视图-控制器这个看起来在WPF中很流行的模式。
It implements the Model - ViewModel - View - Controller pattern that seems to be popular in WPF.
记住，控制器的职责是为视图准备模型对象。
Remember the job of the controller is to prepare the model for the view..
随着时间推移，很多框架代替了控制器的角色，而模型-视图分离也变得微不足道。
Over time, many frameworks took the role of the controller, and model-view separation became trivial.
控制器的目的是为视图准备模型对象。
The goal of the controller is to prepare the model for the view.
控制器的目标是充当从模型到视图的粘合剂。
The goal of the controller is to act as the glue from the model to the view.
应用程序目录，包括模型、视图和控制器的子目录。
Application directories with subdirectories for model, view, and controller.
为了说明这些限制，要创建带有模型、视图和控制器的Location。
To illustrate these limitations, you'll create a Location with model, view, and controller.
Rails帮助器是帮助简化模型、视图、控制器代码的函数。
Rails helpers are functions that help to simplify model, view, or controller code.
应用推荐