The basic idea behind the 'generic browser' is to identify a
subset of WML that both the browsers used above interpret in a more
or less usable way.
Guidelines for the Generic Browser
The generic browser is an attempt at defining the lowest common
denominator features of WML that work acceptably well on the two
main browsers.
Entering Data on the Generic Browser
The 7110 requires the use of links. On the other hand, it's
better to use a <do> element on the UP.Browser, as a link
would introduce two extra steps. Using <do> elements on the
Nokia 7110 is not acceptable - but there's nothing to prevent
you from using both a link and a <do> element in the same
card, as shown in the example below (a modified version of the
example you saw earlier):
<card id="card1" title="mycard">
<do type="accept" label="Send">
<go href="receive.asp"
/>
</do>
<p>
name please:
<input type="text"
name="username" value="" />
<a href="receive.asp"
title="Send">Submit data</a>
</p>
</card>
In the UP.Browser, users will be able to navigate with the
Accept button after they have acknowledged the text they wrote in
the form. As far as the Nokia is concerned, users will get a link
after the input form - business as usual for them.
Menu Navigation on the Generic Browser
No matter how useful the shortcuts supported by the
option-onpick pair in the UP.Browser, the lack of support for this
feature on the 7110 means that you should implement menu navigation
with a list of links. The list of links works well enough on the
UP.Browser, after all.
Email TopXML