Filter
Top Products
Navigation Guidelines
3
22 Genie Application Style Guide February 2001
In Example 3-9 the goal is to allow the user to navigate backward through the data
input wizard without losing data that was difficult to enter (since many devices map
the clear and back functions to the same key) and without corrupting the history stack.
This is accomplished by starting out with the
spawn action, which enables the use of
<throw> for backward navigation. In the <throw> statement for each card, the data
that has already been entered is sent back (so it is not lost) and caught in the card
where the user entered the name. This way, when navigating forward through the
wizard, the user need not re-enter data but can modify or remove it as necessary.
A similar effect (although not quite so efficient) may be achieved with the use of the
onenterbackward construction, although if data is no longer in the cache this will
involve further server hits.
A card containing:
<onevent type="onenterbackward">
<prev/>
</onevent>
Will immediately call the card that originally called it, without erasing any data.
Nokia Navigation Guidelines
■ Provide an action or link on every card.
Every card should define either a link or an action bound to a task of
<do type="accept">, <do type="options">, or <do type="prev">.
Generally, links should be used as a mechanism for forward navigation.
Example 3-10
Nokia 7110 Browser
<do type="accept" label="Edit">
<go href="edit.wml"/>
</do>
<do type="options" label="Find">
<go href="find.wml/>
</do>
In Example 3-10, the <do type="accept"> task calls edit.wml, and the
<do type="options"> task calls find.wml. On the Nokia 7110 browser, Edit and
Find are accessible from the Options softkey.
Last name: Smith
First name:
Andrew
City & State: San
Options
Back
Diego, CA
Zip:
Phone:
------ Contacts------- Options items:
Edit
Find
Email: