1-1-3 TIBCO General Interface GI架构

The View refers to how the object instance is actually displayed on the client machine. A good way to envision a view is to think of object look-and-feel. Figure 3 shows several different views that the Tab object can produce:

View涉及对象实例怎样实际显示到客户端的机制。一个好的关于视图的期望是只考虑对象的感官(look-and-feel)。 Figure3显示了几个Tab对象能够产生的视图。

The easiest aspect of MVC to understand is the view. The view is what end users see when they use the application. The three Tab object instances shown in Figure 4, for example, have a consistent view that adheres to the visual design for the application.

Mvc最容易理解的方面是view，view就是最终用户使用应用程序的时候看到的，树Tab对象实例在Figure4中显示，如例子，tab一块组成了应用程序的可视部分。

With the view element now defined, it’s easier to explain the model portion of the MVC architecture. The model element allows the given Tab object to keep an index of properties that uniquely define its state in memory (see Table 1). The model is unaffected by how the tab visually displays its state. Instead, it maintains a single Boolean property, active, that is set to true or false.

用当前定义的view元素，可以很容易理解mvc架构的model部分。model元素允许给Tab对象保持一个在内存中定义的唯一的索引属性，model不影响tab是如何显示他的状态。而model只是维护一个单独的Boolean属性（活动），可以设置成true或false；

To manage such a broad array of functionality, General Interface employs a multi-tiered approach to object design. Essentially, any available function can be categorized into four distinct layers, as illustrated in Figure 5. These include: