Configuring Siebel Open UI > Post-Upgrade Configuration Tasks > About Mobile-Specific Renderers Dependent on jQuery Mobile APIs >

Parsing for jQuery Mobile Usage

This topic describes various patterns of jQuery Mobile-specific use that might appear in your customized renderers. The descriptions in this topic are neither definitive nor exhaustive, and therefore a careful examination of your existing customizations coupled with comparisons with jQuery Mobile documentation is recommended.

For jQuery Mobile documentation, refer to the following site:

http://api.jquerymobile.com/

jQuery Mobile is a UI and theme library that works on top of jQuery. Therefore, everything customized through the former renderers, can likely be restructured to work using jQuery.

The following is a list of common areas in which you might observe problems as you parse through your customizations:

• API Usage
• Properties
• Widgets
• Events
• HTML Markup

Identification of the types of occurrences in your custom code and replacing them with code that works based on the jQuery and jQuery-UI libraries is essential for the transition of the customization to Siebel Innovation Pack 2014.

API Usage

jQuery Mobile exposes the $.mobile object which contains several APIs that have mobile specific functions. The base jQuery library does not contain this object, so any APIs that you may have used with this object are no longer available. Consequently, the code must be substituted with a jQuery equivalent. The following are examples of APIs to consider:

• buttonMarkup()
• jqmData()
• silentScroll()

Properties

jQuery Mobile exposes a single property on the $.mobile object called activePage, which is no longer available.

Widgets

jQuery Mobile extends the jQuery-UI widget set to provide $.mobile.widget objected, which provides mobile-specific widgets for usage in jQuery mobile environments. The following are examples of widgets to consider:

• Controlgroup
• Listview
• Loader
• Slider

Events

jQuery Mobile builds on native events to provide mobile-oriented events with which to bind. All such bindings will no longer run in Siebel Innovation Pack 2014. The following are examples of events to consider:

• mobileinit
• orientationchange
• scrollstart
• swipe
• tap
• v* (virtual keyboard events)

In Siebel Innovation Pack 2014 and later, the EventHelper object homogenizes events between devices and platforms. All bindings happen using the EventHelper APIs and the bindings are done on events that are homogenized. For more information about the EventHelper objects, see Architecture of Siebel Open UI.

HTML Markup

jQuery Mobile UI identifies certain HTML patterns, such as data attributes, and uses them to render the UI in specific ways. If your customized code contains the creation of HTML markup, you will need to parse for these types of occurrences and modify them as needed. The automatic styling and theme application that the markup generates will no longer occur. The following are examples of HTML markup to consider:

• data-role
• data-theme
• data-title
• data-icon
• data-inline