You can change the theme policy used by the aggregator.
Locale-specific theme support
The XDIME
aggregator uses several locale-specific theme policies named wp_styles_locale.mthm,
where locale is the locale suffix supported by
the theme policy, and wp_smt_style_locale.mthm,
which is smartphone-specific. The default theme policies provide style
rules (for example, wpsPlaceBar, wpsPortletTitle, and wpsPageBar)
that define the style for parts of the user interface. The theme policy
installed with IBM® Mobile Portal Accelerator can
be replaced or modified. Use the Mobile Portal Toolkit to
create and modify theme policies. If you replace the default theme
policies or delete style rules from the wp_styles policies, you must
update the XDIME aggregator JSPs that reference the old style rules.
Portlets
can inherit the theme policy referenced on the XDIME aggregator's
main canvas tag and use style rules defined in that theme policy. If
you replace the XDIME aggregator's theme policy or modify or delete
style rules in the default wp_styles theme policies, you may affect
the XDIME portlets that inherited the XDIME aggregator's theme policy
including the XDIME portlets provided with
Mobile Portal Accelerator.
Portlets can also define their own theme policy, but this is not recommended
if you want all portlets to use a consistent set of style rules.
Note: A
theme policy is different from WebSphere® Portal themes,
which are themes that define how an aggregator displays content on
a page. A theme policy is made up of a set of style rules that define
fonts, colors, backgrounds, and borders and can be device- and locale-dependent.
Important: Limit the number of style rules you create when modifying
or creating a theme policy. All of the style rules in a theme are
sent to a device. If there are too many style rules defined in a theme,
it can overflow the device's input buffer.
Theme support for different locales
WebSphere Portal can
use a different style sheet for each locale. The XDIME aggregator
uses a theme policy in place of a style sheet and provides a version
of the wp_styles theme policy for each supported locale. Each version
of the wp_styles theme policy is named
wp_styles_locale.mthm (where
locale is
the locale suffix supported by the policy). The XDIME aggregator uses
the
mwp:vpMapper JSP tag library to select the theme
policy for the requested locale. If you modify the XDIME aggregator's
wp_styles theme policies, you must update the version for each locale
that you plan to support. If you want to use your own theme policies
instead of the wp_styles theme policies, use the
mwp:vpMapper JSP
tag library to select the appropriate theme policy. Use the following
naming convention for your theme policy:
theme-policy-name_locale.mthm
where:
- theme-policy-name is your new policy name
- locale is the locale supported by the policy
Note: If a device requests a locale that is not supported by Mobile Portal Accelerator,
the default locale used by the XDIME aggregator is English (en).
The locale used by content nodes such as portlets are documented in
the WebSphere Portal product documentation.
