A WML task
element that specifies an action to be performed by the browser,
rather than something to be displayed. For example, the action of
changing to a new card is represented by a
<go> task element, and the action of
returning to the previous card visited is represented by a
task element. Task elements
encapsulate all the information required to perform the action.
Tasks are used in many places in WML. Events (discussed later in this chapter) are tied closely with tasks, and many of the user interface elements (see Chapter 4) use tasks to perform actions.
To see how tasks are used in context, consider the element
<do>, which represents some sort of control
that the user can activate, such as a softkey, a menu item on a cell
phone, or maybe even an onscreen button if the device has a
isn’t itself a task element. Rather, it contains a task
subelement that specifies the action to perform when the user
activates the control.
<do> element that, on activation, simply
assigns the value
wibble to the variable
test can be written as:
<do type="accept"> <refresh> <setvar name="test" value="wibble"/> </refresh> </do>
To have the same
<do> element instead send ...