我们正在混合模型和视图逻辑。
操作提供模型和视图之间的链接。
控制器——控制器是模型和视图间的粘合剂。
Controller - the controller is the glue between the Model and the View.
将该函数传递到插件上下文、数据模型和视图的ID。
This is passed to the context of the plug-in, the data model, and the ID of the view.
之后你可以使用命令行工具生成控制器、模型和视图。
In the end you should be able to do IronNails, which will give you an application skeleton. After that you can generate controllers, models and even views with a command-line generate command.
因此，他们能够之间传输的模型和视图层的数据。
As such, they are able to transfer data between the Model and View layers.
真实的应用程序有着比模型和视图的分离更多的通用特性。
Real applications have many more traits in common than a separation between model and view.
这意味者开发人员必须手工写出数据在模型和视图来回同步的两套代码。
This means that the developer has to write code that constantly syncs the view with the model and the model with the view.
所有的xml绑定api都具有手工序列化技术的一个主要不足：模型和视图的耦合。
All of the XML binding APIs share a major drawback with the manual serialization technique: the coupling of model and view.
不过，您通常希望根据Web应用程序的不同功能领域对操作(及其相关的模型和视图)进行分组。
However, you might often wish to group Actions (and their related Models and Views) together based on the different functional areas of your Web application.
希望这种表单开发方式能够突出XForms标准最引人注目的一个方面：清晰地划分模型和视图。
Hopefully, addressing form development in this way has highlighted one of the appealing aspects of the XForms standard: the clean separation of model and view.
本文将帮助您构建一个微型列表JSONREST控制器，您可以将其放置到您的模型和视图功能之间。
This article will help you build a minimalist JSON REST controller that you can place between your model and view functionality.
显然，你并不想把模型和视图搞成一样的东西，因为完全没有分离的话只会让应用程序一团糟。
Obviously, you don't want the model and view to be the same thing because then, there is no separation at all and the application will be a tangled mess.
该框架充分运用XML和XSLT技术，更好地分离了控制、模型和视图，更多地减少了用户代码。
The frame, applying with XML and XSLT technologies, make controller, model, and view more separated and make user's program code much less.
请记住，这不是一个静态的序列，而需要在各种模型和视图之间进行反馈和迭代，直到利益相关者的需求。
Remember that this is not a static sequence but requires feedback and iteration between the various models and views all the way back to the stakeholder requirements.
在模型和视图之间的清楚分离，对于降低耦合很重要，并使对视图的根本修改不会影响到模型，反之亦然。
Clean separation between model and view is important to reduced coupling, making radical view changes less likely to ripple into the model and vice versa.
为了使用流行的设计模式（MVC），您必须重写公司Web站点的代码，使模型和视图不特定于某种编程语言。
Using a popular design pattern (MVC), you must rewrite the code of the corporate Web site so the model and the view are not bound to a particular programming language.
该平台对于SOA的意义在于使用普通的域架构模型和视图，来将SOA - RM元素，与来自IT架构的概念联合起来。
The significance of this platform to SOA is that RA combines SOA-RM elements with concepts from common it architectures by using common domain architecture models and views.
不管您如何选择，请确保您的模型和视图之间实现了完全的分离，从而避免最基本的服务器端反模式：魔法Servlet。
Whatever you decide, make sure that you achieve a clean separation between your model and view to stay out of the most fundamental server-side antipattern: the Magic Servlet.
模型-视图-控制器(Model,View,Controller,mvc)框架，拆分为两个部分：actioncontroller用于控制器，而ActionView用于模型和视图。
An MVC (model, view, controller) framework, split into two parts: ActionController for the controller and ActionView for the model and view.
实际上，您是否意识到这个应用程序的完成只使用了一个控制器、一个模型和五个视图？
In fact, did you realize that you completed this application using only one controller, one model, and five views?
这个应用程序的设计原则是消除视图和模型之间的耦合。
The general design of the application is to remove the coupling of the view from the model.
使用此方法，数据(模型)和用户界面(视图)将彼此分离，以便对一个方面的更改不会影响另一个方面。
Using this approach, the data (model) and user interfaces (view) are separated so that changes to one will not affect the other.
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.
然后将这些事件映射到远程对象调用，以便将代码细节置于视图和模型之外。
You can then map the events to remote object invocation, leaving the details of the code out of your views and model.
指定包的内容将包含刚才创建的查询、FPML数据模型和CREDITV视图。
Specify that the contents of the package will include the query you created, the FPML data model, and the CREDITV view.
首先要创建视图，而不是模型和控制器。
Instead of creating models and controllers, we create views first and go from there.
了解操作、视图、模型和路由之间的交互。
Understand the interaction between actions, views, models and routes.
现在，您可以使用更多Rails特性来添加更多模型、控制器和视图。
From here, you can use more Rails features to add more models, controllers, and views.
应用程序目录，包括模型、视图和控制器的子目录。
Application directories with subdirectories for model, view, and controller.
应用推荐