A novel design which combines PCI Core and user logic is adopted. In the hardware design, the clutter module is embedded.
采用基于PCI内核与PCI用户逻辑相结合的新型设计方案，并且在硬件设计中加入了杂波产生模块。
If this were more than a demo, some other logic would choose the parameter, perhaps prompting the user to supply the information.
如果这不仅仅是一个演示的话，某些其他的逻辑将选择参数，可能会提示用户提供该信息。
It is simple but slow, especially when the user interface and logic are complicated.
这是简单的，但却是缓慢的，尤其在用户界面和逻辑复杂时。
Of course, you can add whatever logic you want, extra channels, user validation and login, and so on.
当然，您可以添加您想要的任何逻辑，额外的通道、用户验证和登录，等等。
For example, we might add user interface logic that we want to keep separate from our model, or we might add some classes for performance reasons.
例如，我们可能会添加想与模型分离开来的用户接口逻辑，或者我们可能会出于性能方面的原因而添加某些类。
In actual applications, there would be a more complex logic to collect the user identity for assertion.
在实例的应用程序中，可以使用更复杂的逻辑来收集断言的用户标识。
The logic is there to create conceptual user interfaces, but the transactions will have to be reversed before they can be applied.
这儿的逻辑是创建概念上的用户接口，但是事务处理将不得不在应用之前被逆转。
It is common for architects of database interaction logic, for example, to have no knowledge of how their logic is specifically expressed via user interface code.
举例来说，对于数据库交互逻辑的设计师来说，不知道他们的逻辑是如何通过用户接口代码表示出来，是很普通的现象。
Those values are provided from business logic or from previous user input.
这些值是由业务逻辑或先前的用户输入所提供的。
But including user interface logic in a use case is generally considered bad form.
但是在用例中包括用户接口逻辑通常被认为是不好的形式。
Common J2EE Artifacts introduce how to isolate and customize the resources of user interfaces and business logic via an implicit filter-based mechanism among tenants.
公用j2ee工件说明如何通过一种基于隐式筛选器的机制区分租户，隔离和定制用户界面和业务逻辑的资源。
It's a module with business logic, and it's a widget with a user interface.
它是一个包含业务逻辑的模块，也是一个拥有用户界面的部件。
It is not concerned with the dynamic behavior of the user interface, or even of business logic behavior.
它与用户界面的动态行为无关，甚至和事务逻辑行为也无关。
The user interface and application logic of this component must be flexibly adaptable to the different items that may be managed.
该组件的用户界面和应用程序逻辑必须能灵活地适应可能要管理的各种项。
The 4gl vendor assumes the burden of maintenance for these frameworks and the developer is free again to focus on the user interface and core business logic.
4gl供应商承担这些框架的维护责任，开发人员重新获得自由，可以专注于用户界面和核心业务逻辑。
With the subroutines in place, the main program logic allows the user to create a knock sequence, or runs in daemon mode to listen for knocks and execute commands.
利用这些子程序，主程序的逻辑允许用户创建敲打序列，或在守护模式下监听敲打序列并执行命令。
In a small JSP application, it is common to see the data, business logic, and the user interface combined into one module of code.
在小型JSP应用程序中，经常会看到数据、业务逻辑和用户界面被组合在一个代码模块中。
These backups can be used to restore databases to their proper state after data corruption events, such as software failures, hardware failures, bad application logic, and user errors.
当发生数据毁坏事故，例如软件故障、硬件故障、错误的应用程序逻辑和用户错误后，可以使用这些备份将数据库恢复到适当的状态。
It was primarily devised as a strategy for separating user interface logic from business logic.
最初它主要是作为一种分离用户接口逻辑与业务逻辑的策略被设计出来的。
View logic is concerned with presenting information to the user and collecting information from the user.
视图逻辑关注于向用户表达信息和从用户那里搜集信息。
The business logic the user already put in is preserved.
用户已经置入的业务逻辑就会保存。
This ensures the security of the information being transferred and accessed is also left to the user to enforce in their application logic.
用户还需对其应用程序逻辑进行增强，以确保被传递和访问的信息的安全性。
A common architectural strategy is to layer your system, separating your user interface logic, business logic, system logic, and persistence logic from each other.
通常的构造策略是将系统分层，将用户界面逻辑、商业逻辑、系统逻辑和持久性逻辑彼此分开。
The user interface (UI), business logic, and configuration, or lack thereof, are mixed together with no thought to maintaining or extending the page with new features.
用户界面(UI)、业务逻辑和配置，或缺少其中一些元素，将它们混合在一起，而不考虑维护或扩展具有新功能的页面。
Although XUL is a bit more user-responsive than HTML, it won't do business logic for you.
尽管XUL比HTML 提供更多的用户响应能力，但是却不能为您实现业务逻辑。
A workflow is a series of steps that you want a user to follow, but according to some business logic.
工作流是您根据业务逻辑想要用户去遵循的一系列步骤。
However, it is highly possible that the user will make a mistake in entering the correct data. Therefore, the validation logic should immediately prompt the user with an appropriate message.
但是由于用户很有可能在输入数据时出错，因此，验证逻辑应能立即用恰当的消息提示用户。
This will cause too many generated activities within only one BPEL, which is hard for the user to read and understand the logic of the BPEL flow.
这将会在一个BPEL中生成多个活动，会让用户难以阅读和理解bpel流的逻辑。
This ability affects the user interface, business logic, and database; in addition, it is necessary to address issues regarding concurrency, data integrity, user transparency, and replication.
这种能力包括使用用户界面、业务逻辑和数据库的能力；此外，必须解决与并发、数据集成、用户透明度和复制相关的问题。
Fortunately, tight coupling isn't the only option when it comes to coding the User interface's validation logic.
幸运的是，紧密耦合不是我们在编写User接口的验证逻辑时的唯一选项。
应用推荐