在这一节，可以开始深入项目正题，实现视图控制器。
With the view controller header out of the way, you're ready to dig into the meat of the project and to implement the view controller.
在MVC框架中，您要为每个视图定义一个视图控制器。
In the MVC framework, you define one view controller for each view.
第一部分，清单6，介绍应用程序开始部分和视图控制器的初始化。
The first section, Listing 6, covers the application startup and the initialization of the view controller.
要做到这点，你需要为每个界面都添加一个视图和视图控制器。
To accomplish this, you add a View and a View Controller for each screen you want to have.
在你导向另外一个页面的时候，就把视图控制器放到视图控制器堆栈中。
When you want to go to another page, you push your view Controller (and associated view) onto the view Controller stack.
每当用户在视图上执行一个操作时，每一个视图控制器就会接收到这个操作。
Each view controller receives the action every time the user performs an action on the view.
虽然此组件在视图控制器类内不具有已分配的实例变量，但是您需要定义类delegate。
This component does not have an assigned instance variable inside the view controller class, but you need to define the class delegate.
最后，您可以在ViewComponent中看到您视图的视图控制器类管理器(图9)。
At the end, you can see the view controller class manager of your view in the view Component (Figure 9).
如果想在iPhone应用程序中显示不同的界面，你要创建新的视图，并用视图控制器把其“推”到前端。
If you want different "screens" on an iPhone app, you create new views, and have a view controller push them into the front.
使用class下拉菜单为选中的Oneview视图分配OneViewController视图控制器类。
Assign the OneViewController view controller class for the selected One view view using the class drop down list.
如之前所述，您必须为每一个应用程序窗口创建一个视图nib文件和视图控制器，并将视图关联到正确的视图控制器类上。
As described above, you must create a view NIB file and view controller for each application window to associate any view to the correct view controller class.
为了简化，您将对视图控制器和表视图delegate这两种方法使用相同的类(如ListElementViewController)。
To simplify, you will use the same class (such as ListElementViewController) for two methods: view controller and table view delegate.
所有的数据和动作(请求服务器)都属于模型的一部分，和典型的模型-视图-控制器(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.
模型-视图-控制器(MVC)是一种常用的设计模式，用于构建许多不同类型的应用程序。
Model View Controller (MVC) is a popular design pattern for building many different types of applications.
这就是模型-视图-控制器和呈现-内容被认为是好东西的主要原因。
This is much of the reason that model-view-controller and presentation-content partitions are supposed to be good things.
Rails帮助器是帮助简化模型、视图、控制器代码的函数。
Rails helpers are functions that help to simplify model, view, or controller code.
最现代的Web应用程序框架都基于MVC(模型、视图、控制器)模式，Rails也不例外。
Most modern Web application frameworks are based on the MVC (model, view, controller) pattern, and Rails is no different.
例如，分层体系结构、模型-视图-控制器(Model View Controller,mvc)、客户机-服务器甚至SOA。
Think, for example, of layered architectures, model view controller (MVC), client-server, or even SOA.
Rubyon Rails是Web应用程序框架，使用模型-视图-控制器体系结构模式来组织应用程序。
Ruby on Rails is a Web application framework that USES the model-view-controller architectural pattern for organizing applications. It is built on two solid principles.
例如，在模型-视图-控制器(MVC)设计模式中，控制器调用方法。
For example, in the Model-View-Controller (MVC) design pattern, the controller invokes methods.
我们的应用开发工具支持“IBM电子商务框架”，它支持模型-视图-控制器（MVC）概念。
Our application development tools support the IBM Framework for e-business, which advocates the model view controller (MVC) concept.
该命令将创建模型-视图-控制器(mvc)的视图和控制器部分。
This command creates the proverbial view and controller part of Model-View-Controller (MVC).
这种方法是分离关注点原则的一个变种，附在模型-视图-控制器架构中。
This approach is a variation of the separation of concerns principle embodied in the Model-View-Controller architecture.
您很可能也知道这种分离的根源要追溯到最早的设计模式之一：模型-视图-控制器。
You probably also know that the roots of this separation go back to one of the earliest design patterns: Model-View-Controller.
它实现了模型-视图模型-视图-控制器这个看起来在WPF中很流行的模式。
It implements the Model - ViewModel - View - Controller pattern that seems to be popular in WPF.
这项设计技术叫做模型-视图-控制器(mvc)，它使对视图或模型的更改更容易分隔开。
This design technique, called model-view-controller (MVC), makes it easier to isolate changes to a view or model.
其中使用最广泛的一个模式就是模型-视图-控制器(mvc)。
One of the most widely used patterns is Model-View-Controller (MVC).
数十年来，程序员们使用模型-视图-控制器简化了代码结构，并使得维护任务更加容易。
Programmers have simplified their code structure and eased maintenance tasks with Model-View-Controller for decades.
这两种方法各有优缺点，但我们认为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.
现在可以自由地在模型-视图-控制器Web体系结构中的两个控制器之间进行选择。
There is now the freedom of choice between the two controllers in a Model-View-Controller Web architecture.
应用推荐