这种布局将视图层相互层叠。
探索视图层和jsp。
您甚至可能同意验证代码不属于视图层的说法。
You may even agree with the argument that validation code doesn't belong in the view layer.
这些实体的行为最终由服务或视图层实现。
Behavior for these entities would end up being pushed up to the service or the view layer.
在MTV架构中，视图层描述应该向用户显示哪些数据。
In an MTV architecture, the View layer describes what data should be presented to the user.
模型框架结构分为数据层、应用服务层和视图层。
This model is composed of three tiers: data tier, application tier and presentation tier.
例如，不要将它放在应用程序的视图层和控制层之间。
For instance, don't put it between the view layer and the controller layer of an application.
视图层次中的布局是以一系列的线性方程来定义的。
The layout of your view hierarchy is defined as a series of linear equations.
从视图层的设计角度，facade也有提供业务处理的语义的优点。
From a design point of view, the facade also has the benefit of providing semantic meaning to the business process.
菜单也是用视图层次进行构架的，但你不必自己定义这个架构。
Menus are also structured using a View hierarchy, but you don't define this structure yourself.
中间件和工具将视图层ui技术连接到模型层web服务和数据。
Middleware and tools connect view-layer UI technologies to model-layer Web services and data.
例如，不要将Web服务放在应用程序的视图层和控制器层之间。
For example, don't put it between the view and the controller layers of an application.
从视图层次里删除一个视图就同时删除了该视图引用的所有约束。
Removing a view from the view hierarchy also removes all the constraints that reference that view.
每次变化，你都必须更新视图层次中的布局以实现最合理的布局。
With each change, you must update the layout of your view hierarchy to best use the available space.
依照最佳实践，视图层和控制层进行通信，控制层将通信转至业务层。
According to best practices, the view layer communicates with the control layer, which in turn communicates with the business layer.
如果改变了数据库结构，就需要相应地改变数据访问层、视图层等。
If you change the database structure, you need to accordingly change the data access layer, view layer.
响应者链是一组对象链接集，多数部分是通过视图层次结构向上延伸的。
This is a linked set of objects that, for the most part, goes backward up through the view hierarchy.
模板层定义向用户显示数据的方式，这相当于 MVC模式中的视图层。
The Template is the layer that defines how the data should be presented to the user, whereas this is considered the View layer in an MVC pattern.
如果Web应用程序高度依赖标记库，这种方式最终会造成视图层页面尺寸的增大。
If the Web application is highly dependent on taglibs, this approach will eventually lead to an increase in view-layer page size.
要想布置你的用户界面，你必须为视图层次中所有视图计算尺寸和位置。
To lay out your user interface, you had to calculate the size and position for every view in your view hierarchy.
因为数据库表本身没有行为，开发人员常常把领域模型实体的行为放在服务或视图层中。
Because database tables by themselves do not have behavior, it's tempting to put the behavior of domain-model entities in services or the view layer.
可以看出，由于使用了Ajax，视图层的脚本编写量增加了，从而导致三个明显缺陷。
You can see that the amount of scripting code in the view layer increases with the use of Ajax, causing three significant drawbacks.
比如，你可以使用他们来构建更小的视图层次，来展示图像，甚至于构建动态的内容。
For example, you can use them to build small view hierarchies, to display images, or even to draw content dynamically.
在视图层采用了视图助手模式，降低了系统之间各模块的耦合度，使系统容易维护和扩展。
These design patterns helps to reduce coupling degree between various modules of the system and makes the system to be easy to maintain and expand.
首先介绍JSF，它解决了控制器和MVCWeb应用程序视图层之间更清晰地分离这种需求。
When JSF was first introduced, it addressed the need for cleaner separation between the controller and the view layers of MVC Web applications.
应用程序的主要层是数据库、持久性框架、数据库访问对象和用户界面(UI)控制器及视图层。
The main layers of the application are a database, a persistence framework, a database access object, and user interface (UI) controller and view layers.
如欲获得更多关于视图层次如何测算以及绘制细节的讨论，情参阅Android如何绘制视图。
For a more detailed discussion on how view hierarchies are measured and drawn, read how Android Draws Views.
View对象是树的叶节点，而ViewGroup对象是树的分支(参阅楼上的视图层次图)。
View objects are leaves in the tree, ViewGroup objects are branches in the tree (see the View Hierarchy figure above).
一个Hobo模型仿佛具有生命一样；在控制器层和视图层的用户接口中，相应的动作会自动创建。
A Hobo model might also declare a lifecycle; corresponding actions are automatically created in the controller layer and user interfaces in the view layer.
一个Hobo模型仿佛具有生命一样；在控制器层和视图层的用户接口中，相应的动作会自动创建。
A Hobo model might also declare a lifecycle; corresponding actions are automatically created in the controller layer and user interfaces in the view layer.
应用推荐