Application Object Model
General Interface defines screens and controls at a higher level of abstraction than that of the HTML Document Object Model. This model, called the Application Object Model (AOM), maps to the native browser's DOM. This enables General Interface applications to run in any browser where General Interface's AOM is implemented. Figure 2.3 shows a designer view of application canvas for a sample application in TIBCO General Interface, and Figure 2.4 shows the XML definition of the same appCanvas.
Figure 2.3 Application canvas in Design view.
Figure 2.4 Application Canvas in XML view.
As you can see, every element's properties are defined in XML, and it is associated with a JavaScript class. As the General Interface controller loads the components, it creates an instance of the associated JavaScript class to handle events and behaviors for the component. This provides a great degree of encapsulation for classes and widgets. It is possible to make use of the familiar concepts of object-oriented programming to extend built-in widgets (or create new ones). As you build your canvas in GI Builder, it builds this file, and you can view a user-friendly representation of this file in the Component Hierarchy quadrant in the GI Builder.