Configuring Siebel Open UI > Architecture of Siebel Open UI > About the Siebel Open UI Development Architecture >

Stack That Siebel Open UI Uses to Render Objects

Figure 12 describes the stack that Siebel Open UI uses to render objects. It uses the applet object as an example.

Figure 12. Stack That Siebel Open UI Uses to Render Objects

Explanation of Callouts

The stack that Siebel Open UI uses to render objects includes the following items:

1. Physical layout and styling. Allows you to use HTML to display content, JavaScript to customize logic, and cascading style sheets to customize layout and styling in the client. You can position or hide controls to achieve almost any layout requirement. This high level of customization is not possible with a high-interactivity client because high interactivity hard codes the physical layout.
2. Physical renderer. For more information, see About the Physical Renderer and About Plug-in Wrappers.
3. Presentation model. For more information, see About the Presentation Model.
4. Proxy objects. Includes object instances for the client proxy. Each of these instances represents an instance of a corresponding repository object that resides on the Siebel Server. Example objects include a view, applet, business object, or business component. A proxy object includes only enough logic to allow the client to use the same functionality that the server object uses, including the data and metadata that the server object requires. A proxy object exposes the interface for scripting in the client, but it does not allow you to significantly modify the physical user interface. You can customize only the information that flows from the Siebel Server to the client. You cannot customize how Siebel Open UI uses the metadata or data in the proxy object to render the physical user interface. In this example, proxy objects include the applet proxy and business component proxy that contain data and metadata from the Server Response property set. For more information, see Browser Script Compatibility.
5. Siebel Property Set. A hierarchy that Siebel Open UI uses to communicate between objects that reside on the Siebel Server and the proxies that reside in the client. The high-interactivity client uses the same format for this property set.
6. SWE run-time applet object. Exposes scripting interfaces that allow you to modify the applet so that it can control the business component or business service that this applet references. The applet that resides on the Siebel Server gets a request from the proxy applet instance that resides in the client. If necessary, it sends the request to a business component or business service. Siebel Open UI does not currently include a scripting interface that allows you to modify the property set that the applet sends to the client.
7. Applet metadata. The applet object in the Siebel Repository File (SRF) that contains information that Siebel Open UI uses to bind the user interface to the business component. Siebel Open UI maps this information through business component fields. This binding can include only a one-to-one mapping between one applet control and one business component field. Siebel Open UI does not allow more complex bindings. You can configure Siebel Open UI to get data through a presentation model in the client to develop functionality that is similar to the functionality that a more complex binding provides. For more information, see About Objects and Metadata.

Example Stack That Siebel Open UI Uses to Render Objects

This topic describes a typical example of how Siebel Open UI uses a presentation model and physical renderer for an applet that it displays in a view. Every object that Siebel Open UI renders uses this same object stack. You can customize objects in this stack to modify rendering and behavior. For example, you can customize the presentation model and physical renderers that implement view navigation to use tree navigation instead of the predefined nested tab navigation.

Figure 13 describes an example stack that Siebel Open UI uses to display a calendar applet.

Figure 13. Example Stack That Siebel Open UI Uses to Render Objects

Explanation of Callouts

Siebel Open UI uses the following items to display a calendar applet:

1. Jquery FullCalendar. The physical JavaScript control. A third-party typically provides this control.
2. jqfullcalrenderer.js. Binds the CallPresentationModel object that the calpmodel.js file contains with the third-party calendar control.
3. calpmodel.js. Describes the logical behavior for the calendar user interface that Siebel Open UI displays on top of a list applet that runs in high interactivity.
4. Activity proxies. Includes proxies for the Activity HI Calendar Applet and the Activity business component.