Bookshelf Home | Contents | Index | PDF |
Configuring Siebel Open UI > Customizing Siebel Open UI > Doing General Customization Tasks > Using the Base Physical Renderer Class With Nonapplet ObjectsThis topic describes how to use the Base Physical Renderer class with nonapplet objects that you customize. It includes the following topics:
The BasePhysicalRenderer class simplifies calls that Siebel Open UI makes to the AttachPMBinding method for nonapplet objects. You can configure Siebel Open UI to use the BasePhysicalRenderer class to identify the physical renderer, call AttachPMBinding, and specify the configuration for the scope of a nonapplet object. You can then use a custom physical renderer to call AttachPMBinding with the appropriate handler. Siebel Open UI uses the PhysicalRenderer class to interface with and to render applets. Starting with Siebel CRM versions 8.1.1.11 and 8.2.2.4, it uses the BasePhysicalRenderer class to render nonapplet objects. It uses this class to separate the interface to the physical renderer from the physical renderer. Siebel Open UI uses the BasePhysicalRenderer class only with nonapplet objects, such as the toolbar or predefined query bar. If your deployment includes nonapplet custom rendering, and if it uses Siebel CRM version 8.1.1.10, 8.2.2.3 or earlier, then it is strongly recommended, but not required, that you modify your configuration so that it uses the BasePhysicalRenderer class to render your custom, nonapplet objects. If your deployment uses the PhysicalRenderer class to render nonapplet objects, then this class will provide access to applet functionality and properties that it does not require to do the rendering, which could degrade performance or result in rendering problems. Siebel Open UI defines the BasePhysicalRenderer class in the basephyrenderer.js file. Hierarchy That the Base Physical Renderer Class UsesFigure 27 illustrates the hierarchy that the BasePhysicalRenderer class uses for nonmobile applications. The member variable is a variable that is associated with the class. All methods can access this member variable. Figure 28 illustrates the hierarchy that the BasePhysicalRenderer class uses for mobile applications. Using Methods with the Base Physical Renderer ClassTable 6 describes how to use methods with the BasePhysicalRenderer class.
Declaring the AttachPMBinding Method When Using the Base Physical Renderer ClassIf you configure Siebel Open UI to use the BasePhysicalRenderer class, then you must declare the AttachPMBinding method. To declare the AttachPMBinding method when using the Base Physical Renderer class
Sending an Arbitrary ScopeAn arbitrary scope is any scope other than the scope that calls the handler. You can configure Siebel Open UI to send to AttachPMBinding any scope that is available in the physical renderer. You can use the BasePhysicalRenderer class to send an arbitrary scope that identifies the handler method that Siebel Open UI must use.
Accessing Proxy ObjectsIf you must write code that accesses a proxy object, then it is strongly recommended that you access this proxy object through a physical renderer. The physical renderer typically exposes the interfaces that allow access to operations on the proxy object. The example in this topic accesses a proxy object for an active control.
It is recommended that you do not write code that directly accesses a proxy object from a physical renderer. In the following example, Siebel Open UI might remove the GetProxy method from the presentation model, and any code that references GetProxy might fail. It is recommended that you do not use the following code: this.GetProxy().SetActiveControl(control); Modifying Nonapplet Configurations for Siebel CRM Version 8.1.1.10, 8.2.2.3, or EarlierSiebel Open UI removed the scope argument for calls that it makes to the AttachPMBinding method with nonapplet objects, starting with Siebel CRM versions 8.1.1.11 and 8.2.2.4. You can modify your custom code to use this new configuration. To modify nonapplet configurations for Siebel CRM versions 8.1.1.10, 8.2.2.3, or earlier
|
Configuring Siebel Open UI | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |