About Mobile-Specific Renderers Independent of jQuery Mobile APIs

This topic describes how to change existing customizations, based on Siebel Open UI Mobile Renderers. It contains the following information:

"About Restructuring Mobile Classes"
"About Class Equivalency"
"Adapting Inheritance Hierarchies"

About Restructuring Mobile Classes

Beginning in Siebel Innovation Pack 2014, all mobile renderer classes have been deprecated and any extensions from those classes will no longer work in customized deployments. As a part of the Responsive Web Design (RWD) streamlining, the jQuery Mobile plug-in library that was in Siebel Innovation Pack 2013, is no longer available.

The decision manager in the SiebelAppFacade namespace has a utility call to distinguish between touch and non-touch devices which can be used for programming control. However, client classes are not coded entirely for one type of device. Specific handlers maybe be present for one type of device which differs in functionality. Also, touch capability is no longer restricted only to mobile devices. Any browser that answers true to touch capability, will work in the touch mode in Siebel Open UI.

As of Siebel Innovation Pack 2014, the following set of classes are no longer used:

JQMFormRenderer
JQMScrollContainer
JQMGridRenderer
JQMTabletGridRenderer
JQMListRenderer
JQMTabletListRenderer
JQMCallListRenderer
JQMNavBaseRenderer
JQMLaunchPadNavRenderer
JQMNavBarRenderer
JQMPDQPhyRenderer
JQMToolBarRenderer
JQMVisDropDownPhyRenderer

All of the functionality in the above mobile-specific renderers have been either deprecated or streamlined into singular renderer that work for touch and non-touch devices. Moving forward, if you have existing customizations that extend any of these renderers, you will need to revisit the extension logic, and make modification so that they extend from the RWD unified equivalents.

Table C-1 lists renderers have had extension changes from the existing JQM-specific renderers to the unified renderers in Siebel Innovation Pack 2014. If you had customized code that extends from these renderers, they should largely remain unaffected, but it is recommended that you test your customizations thoroughly in Siebel Innovation Pack 2014 before deployment.

Table C-1 Extension Changes in Renderers

Class	Renderer Extension in Siebel Innovation Pack 2013 and Earlier	Renderer Extension in Siebel Innovation Pack 2014 and Later
TileLayoutPR	JQMScrollContainer	PhysicalRenderer
UMFTileRenderer	TilescrollContainer	TileLayoutPR
SignViewPhyRenderer	JQMFormRenderer	PhysicalRenderer

About Class Equivalency

Table C-2 describes the equivalent classes that you can use when changing the extension hierarchy for your customizations. This is not an absolute list. It is recommended that each case be examined carefully to determine equivalencies, however Table C-2 can be used as a guideline for refactoring customized code.

Table C-2 Extension Equivalencies

Extension in Siebel Innovation Pack 2013 and Earlier	Extension in Siebel Innovation Pack 2014 and Later
JQMFormRenderer	PhysicalRenderer
JQMScrollContainer	PhysicalRenderer
JQMGridRenderer	JQGridRenderer
JQMTabletGridRendeer	JQGridRenderer
JQMListRenderer	JQGridRenderer
JQMTabletListRenderer	JQGridRenderer
JQMCallListRenderer	JQGridRenderer
TileLayoutPR	TileLayoutPR
Tilescrollcontainer	Tilescrollcontainer
UMFTileRenderer	UMFTileRenderer
SignViewPhyRenderer	SignViewPhyRenderer
JQMNavBaseRenderer	AccNavigationPhyRenderer
JQMLaunchpadNavRenderer	AccNavigationPhyRenderer
JQMNavBarRenderer	AccNavigationPhyRenderer
JQMPDQPhyRenderer	PDQPhyRenderer
JQMToolbarRendeer	ToolbarRenderer
JQMVisDropdownPhyRenderer	VisDropdownPhyRenderer

Adapting Inheritance Hierarchies

This section includes information about changing existing customized code that was meant for mobile devices which did not have any references or calls to JQM-specific properties or methods. All such code classes should integrate into the new unified renderers with just the extension change.

To modify customized code to adapt to new unified renderers

Find and change class definitions:
1. Determine if you have the following code in the beginning of your class definitions:
```
if (typeof (SiebelAppFacade.CustomMobileAppletXRenderer) === "undefined") {
SiebelJS.Namespace('SiebelAppFacade.CustomMobileAppletXRenderer');

//Module with its dependencies
define("siebel/custom/custommobileappletxrenderer", ["siebel/jqmformrenderer"], function () {
SiebelAppFacade.CustomMobileAppletXRenderer = (function () {

function CustomMobileAppletXRenderer(pm) {
SiebelAppFacade.CustomMobileAppletXRenderer.superclass.constructor.call(this, pm);
}

SiebelJS.Extend(CustomMobileAppletXRenderer, SiebelAppFacade.JQMFormRenderer);
.
.
.
```
2. Replace the code found in Step a with the following code:
```
if (typeof (SiebelAppFacade.CustomAppletXRenderer) === "undefined") {
SiebelJS.Namespace('SiebelAppFacade.CustomAppletXRenderer');

//Module with its dependencies
define("siebel/custom/customappletxrenderer", ["siebel/phyrenderer"], function () {
SiebelAppFacade.CustomAppletXRenderer = (function () {

function CustomAppletXRenderer(pm) {
SiebelAppFacade.CustomAppletXRenderer.superclass.constructor.call(this, pm);
}

SiebelJS.Extend(CustomAppletXRenderer, SiebelAppFacade.PhysicalRenderer);
.
.
.
```
The following definition changes are among the most important:
- CustomMobileAppletXRenderer to CustomAppletXRenderer
- All renderers that are customized in Siebel Innovation Pack 2014 are unified renderers. They will work for all devices. This means that there will only be a singular renderer for a given applet for multiple devices. The nomenclature change is to signify that no mobile specificity exists in renderer customization.
- ["siebel/jqmformrenderer"] to ["siebel/phyrenderer"]
  
  In releases prior to Siebel Innovation Pack 2014, the dependency definition section defined a jQuery Mobile oriented module or file in the call to define. These modules and files are no longer used and should be changed to modules and files in which the new extension classes are hosted.
- SiebelAppFacade.JQMFormRenderer to SiebelAppFacade.PhysicalRenderer
  
  The extension hierarchy change as presented to the SiebelJS.Extend method is required because the older classes are no longer available or defined in the SiebelAppFacade namespace. Use the Table C-2 as a guide to apply your modifications.
Determine if you have any of the following references:
```
CustomMobileAppletXRenderer
```
Replace all of the references that you found in Step 2 with the following definition:
```
CustomAppletXRenderer
```
Determine if you have any of the following references:
```
["siebel/jqmformrenderer"]
```
Replace all of the references that you found in Step 4 with the following definition:
```
["siebel/phyrenderer"]
```
Determine if you have any of the following references:
```
SiebelAppFacade.JQMFormRenderer
```
Replace all of the references that you found in Step 6 with the following definition:
```
SiebelAppFacade.PhysicalRenderer
```