Every application on the Palm VII needs two icons -- a large icon for use in the application launcherís Icon view, and a small one for use in List view. You can create your own icons, or you can let QABuilder provide default generic icons: a small and large solid black diamond with the familiar "over the air" lines on the right side.

Figures D-6 through D-8
The small icons can have a similar theme to the large icons or, if you want, you can just use the default.

Notes for HTML coders

Most of the commands and controls in the HTML 3.2 specification work on the Palm VII. However, a few common codes donít work: vertical alignment (the VALIGN attribute to various tags), nested tables, subscripts, superscripts, small text, the LINK tag, the APPLET tag, and the ISINDEX tag.

Only four colors are supported: Black="#000000", Silver="#C0C0C0C0" (light gray), Gray="#808080" (dark gray) and White="#FFFFFF". If you enter in any other color number, it will be "rounded off" to the closest of these four colors, often with unfortunate results. Graphics canít be153x144 pixels, and sequential .gif animation is not supported (thank goodness).

The Body tag only supports BGCOLOR and TEXT tags. There are also limitations on the types of fonts -- Clipper does a decent job of differentiating among the various subtle font variations allowed in the 3.2 HTML specification (such as <SAMP>, <STRONG> and <EM>), but there are only so many different fonts that will work with so few pixels. Therefore, for example, <SAMP>, <CODE> and <KBD> are all translated into TD Monospace. And <FONT> attributes like "Arial" are ignored.

A few HTML tricks that arenít actually in the 3.2 specification, but have become widespread, also donít work on the Palm VII: Frames, any form of image maps, and any kind of scripting (like javascript).

Cool New Tags

On the other hand, the Palm VII accommodates a number of new tags that, while theyíre not part of the standard HTML vocabulary, take advantage of the Palm VIIís special capabilities:

The "PalmComputingPlatform" metatag (with a content of "TRUE") tells the Palm VII server that you have a "Palm-friendly" site. The server will allow graphics, and generally treat your content with less suspicion, if your PQA includes this tag.

The "HistoryListText" metatag lets you specify how pages will appear in the History List on the Palm VII, the shown in Chapter 16. You can specify any text. The special strings &date and &time indicate that you want the date or time inserted into the History List text.

The "PalmLauncherRevision" metatag lets you set the revision date on your PQA as it appears in the version list of the the Palm application launcher. As any developer knows, adding a revision number to a program can save a great deal of confusion later.

The "LocalIcon" metatag tells the QABuilder program to include files (for example, graphics) in the PQA that arenít actually used by the PQA, but instead are elsewhere on the Palm VII. The server can reference these files much more cheaply because they are already on the device.

Use caution with both of the special strings. The zip code is based on the location of the radio base station, but a particular Palm VII might use base stations across several zip codes. Furthermore, the Palm VIIís unique ID can be "spoofed" using a web browser, which contacts your server directly without going through the Palm VII servers.

<A HREF="palm:addr.appl">Address Book</A>

... then "Address Book" will appear in your PQA as link. When the Palm VII user taps it, the Palm VII launches the Address Book! All the standard applications on the Palm VII have four-character abbreviations. You can look them up either in the table below, in the Palm VII Content Style guide, or in the Launcher sample PQA included on this bookís CD, which uses these tags to create a launching pad on a single PQA screen.

Figure D-9
The Launcher PQA demonstrates that you can call regular applications from your PQA.


Application Called