The term UP.Phone refers to all UP.Link-enabled devices, including wireless phones, Personal Digital Assistants (PDAs), and two-way pagers. The term refers to both the hardware and the UP.BrowserTM software installed on it.
For the purposes of this documentation, all illustrations and examples refer to a generic UP.Phone with the following characteristics:
A 4 x 20 character display. Note that the UP.Browser always reserves one line for function key labels and status.
ACCEPT, PREV, and OPTIONS function keys. The actual labels and locations of these keys vary from one device to another.
IMPORTANT
Keep in mind that the display area and key arrangements on real UP.Phones vary considerably. Some UP.Phones reverse the location of the ACCEPT and OPTIONS keys relative to the illustrations in this documentation. Others have fewer or no function keys and use different mechanisms for implementing the ACCEPT, PREV, and OPTIONS actions, such as a jog shuttle or other user-interface gestures.
This manual uses different fonts to represent the information you must enter:
Text that appears like this identifies command names, path names, URLs, and specific text that you must enter.
Text that appears like this identifies placeholders or variables that you should replace with values appropriate to your environment.
Text that appears like this identifies default WML attribute values.
Omitted code is indicated with ellipses. For example, the ellipses in the following example indicate that additional code exists in this WML card definition:
1 <wml>Line numbers that appear in some code examples are for reference only and are not part of the actual code.