We need this knowledge to create more customized controllers and views for your application.
我们需要使用这些知识为应用程序创建更加个性化的控制器和视图。
Sitebricks is a model-view-control (MVC) style of framework, but it concentrates on the controllers and views in your application.
Sitebricks是一种模型-视图-控制（MVC）类型的框架，不过它专注于应用程序中的控制器和视图。
In some cases, though, your projects will only have controllers and views-a perfect solution if you're building a static web site without a database back end.
不过在某些情况下，您的项目将只具有控制器和视图—如果您正在没有数据库后端的情况下构建静态web站点，这将是一个完美的解决方案。
Also, if you alter your domain model to not use the "default" package you lose the navigation decorators and the ability to generate Controllers and Views inside the ide.
同样的，如果你改变你的领域模型不使用“缺省”包，你也会失去导航功能条和在IDE内生成控制器和视图的能力。
The default controllers and views can be useful to get your project started, but we tend to use the Empty template so that our application contains only the items that we need.
默认的控制器和视图可能对你开始项目是有用的，但我们倾向于使用空模板，以使我们的应用程序只含有我们所需要的条目。
For example, a default Hobo application provides for user signup and login; out of the box an application comes with a user model as well as controllers and views for registration and authentication.
例如，一个Hobo缺省应用会提供用户注册和登录功能；缺省情况下，应用程序包括一个用户模型以及负责注册验证的控制器和视图。
If you don't need the added separation, or find that maintaining models requires more complexity than you want, you can ignore them and build your application minimally using Controllers and Views.
如果你不需要使用模型这一层，或是认为维护模型比你想象中的复杂很多，那么你可以忽略它，而只使用控制器和视图创建你的应用程序。
Now that the controllers are updated with new data being sent to the views, you need to update the views to capture this data and display it appropriately to the user.
既然控制器与将传送给视图的新数据是一起更新的，那么我们需要更新该视图来捕获此数据，并适当地将其展示给用户。
Typically, your application will have a series of controllers, all of which will pull data from models and then display data in views.
通常情况下，您的应用程序将具有一系列控制器，所有的控制器都将从模型中提取数据，然后在视图中显示。
Because of this separation, multiple views and controllers can work with the same model.
通过这种分离方式，多个视图以及控制器就可以同时与一个模型一起工作了。
Instead of creating models and controllers, we create views first and go from there.
首先要创建视图，而不是模型和控制器。
In this article we're going to make another simple application, but this time we're going to explore using Views and View Controllers to make an application with more than one screen.
在这篇文章中，我们将要创建另外一个简单的应用程序，不过这次要学习下如何使用Views(视图)和ViewControllers(视图控制器)来创建一个具有多个界面的应用程序。
From here, you can use more Rails features to add more models, controllers, and views.
现在，您可以使用更多Rails特性来添加更多模型、控制器和视图。
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.
之后你可以使用命令行工具生成控制器、模型和视图。
Cocoa is implemented in Object-C and USES the MVC pattern to encapsulate views, application data, controllers and the class to mediate the management logic.
Cocoa是用Object - c实现的，并使用MVC模式来封装视图、应用程序数据、控制器和实现管理逻辑的类。
If the facade is built well (with no dependencies on the view or controller), it can even be used for different kinds of views and controllers.
如果facade创建的很好(与视图层或控制器层没有关系)，它甚至可以被用在不同种类的视图层和控制器层。
A central component of Rails is the class ActiveRecord, which maps relational tables to Ruby objects and thereby to the data manipulated by controllers and shown in views.
activerecord类是Rails的一个核心组成部分，它将关系型表映射为Ruby对象，使其成为控制器可以操作并能在视图中显示的数据。
For this example, you want to be sure that you're allowing Grails to scaffold both the controllers and the views dynamically.
对于这个示例，需要确保既允许Grails动态搭建控制器，又允许它动态搭建视图。
This decoupling makes it easier to test your views and controllers.
这种解耦使得视图和控制器更易于测试。
At each tier, the devices embody models computation, apps, views the display, and controllers input and interaction capability.
每一层的设备都实现了模型(计算，应用程序)，视图(展现)和控制器(输入和交互能力)。
It puts controllers as the main player in a web application, deciding the flow, delegating to other layers and choosing views to render, hence it only CARES about application flow logic.
它以控制器作为Web应用程序中的主要角色，决定流程，委托到其他层并选取视图来呈现，因此它只关心应用程序的流程逻辑。
Your models go in the models folder, the views into views, controllers into controllers, and so on.
模型存放在models文件夹中、视图存放在views文件夹中、控制器存放在controllers文件夹中，依此类推。
You can create controllers, views, and models in an area just as you have seen in previous examples.
就像你在前面的例子中所看到的，你可以在一个区域中生成控制器、视图、以及模型等。
This is useful in a large project, where having a single set of folders for all of the controllers, views, and models can become difficult to manage.
这对大型项目是很有用的，对所有控制器、视图、和模型只用一组文件夹，可能会使管理变得困难。
Type grails generate-all Trip to build out a grails-app/controllers/TripController.groovy class and a matching set of Groovy Server Pages (GSPs) in grails-app/views/Trip.
输入grailsgenerate-all Trip，以构建一个grails-app/controllers/TripController.groovy类，并在 grails-app/views/Trip 中生成一组匹配的GroovyServerPage（GSP）。
Controllers are the glue between views and the model.
控制器是视图与模型之间的粘合剂。
One way to better prepare for writing a solid architecture is to follow certain conventions and define application views, models, stores and controllers before actually implementing them.
写一个可靠架构有一条更好的解决之道，就是跟随确定的惯例，在实际实现之前就定义好应用的视图、模型、存储和控制器。
View controllers can also display modal views, respond to low-memory warnings, and rotate views when the orientation changes.
视图控制器也可以显示独占的视图、回应低内存警告，以及当方向改变时旋转视图。
Models don't deal with rendering UIs or processing requests—those are the responsibilities of views and controllers.
模型不涉及渲染UI或处理请求—那些是视图和控制器的责任。
Models don't deal with rendering UIs or processing requests—those are the responsibilities of views and controllers.
模型不涉及渲染UI或处理请求—那些是视图和控制器的责任。
应用推荐