Implementing forms entry

Many applications require a "form" style of entry, in which the user enters data in a form containing associated data fields. For example, an address book application might allow the user to enter addresses in forms containing name and address fields. Some applications may allow the user to use forms that set related preferences.

Unwired Planet recommends that you implement an interface for these applications in the following manner:

• Create a choice card that provides a choice entry for each data field. Each choice entry should display the field name, followed by the field value (if any) enclosed in square brackets.

• Set the choice card's ACCEPT label to EDIT and SOFT1 label to SAVE.

• For each choice entry, specify a GOSUB task (activity) that allows the user to edit the field value displayed by the choice entry. Providing a separate activity to edit each choice entry allows the user to easily cancel editing.

• On return, the GOSUB task that allows the user to edit a choice entry should automatically advance the user to the next choice entry. It can do this by returning a variable that sets the IKEY option of the choice card. This is illustrated in the sample code below.

• Specify a task for the SOFT1 key to commit the values on the choice card

The following code provides a very simple implementation of this type of interface. Figure 8-9 depicts the interface.

<HDML VERSION=3.0>
    <CHOICE NAME=c1 IKEY=curItem>
        <ACTION TYPE=ACCEPT LABEL=Edit>
        <ACTION TYPE=SOFT1 TASK=GOSUB LABEL=Save
            DEST=newname.cgi?first=$first&last=$last>
        <CE TASK=GOSUB DEST=#first
            RECEIVE=first;curItem>First [$first]
        <CE TASK=GOSUB DEST=#last
            RECEIVE=last>Last [$last]
    </CHOICE>
    <--Activity: enter first name -->
    <ENTRY NAME=first KEY=fname>
        <ACTION TYPE=ACCEPT TASK=RETURN RETVALS=$fname;2>
        <WRAP>First:
    </ENTRY>
    <--Activity: enter last name -->
    <ENTRY NAME=last KEY=lname>
        <ACTION TYPE=ACCEPT TASK=RETURN RETVALS=$lname>
        <WRAP>Last:
    </ENTRY>
</HDML>

FIGURE  8-9.     Entry form implementation

Note that the activity that allows the user to edit the first choice entry sets the curItem variable (the variable used to set the default choice item) to 2. Thus, after the user finishes editing the first choice item, the second item will be the default. This saves users the trouble of scrolling to the second item after they have finished editing the first item.

---

Implementing lookup forms

To implement a "lookup" or search form, you use an interface similar to that described in the previous section. However, instead of changing the SOFT1 key label to Save, change it to Find.