[Cover] [Previous Section] [Next Section] [Index]

Current chapter: Getting Started
Section 19 out of 26 total sections , Section 4 out of 5 sections in this chapter


Creating and testing a static HDML deck

Although your HDML services will probably be scripts or programs that dynamically generate HDML, static HDML decks are useful for providing help text, menus, and other elements of your service's interface that don't change often. Static HDML files are also useful for conducting a "simplest case" test of the UP.Simulator.

To create and test a simple static HDML deck:

  1. Use a text editor to create the HDML file.
  2. For example, create a file containing the following HDML deck:

    The HDML language provides a line-by-line description of this deck.

    Make sure you save the file as a text-only file and that you save it to a filename with an .hdml extension.


    IMPORTANT     Many Windows text editors, such as Notepad, automatically add a txt filename extension when you save a text-only file--even if you have already specified another filename extension, such as hdml. After you save your HDML file, make sure it only has the filename extension hdml, and not an extension like hdml.txt. If the extension is not correct, use Windows Explorer or a DOS window to change the filename extension after you have saved the file.

  3. Start the UP.Simulator.
  4. The procedure for starting the UP.Simulator is described in Using the UP.Simulator.

  5. In the Go field below the UP.Simulator menu bar, type the URL of the HDML file you created and press Enter (on your computer keyboard).
  6. For example, if you saved the file to c:\mydeck.hdml, type the following URL in the Go field:

The UP.Simulator should display the card as shown in Figure 3-5.

FIGURE  3-5.     An HDML deck with a display card

If the UP.Simulator does not display the card correctly, there may be an error in the HDML. See the following section for instructions on checking UP.Simulator status messages.


IMPORTANT     If you edit an HDML deck that you have previously loaded in the UP.Simulator, the UP.Simulator might not display the changes when you navigate to the deck. This is because the UP.Simulator caches decks; instead of reloading a deck each time you request it, the UP.Simulator attempts to retrieve the deck from its cache. To make sure the UP.Simulator reloads the latest version of a deck you have modified, navigate to the deck and then choose Reload from the UP.Simulator's Edit menu. Phone caching behavior is described in the UP.SDK Developer's Guide.


[Cover] [Previous Section] [Next Section] [Index]

Current chapter: Getting Started
Section 19 out of 26 total sections , Section 4 out of 5 sections in this chapter


Copyright © 1999, Unwired Planet, Inc. All rights reserved.