Configuring Siebel Open UI > Overview of Siebel Open UI > Differences Between High Interactivity and Siebel Open UI >

Summary of Differences Between High Interactivity and Siebel Open UI

Siebel Open UI and high interactivity implement the physical user interface differently:

• Siebel Open UI. The SWE renderer that Siebel Open UI uses structures the physical user interface through HTML div elements instead of the HTML frames that high interactivity uses. This configuration allows you to use cascading style sheets to do the layout for these div elements instead of hard coding the position of HTML frames. It simplifies reconfiguring the HTML for different user interface themes.
• High interactivity. Uses a hierarchy of HTML frames. This hierarchy makes it difficult to reconfigure the rendered HTML to support different user interface themes.

Siebel Open UI uses the same browser proxy configuration that high interactivity uses. This structure includes the object type hierarchy for applications, views, applets, business objects, and business components. It implements each of these objects in JavaScript. These JavaScript objects render HTML and handle user interaction through DOM events. Siebel Open UI uses no ActiveX controls to render the physical user interface.

The applet object that resides in the proxy contains all the same metadata and data that it requires to render the physical user interface that high interactivity uses. For more information, see About Objects and Metadata.

In some situations, Siebel Open UI gets more data locally from the proxy or the client, or it creates metadata in the client. A presentation model specifies how to display this local data. It also provides an interface to the proxy.

Siebel Open UI uses a physical renderer to implement the binding that exists between a predefined JavaScript control and the Siebel Object Model in the proxy.

To create the HTML DOM structure for a JavaScript control, the renderer uses the metadata and data that Siebel Open UI populates into the client proxy. The renderer uses methods that reside in the presentation model to access this metadata.

Comparison of Customization Capabilities Between High Interactivity and Siebel Open UI

High interactivity and Siebel Open UI share the following customization capabilities:

• Metadata configuration for all user interface objects resides in the Siebel Repository.
• Layout configuration of user interface objects resides in SWE templates.
• Negligible server scripting capabilities exist to render custom configurations.

Table 4 summarizes some of the significant customization differences that exist between high interactivity and Siebel Open UI. For a more detailed comparison, see Article ID 1499842.1 on My Oracle Support.

Browser scripting for proxy objects resides in the client. For more information, see Browser Script Compatibility.