user interface definitions using PACE

Designers can create simple, stylish campaigns that can be displayed on the handset screensaver, home screen, or drawn on top of any running application.

The visual components of campaigns are drawn using either Flash Lite® or SVG. Campaigns ‘targets’ include the handset screensaver or home screen, alternatively, campaigns can be drawn as floating ‘tooltips’ over the top of a running application or as popup (modal) dialogs.

UI View Types

PACE supports five related types of UI elements:

  1. Screensaver
  2. Home Screen view
  3. Focused view
  4. Overlay view
  5. Popup view

screensaver

The client implements a screensaver control that can draw a UI using our SVG engine or can host the native Flash Lite® Player.

Items are rendered in display carousel order.

home-screen

Home Screen views are drawn in display carousel order.

They are synchronised with the current screensaver view to provide a contextual linkage for the user to act upon.

Focused View

Focused Views are the normal way of interacting with campaigns. They present a set of actions associated with a campaign and are activated by either a single key press from the home-screen, or a tap on the campaign UI.

Overlay View

An Overlay View is the ‘Swiss Army Knife’ of PACE campaigns because it can be displayed over any application and bound to multiple application UIDs.

screensaver

The client implements a native screensaver control that can draw a UI using our SVG engine or can host the native Flash Lite® Player.

Campaigns are rendered in display carousel order during.

To conserve power, the client may:

  • Modify the handset backlight illumination level.
  • Disable individual screensaver campaigns.
  • Disable the screensaver entirely.

Where power is unlimited (i.e. on charger) the screensaver may stay on for an additional - possibly unlimited - time.

home screen

Campaigns in the display carousel typically have a screensaver view and an associated home screen view.

The client displays the campaigns in order, changing the campaign when each has been

Home Screen campaigns on S60 3rd Edition handsets are drawn as overlays on the home-screen. On S60 5th Edition handsets and later are rendered into a home-screen plugin.

On S60 3rd Edition handsets, campaign views are limited to 10 seconds duration and are dismissed immediately on any user interaction with the handset.

Focused View

Focused Views are the normal way of interacting with campaigns. They present a set of actions associated with a campaign and are activated by either a key press, or a tap on the campaign UI.

Focused Views are drawn onto windows that float above the app from which they were launched - in this case the home screen. Because the PACE client runs in the background, the display of these views is near instantaneous.

UI templates can be used to obtain a standard look and feel. This is not mandated by the client but makes standard campaigns very easy to create.

Overlay Views

An Overlay View is the ‘Swiss Army Knife’ of PACE campaigns because it can be displayed over any application.

Overlay views are tightly bound to the client rules engine. The campaign specifies which application UIDs the overlay should be drawn over. When a nominated application gets focus, campaign rules are evaluated. If the resulting display priority is greater than zero, the UI is immediately rendered.

Since overlays can be associated with multiple app UIDs, the client can intelligently pause and resume animation on focus change — a killer feature for rich mobile advertisements.

drawing a ui with PACE

For the screensaver, the client uses either the handset [an error occurred while processing this directive] application or its own SVG engine. The PACE SVG engine is always used to render home-screen, popup and overlay campaigns.

PACE SVG support includes a subset of elements from the [an error occurred while processing this directive] specification including [an error occurred while processing this directive] animations.

The choice of Flash Lite® or SVG for screensaver campaigns is dictated by whether the campaign is dynamic, in which case, SVG should be used; or where existing assets are to be used, in which case Flash® might be more appropriate.

view documents

A campaign view document is responsible for event handling as well as controlling:

· a focused ui composite view created from multiple SVT templates · PACE active campaign engine ·

The PACE event model binds actions to key, touch and timer events. Focused or popup views can use these events to create interactive applications through manipulation of the SVG DOM

Views are also responsible for performing actions in response to user events. For example, a view may launch the web browser in response to user input.

ui compositing

· ui compositing from re-usable SVT templates · PACE active campaign engine ·

Because a view can specify that an image be made up of multiple documents, composite UIs can dynamically be created from reusable XML components, e.g.:

Compositing occurs at runtime in a just-in-time basis.

themed common ui components

The client comes pre-installed with a set of UI templates for home screen, focused and other views.

For most campaigns, custom screensaver and application overlay views are created. For consistency, view templates are used for both the home screen and focused screen.

Templates simplify the ingestion of third-party ad content because in most cases, templates eliminate the need for a custom UI. Where non-standard behaviour or look-and-feel is required, custom home and focused screen view components can be created on an as-need basis.

technical benefits

The PACE rules engine works to prioritise which campaigns are displayed to the user. A simple system of display priorities coupled with event subscriptions makes it easy to build either static or active campaigns. The multi-layered approach employed by the rules engine ensures that the system is very efficient. For example, the overhead of having a campaign. that activates only when the handset is roaming is tiny.

Top of Page.