
Web Browser for the 4625SW IP Telephone
160 4600 Series IP Telephones Application Programmer Interface (API) Guide
All <do> tags with the type attribute X* or x* (experimental) and any vendor-specific tags are
treated as unknown types.Therefore, shadow rules apply where the last attribute overwrites the
previous attribute when a <do> tag with the same type and name. In this case, a <do> tag with
the same type and name at the card level, shadows or renders a <do> tag inactive at the deck
level. A <do> tag with the <noop> tag embedded is not rendered on the Web browser. An
unspecified name attribute for the <do> tag defaults to the <type> attribute value. If a <do> tag
is defined for the <card> tag and one already exists for the <wml> tag, the <card> tag overwrites
that of the <wml> tag, assuming they are the same type and name.
If no <do> tags were specified, no softkeys display:
If one <do> tag was specified, these softkeys display:
If multiple <do> tags are specified, display them as follows:
Page 1 softkeys:
Page 2 softkeys:
Note: If more than one page of softkey labels are specified, pressing the MORE softkey
automatically presents the user with the next page of labels. If the last page
displays and the user presses the MORE softkey, the first page of labels is then
displayed. As implied in the examples, the Softkey buttons are labeled in
sequential order of the <do> tags.
To render JPEG or WBMP images in the softkey area, embed <img> tags in the <do> tag. For
example, the syntax might be:
<do type="example-accept" label="SK1">
<go href="example-#card2"/>
<img src="x.jpg"/>
</do>
Note: When an image tag existing inside a <do> tag results in a failed attempt to
retrieve the image through http, the softkey label displays the do tag label.
1st DO
1st DO 2nd DO 3rd DO MORE
1st DO 2nd DO 3rd DO MORE
4th DO 5th DO Etc. MORE
Komentarze do niniejszej Instrukcji