Filter
Top Products
February 2001 Genie Application Style Guide 47
Displaying Text
8
Openwave Text-Display Guidelines
■ Use mobile originated prefetch to access the next card.
This shortens the time needed to retrieve the next set of information. While the user is
reading one card, the next card can be retrieved and put into the cache.
Example 8-3
<head>
<link href="page2.wml" rel="next"/>
</head>
<card id="page1">
<do type="accept" label="Page2">
<go href="page2.wml"/>
</do>
<p>
Page 1 of 2<br/>
...
</p>
</card>
Example 8-3 shows how to use prefetch to access the next card in a deck.
■ Do not use links on cards used to display results.
On cards that ask the user to confirm an action (for instance, deleting a contact from
an address book), that provide error explanations, or that display other results, use the
<do type="accept"> and <do type="options"> labels instead of links. Map
the safest or most common response to the
<do type="accept"> label.
■ Incorporate Done softkeys when possible.
If no secondary functions on the displayed text are needed, add a Done softkey that
returns the user to the next highest level within the application. This is often used in
conjunction with activities so that the user can pop out of the current activity and
return to the activity that spawned it.