Filter
Top Products
Navigation Guidelines
3
24 Genie Application Style Guide February 2001
Mitsubishi Trium Navigation Guidelines
■ Provide backward navigation for each card.
Provide an intuitive label, for example Done or Back, to allow the user to use the right
softkey for backward navigation. The browser will automatically provide a label of
Back assigned to an action of
<prev/> - if the term “Back” is not suitable, it may be
overridden such
Example 3-13
<do type="prev" label="Done">
<prev/>
</do>
Example 3-13 provides an alternative labelling for the right hand key.
■ Do not rely on being able to override the default backward navigation
Trium browsers vary in terms of their handling of the <do type="prev">
construction. One type will only change the right hand key behaviour if the action is
still
<prev/>; the other type allows <noop/> and <go/> constructions to be used
also. For safety, handle alternate back navigation using a mechanism similar to
Example 3-12 above.
■ Do not define a <do type="accept"> or <do type="options"> task when a
<select> element, <input> element, <a> or <anchor> is used.
A <do type="accept"> or <do type="options"> task on some versions of the
browser, this will cause the softkey to display the Card label preventing easy
navigation to the next card or to the input and select items. Instead, provide a link
allowing the user to navigate to the next card.
■ Limit the number of softkey actions to one.
The browser displays the defined label on the left softkey. This simplifies tasks
because the softkey label is accessible with one keypress. When more than one task is
defined, the left softkey label may become Card and displays the defined labels. In
this case, build a card with the desired tasks and label the softkey Menu. This provides
room to display more descriptive labels for each action and enables the use of key
accelerators, on some handsets.
■ Do not underline text (<u> mark-up tag), because the user may think that the
item is a link.
Not all Trium browsers will do underlining if the tag is used, but if it does, there is
clear possibility for confusion.
■ Avoid using WML Scripts.
Since the user can disable WML Scripts, do not rely on them being activated. You can
check to see if the user has disabled scripts by checking the
HTTP_ACCEPT header –
however the user could still turn off scripts while a script is in the cache of the phone.