Nokia COMMUNICATOR 9200 Developer's Manual
WAP Service DeveloperâÂÂs Guide for Nokia 9200 Communicator Series FORUM NOKIA Version 1.0; March 03, 2003 Browsing
Forum.Nokia.com Contents 1 Introduc tion ................................................................................................................... ...................................... 5 2 Introduction to the User Int erface of Nokia 9 200 Comm unicator Se r ies ........................................... 6 2.1 WAP Browser Tech nical Features ................................................................................................. .............6 2.2 Keypad ................................................................................................................................................................6 2.3 Display - Detailed Description ................................................................................................. ....................6 2.3.1 Overview ....................................................................................................................... ....................6 2.3.2 Display co lormap ............................................................................................................... .............7 2.4 WAP Browser Display ............................................................................................................ .........................7 2.4.1 Card view...........................................................................................................................................7 2.4.2 Bookmarks view ................................................................................................................. ............8 3 Nokia 9210 Communicator User Interface Elements of W ML ................................................................. 9 3.1 Browser Di splay ...............................................................................................................................................9 3.2 Formatting Elemen ts ............................................................................................................ ...................... 10 3.2.1 Text form atting ................................................................................................................ ............ 10 3.2.2 Paragraph ...................................................................................................................... ................ 11 3.2.3 Line Break ..................................................................................................................... ................. 11 3.2.4 Fieldset....................................................................................................................... ..................... 11 3.3 Tables ............................................................................................................................................................... 11 3.4 Images, Links, and Ti mers ...................................................................................................... ................... 13 3.4.1 Img â Im ages ................................................................................................................... ............. 13 3.4.2 Anchors ........................................................................................................................ ................... 14 3.4.3 Timer .......................................................................................................................... ..................... 15 3.5 Dynamic Buttons ................................................................................................................ .......................... 15 3.5.1 Do ele ments .................................................................................................................... .............. 15 3.5.2 Prev type do el ements .......................................................................................................... ..... 17 3.6 WML Input Processing ........................................................................................................... ..................... 18 3.6.1 Input el ements ................................................................................................................. ............ 18 3.6.2 Selection lists ................................................................................................................ ................ 19 3.7 Titles an d Labe ls .............................................................................................................. ............................. 21 3.7.1 Titles ......................................................................................................................... ....................... 21 3.7.2 Labels ......................................................................................................................... ..................... 21 3.8 Limitati ons .................................................................................................................... ................................. 21 3.8.1 WML character sets. ............................................................................................................ ........ 21 3.8.2 Features not support ed in WML 1.1 ...................................................................................... 21 4 General Usability Issues â Guidelines for De sign............................................................................... ...... 22 4.1 WML History Navigation ......................................................................................................... ................... 22 WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 1
Forum.Nokia.com 4.2 Validate Yo ur WML .............................................................................................................. ......................... 22 4.3 Site Orga nization .............................................................................................................. ........................... 22 4.3.1 Avoid âÂÂdoorma tâ pages.......................................................................................................... ..... 22 4.3.2 Automatically Detect the Browser ......................................................................................... 22 4.3.3 Optimise for Size.............................................................................................................. ............ 22 4.3.4 Choose Descriptive Card Titles ................................................................................................ 2 2 4.3.5 Pay Attention to the First Screenful ...................................................................................... 22 4.3.6 Use of do elements ............................................................................................................. ........ 23 4.4 Pictures, Tables, and Color .................................................................................................... .................... 23 4.4.1 Avoid Useles s Images ........................................................................................................... ...... 23 4.4.2 Use Reasonable Image Sizes ................................................................................................... 23 4.4.3 Colormap ....................................................................................................................... ................. 23 4.4.4 Use Reasonable Table Si zes ..................................................................................................... 23 4.5 Use of Card Titles and Element Labels .......................................................................................... ......... 23 4.6 Perform Usab ility Test ......................................................................................................... ....................... 24 5 Terms and Abbr eviati ons ........................................................................................................ ....................... 25 6 Refere nces .......................................................................................................................................................... 27 7 Appendix A. Wireless Appl ication Proto c ol (WAP) ................................................................................ .. 28 7.1 Introduc tion ................................................................................................................... ................................ 28 7.2 WAP Archit ecture ............................................................................................................... .......................... 28 7.2.1 WAP and Internet architec ture ............................................................................................... 28 7.2.2 Wireless Application En vironment (WAE)............................................................................ 28 7.2.3 Wireless Session Pr otocol (WSP) ............................................................................................ 29 7.2.4 Wireless Transport Pr otocol (WTP)........................................................................................ 29 7.2.5 Wireless Transport Laye r Security (WTLS) ........................................................................... 29 7.3 Developing Applications for Mobile Browsing ................................................................................... 2 9 7.4 Additional In formation ......................................................................................................... ..................... 30 WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 2
Forum.Nokia.com Change History 03 March 2003 V1.0 Initial document relea se. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 3
Forum.Nokia.com Disclaimer The information in this document is provided âÂÂas is,â with no warranties whatsoever, including any warranty of merchantability, fitness for a ny particular purpose , or any warranty otherwise ar ising out of any proposal, specification, or sample. Furthermore, information provided i n this document is preliminary, and may be changed substantially prior to final release. This docume nt is provided for i nformational purposes only. Nokia Corporation disclaims all liability, including liabilit y for infringeme nt of any proprietary rights, relating to implementation of information presen ted in this document. Nokia Corporat ion does not warrant or represent that such use will not inf ringe such rights. Nokia Corporation re tains the right to make c hanges to this specification at any time, without notice. The phone UI images shown in this document are for illustra tive purposes and do not re present any real device . Copyright é 2003 Nokia Co rporation. Nokia and Nokia Connecting People are regist ered trademarks of Nokia Corporation. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. Other product and company names ment ioned herein may be trademarks or trade names of their respective owners. License A license is hereby granted to downlo ad and print a copy of this specific ation for persona l use only. No other license to any other intellectual pr operty rights is granted here in. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 4
Forum.Nokia.com WAP Service DeveloperâÂÂs Guide for Nokia 9200 Communicator Series Version 1.0; March 03, 2003 1 Introduction This WAP Service Develop er's Guide for Nokia 9 200 Communicator Series provides information and practical examples for developers who want to devel op WAP services for Nokia 920 0 Communicator Series devices. This document is adapt able for the following devices: ⢠Nokia 9210 Communic ator ⢠Nokia 9210i Communicator ⢠Nokia 9290 Communic ator ⢠Nokia 9210c Communicator The communicator is an adv anced communication s device with a featu re-rich WAP services application. This document highli ghts the poss ibilities, limitations, and requ irements of service development and provides a good introduction to the Nokia style of designing user interfaces. The Wireless Application Protocol (WAP) enhances th e functionality of mobile handsets through real- time interactive serv ices. The protocol has been designed especially fo r small screens and low bandwidth, and it offers a wide variety of wireless services over the Inte rnet for handsets. However, the WAP services screen size in Nokia 9200 Co mmunicator Series differs fro m that of common handsets and should be taken into account when design ing services that are both fast and easy to use, and offer the user maximum en joyment. Besides including issues that are Nok ia 9210 Communicator -specific, many of the instruct ions in this document can be used to maximise interoperability and ease of use of v arious other browsers. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 5
Forum.Nokia.com 2 Introduction to the User Interface of Nokia 9200 Communicator Series Figure 1: Communicator i nterface, WML browser display. This section gives a short o verview of the user interface of Nokia 9200 Communicator Series. Nokia 9200 Communicator Series is a device wit h both a communic ator interface and a phone interfac e. The WAP services appl ication is implemente d in the communicator interface toge ther with Internet services. The phone interface in the CMT part does not contain a WML browser. 2.1 WAP Browser Technical Features Data call bearer fo r WAP. GSM data tr ansports: HSCSD 2 2 / 3 1 / 1 1 with either 9600 bps or 14400 bps ch annel coding. WAP version 1 .1 The operating system is Symbian OS, which is optimise d for mobile devices. Symb ian OS is categorised according to screen size. No kia 9200 Communicator Se ries belongs to the Crystal category (64 0 x 200 display). 2.2 Keypad Nokia 9200 Communicator Series devices have a QWER TY keyboard (See Figu re 1) with a menu key for application-sp ecific menus. 2.3 Display - Detailed Description 2.3.1 Overview Nokia 9200 Communicator Series display (resolut ion 64 0 x 200 pixels) contains the followin g elements (from left to right): an Indicator area, applicatio n area and comman d button area (CBA) with four soft buttons. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 6
Forum.Nokia.com ⢠The width of th e indicator area. The width of the wi de indicator are a is 92 pixels and the width of the narrow indic ator area, which is displ ayed with the WAP browser, is 32 pixels. A space is reserved for d ifferent kinds of info rmation, such as inbox and outbox, clock and profile. ⢠The width of th e indicator area. The width of the wi de indicator are a is 92 pixels and the width of the narrow indic ator area, which is displ ayed with the WAP browser, is 32 pixels. A space is reserved for d ifferent kinds of info rmation, such as inbox and outbox, clock and profile. ⢠The width of the co mmand button area is dyn amic, and depen ds on the longest comman d text in the view. The width change s only if the whole view changes, that is, t he width remain the same when only the button te xts change in the same view. The command texts are aligned to the right. The mini mum widt h of the com mand button area is 8 0 pixels, t he maximum b eing 130 pixels. ⢠The width of the co mmand button area is dyn amic, and depen ds on the longest comman d text in the view. The width change s only if the whole view changes, that is, t he width remain the same when only the button te xts change in the same view. The command texts are aligned to the right. The mini mum widt h of the com mand button area is 8 0 pixels, t he maximum b eing 130 pixels. ⢠The width of th e application area is 490 p ixels. In full screen mo de the width is 625 pixels. He ight is always 165 pixels. ⢠The width of th e application area is 490 p ixels. In full screen mo de the width is 625 pixels. He ight is always 165 pixels. Narrow Indicator area Command button area Application area Figure 2: Different parts of the display. 2.3.2 Display colormap Nokia 9210 Communicator supports 4096 colors. The normal âÂÂtrue colorâ is specified by 24 bits, 8 bits for each color component (red, green, and blue). Nokia 9200 Communicator Series uses the most significant 4 bits of each of the color component, re sulting in a color depth of 12 bits. All other colors are either dithered or mapped to the cl osest co lor available, depending on the application. Although WAP does not support colors, Nokia 9200 Communicator Series WAP browser supports image formats with colors (other than the WBMP imag e format). 2.4 WAP Browser Display There are two views in the WAP browser: the Book marks view and the Card view. The Card view consists of a rendered card, options list, and a title bar. The Bookmarks view consis ts of a hierarchical list of saved bookmarks and a title bar. Both view s have their o wn menus that provide access to the viewâÂÂs different functions. 2.4.1 Card view WML cards are displayed in the Card view. Only one ca rd of a WML deck is shown at a time. The v ertical scroll bar is visible when the vert ical length of the active card e xceeds the screen size. The horizontal scroll bar is visible when a table or a non-br eaking paragraph e xceeds the scree n width. On the left side of the card is an options list, wh ich lists all currently active do element labels. The narrow indicator area and CBA are v isible unless in full scre en mode. The user can switch focus between the card and t he options list wit h the tab key and the left and right arrow keys. The browser remembers the focus on both the Card an d the options list. For example, if the focus on a card is on an anchor and th e user focuses on the options list and then returns the focus to the Card, WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 7
Forum.Nokia.com the focus is automatically set on that same anchor. The same applies to the options list. The browser also remembers whether t he focus was on the card o r on the options list if th e user initiates a task that causes another card to be loaded. Once the ne w card has been displ ayed, the focus is set on the card area if it had focus bef ore the action. If the us er had focused on the options l ist before the action, it remains focused after the card has been displayed. The focus on the options lis t is on the first item after the card has been fetched. T he focus is not moved after a refresh task, however. The first button is a context sensitive â actionâ button, that is, when a select or an anchor element is focused, the 1 st CBA will be "Select". If no app ropriate element has been selecte d, the button label is dimmed. The first CBA button is always the def ault button in the card v iew and may be launched by pressing <ENTER>. 2.4.2 Bookmarks view In the Bookmarks view, the user creates and ma nages WAP connectio ns. The Bookmarks view is opened when the browser is laun ched without an URL. The user can switch to the Bookmarks v iew from the Card view by sel ecting the 3 rd CBA button, Bookmark. The Bookmarks view consists of a hierarchical list of s aved bo okmarks, and a title bar. When the user focuses on a bookmark, its URL will be displayed in an info message. The URL address may be abbreviat ed, that is, part of the path name ma y be replaced with three dots, if necessary. The first and the last components of the URL (that is, th e domain name and the fil e name) are visible. If there is no space fo r both the first and t he last component of the URL, the first one is display ed and the URL is simply truncated. If the scheme of the URL is different than âÂÂhttp://âÂÂ, it is displayed before the domain. Only one bookmark item (a co nnection bookmark or a fol der) can be selected at a time. Zooming is not possible in Bookmarks view. The first CBA button is always the defau lt button in the Bookmarks view and may be launch ed by pressing <ENTER>. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 8
Forum.Nokia.com 3 Nokia 9210 Communicator User Interface Elements of WML 3 Nokia 9210 Communicator User Interface Elements of WML This chapter describes ho w to use WML in desi gning serv ices aimed at Nokia 9200 Communicator Series. It gives an overview of the graphical us er interface elements and th eir WML capabilities supported by the browser. The document does not include all possible WML el ements and attributes. Nokia 9200 Communicator Series supports WML v1.1. This chapter describes ho w to use WML in desi gning serv ices aimed at Nokia 9200 Communicator Series. It gives an overview of the graphical us er interface elements and th eir WML capabilities supported by the browser. The document does not include all possible WML el ements and attributes. Nokia 9200 Communicator Series supports WML v1.1. The elements are briefly de scribed and shown in sa m ple pictures and WML code. The code examples include only the essential part in using th e elements, that is, the document prologue is not shown. The elements are briefly de scribed and shown in sa m ple pictures and WML code. The code examples include only the essential part in using th e elements, that is, the document prologue is not shown. 3.1 Browser Display 3.1 Browser Display Options list Options list Card name Card name Ti tle bar Ti tle bar Card Card Command button area Command button area Figure 3: WML browser C ard view with diffe rent display areas. Nokia 9200 Communi cator Series has a high qu ality active mat rix display, with 640 x 200 pixels and 4096 colors. As pixel size is smaller than in laptop s, the screen is sharper. In the WAP browser, the application area is divide d as follows: 30 pi xels title bar on th e top, a WML rendering ar ea, and an options list on the left side. The wi dth of options list is 100 pi xels, but it is displayed only if there are active do elements on the card. So, de pending on th e presen ce of options list, the WML rende ring area width is between 390 an d 490 pixels. The dim ensions in full screen mode are 525 and 62 5 pixels. The height is always 165 pixels. The vertical scroll bar is visible when the vertical length of the active card exceeds the screen size. The horizontal scroll bar is visible only when a tabl e or a non-bre aking paragraph exceeds the screen width. On the left side of the card is the options list, which lists all curre ntly active do element label s with their possible icons and ho tkeys. The narrow indica tor area and CBA are visible u nless in full screen mode. The user can switch focus between the card and the options list with the t ab key. The title bar is divided in two parts. On t he left, the ti tle of the card is shown. On the right, the title of the active element is shown. If both title s are too lo n g to fit the title bar, th e title of the active element is displayed as whole and th e title of the card is trun cated or, both of them are t runcated. If there is no card name, the URL is displayed inste ad. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 9
Forum.Nokia.com 3.2 Formatting Elements The table below contains all text layout-formatting ele ments. These are described in more details in this chapter later o n. Element Formatting em Italics font of color red Strong Bold, italics font of color green b Bold font I Italics font U Underlined font Big Font size is set to big Small Font size is set to small P A paragraph break is inserted in the text Br A line break is in serted in the text Table 1: Text layout fo rmats. 3.2.1 Text formatting Figure 4: Card demonstrating text-for matting elements. The browser supports all te xt formatting elements of WML. Emph asis and strong elements are shown in colors. The picture above demonstrat es how different formatting elements are rende red as text, also specified in th e table above. <wml> <card id="text" title="Text formatting elements"> <p align="center"> This card demonstrates the formatting elements:<br/> </p> <p align="right"> <b>bold,</b><br/> <u>underline,<i>italic,<b>bold,</b></i></u><br/> <big>big,<u>underline,<i>italic,<b>bold,</b></i>< /u> </big><br/> <small>small,<u>underline,<i>italic,<b>bold,</b>< WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 10
Forum.Nokia.com /i> </u></small><br/> <em>emphasis,<i>italic,</i><u>underline,</u></em> <br/> <strong>strong,<I>italic,</i><u>underline,</u> </strong><br/> </p> <do type="prev"> <prev/> </do> </card> </wml> Example 1: Text formatting elements. 3.2.2 Paragraph Paragraph <p> determines the text groups. A new para graph alway s starts on a new line. Text inside a paragraph can be aligned to the left , center, or right, but left alignment is used by default. Alignment is determine d in paragr aph attributes (fo r example, <p align="right" >). 3.2.3 Line Break New lines in text can be defined by the line break elem ent <br>. The <br> element can be used within other elements as long as it belongs to a paragraph. 3.2.4 Fieldset The fieldset element can be used for grouping eleme nts. It implies a paragraph bre ak between the elements, and the title of the element is used as the active elementâ s title if it has no title of its own. Note that fieldset title is not supported f or text, that is, text in a card can not be given a title by using fieldset element. 3.3 Tables Figure 5: A sample table. A table element <table>, and its cont ent elements <tr> an d <td > are used to create columns and rows of text and images in a ca rd surrou nded by a gray border. Table elements do not specify column or intercolumn widths; the width of the column is same as the width of the widest cell in the column. If there is a title attribute o n the table element, it w ill be rendered as the first row of the table, with a bold font and white font color on a blue backgroun d. There can be multipl e tables in one card. A line WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 11
Forum.Nokia.com break is inserted before and after each table. Th e table may also contain images and links, which are focused from left to right and from top to bottom order. The maximum nu mber of columns in a table is 30. All cell contents of t ables over 30 columns are rendered in the l ast column of the table. <wml> <card id="card1" title="Table element"> <p> <table columns="4" align="LCCL" title=Weather Forecast> <tr> <td><b>Date</b></td><td><b>F'cast</b></td><td><b>T° C </b></td><td><b>Description</b></td> </tr> <tr> <td>M 6/7</td><td><img src="rainy.gif" alt="rain" width="30"/> </td><td>Hi 20°C, Lo 3°C</td><td>Rainy</td> </tr> <tr> <td>T 6/8</td><td><img src="partcldy.gif" alt="part cldy" width="30"/></td><td>Hi 25°C, Lo 15°C</td> <td>Partly cloudy</td> </tr> <tr> <td>W 6/9</td><td><img src="cloudy.gif" alt="cloudy" width="30" /></td><td>Hi 22°C, Lo °C</td><td>Cloudy</td> </tr> <tr> <td>T 6/10</td><td><img src="rainy.gif" alt="rainy" width="30" /></td><td>Hi 20°C, Lo 3°C</td><td>Rainy</td> </tr> <tr> <td>F 6/11</td><td><img src="sunny.gif" alt="sunny" width="30" /></td><td>Hi 28°C, Lo 0°C</td><td>Sunny</td> </tr> </table> </p> <do type="prev"> <prev/> </do> </card> </wml> Example 2: Table element. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 12
Forum.Nokia.com 3.4 Images, Links, and Timers 3.4.1 Img â Images Figure 6: Different types of imag es. In addition to WBMP image format Nokia 9210 Co mmunicator suppo rts all the most commonly know image formats. Note: some WAP Ga teways may not support all these con tent types. Nokia WAP Gateway products su pport all these conte nt types listed here: ⢠a WBMP (Wireless Bitm ap), "image/vnd.wap.wbmp" ⢠a JPEG File (incl. progress ive), ".JPG", "image/jpeg" ⢠a GIF file, ".GIF", "image/gif" ⢠a PNG file, ".PNG", "im age/png" The image element is used for displaying an imag e in a card. The maximum image size is 64 KB. Although there are no absolute limits to an image' s physical measurements. However, for taller images, the user must scroll down and f or images wider than the browser area, images are scale d down to fit the screen. I mages can also be use d inside a table and as links (see Example 4). The img element should have width an d height attribut es defined in pixels. If either one or both of the width and height attributes hav e been defined in pixels, they are us ed as the size of the image and the pla ceholder. A fetche d image is scal ed to fit the spec ified size. Width and height attri bute values specified in pe rcentages a re ignored. An image is always forced into the horizontal spa ce availabl e. That is, if t he image is wider than the screen, it will be scaled (width and height un iformly) to fit the ho rizontal space available. If the horizontal m argin (hspace) or ve rtical marg in (vspace) has been def ined for the img el ement, the number of pixels specif ied are left as a m argin between the surrounding text f low and the image. Again, hspace and vspa ce specified in per centages are ignored. When the user focuses on an image and it has not been (completel y) fetched and is not inside an anchor element, the first CBA butto n will change to "Lo ad Image". If the user selects it, the image will be fetched and displ ayed as it arrives f rom the network (or cache). If the image is inside an anchor or A element, the anchorâÂÂs UI behaviour will override the imageâÂÂs beh aviour. If the user focuses on a completely loaded image, or if the focus is on an image that is being fetched and the fetch is completed, the first CBA button will ch ange to "Save Image". If the user presses it, the standard Save As dialog box opens and the use r can save the i mage in its orig inal format ( WBMP). <wml> <card id="card1" title="Image element"> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 13
Forum.Nokia.com <p> Format:GIF <img src="games.gif" alt="Games"/> JPEG<img src="ClubN.jpg" alt="ClubNokia"/> <br/> Stretched JPEG:<img src="N6210.jpg" alt="Nokia 6210 - Streched!" width="150"/> </p> <do type="prev"> <prev/> </do> </card> </wml> Example 3: Image element. 3.4.2 Anchors A and anchor elements s pecify the head of links to an other card or deck, for exampl e. A link provides easy navigation through an application. An anchor may consist of text, an image, or a combin ation of text and an image. The < a> element is a short form of the anchor elemen t. In general it is recommended to use t he < a> element instead of anchor where possible. An u nselected anchor is rende red as under lined (an im age is frame d), wh ile the color of a selected anchor is inverted. Figure 7: Text and image links. An i mage within a table selected. <wml> <template> <do type="prev" label="go"> <prev/> </do> </template> <wml> <card id="card1" title="Anchor element"> <p> Here's a  <a title="Link to Products">link<go href="#products"/></a>  to another card. Tables can contain links and an image can be a link, too. <a title="Link to Nokia Group" href="#group"><img src= "Nokia_n1.gif" alt="nokia"/></a> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 14
Forum.Nokia.com </p> <p align="right"> <table columns="2" title="Weather Forecast"> <tr> <td>Monday 6/7</td> <td><a title="See more about the weather..." href="#rain"> <img src="rainy.gif" alt="rainy" width="30"/></a></td> </tr> <tr> <td>Tuesday 6/8</td> <td><img src="sunny.gif" alt="sunny" width="30"/></td> </tr> <tr> <td>Wednesday 6/9</td><td><img src="partcldy.gif" alt="part cldy" width="30"/></td> </tr> <tr> <td>Thursday 6/10</td> <td><img src="cloudy.gif" alt="cloudy" width="30"/></td> </tr> <tr> <td>Friday 6/11</td><td><img src="rainy.gif" alt="rainy" width="30"/></td> </tr> </table> </p> </card> </wml> Example 4: Anchor element. 3.4.3 Timer The timer element def ines a card timer, which processe s inactivity or idle time. Timer s tarts the count immediately after the card is loaded. This element can be used only o nce in card and its unit is 1/10 s. 3.5 Dynamic Buttons 3.5.1 Do elements The do element binds a task to a user act ion, which ca n be executed in an options list on the left side of the screen. The options list contains all curr ently access ible do elements (options). The text representing each do el ement is the do elementâÂÂs l abel attribute value, or if it has not been defined, the UI string corresponding to the elemen tâÂÂs type attribute value. The labels are updated with current values whenever a refresh task is executed but th e focus in a list is not changed. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 15
Forum.Nokia.com Figure 8: Do elements in an option s list. The options list is focused. Each WML deck can have a template el ement. The template contains do elements that are to be displayed on each card of the deck. A cardâÂÂs do eleme nts can either override or hide the templateâÂÂs do elements. Hidden do eleme nts will not be shown. The order of the cardâÂÂs do elements in the options li st is the same as in which they are defined o n the card, unless they override the templat eâÂÂs do elements. The templateâÂÂs do elements are l ast on the options list, that is, after all t he cardâÂÂs do elements . If a do element on a card overrides the do element on a template, the cardâÂÂs do element replaces the templateâÂÂs do element in the list. All optional do elements are displayed. Do elements of the type âÂÂprevâ are handled as an exce ption. (See section 3. 5.2) <wml> <template> <do type="accept" name="news" label="News"> <go href="http://.../news.wml"/></do> <do type="accept" name="contactus" label="Contact us"> <go href="http://.../contact.wml"/></do> <do type="accept" label="Help" name="helphelp" optional="false"> <go href="http://.../help.wml"/></do> </template> <card id="form" title="Registration Form"> <p> Company Information<br/> </p> <p align="right"> <small>Company name:</small> <input name="company" type="text" title="Company name" format="*A" emptyok="false" size="25"/><br/> <small>Street address:</small> <input name="address" type="text" title="Street address" emptyok="false" size="25"/><br/> <small>Postal Code:</small> <input name="code" type="text" title="Postal code" emptyok="false" size="25"/><br/> <small>City:</small> <input name="city" type="text" title="City" emptyok="false" size="25"/><br/> <small>Country:</small> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 16
Forum.Nokia.com <select name="country" multiple="true"> <option value="-">-</option> <option value="Australia">Australia</option> <option value="Canada" size="25">Canada</option> <option value="Denmark">Denmark</option> <option value="Finland">Finland</option> <option value="France">France</option> <option value="Germany">Germany</option> <option value="Italy">Italy</option> </select> </p> <do type="accept" label="Enter" optional="false"> <go href="#confirm" method="get" sendreferer="false"/> </do> <do type="prev" label="Back" optional="false"> <prev/> </do> </card> </wml> Example 5: Do element - options list items. 3.5.2 Prev type do e lements Whenever a new card is shown, a new history l ist item is created. When activating the prev task on a WML card, the target URL is the p revious history list item and the current card (in which p rev was activated) is n ot retained in the h istory list (the re is no "forward" funct ion). Do elements of the type âÂÂprevâ are handl ed as an exception to other types of do elements (see s ection 4.5.1). If there is only on e "prev" type do element active, it is not shown on the o ptions list. Instead, it is bound to the 2 nd CBA button and it is labelled as "Back". The 2 nd CBA is dimme d if there is zero o r more than one "prev" ty pe do element active and do elements are displayed on th e options list like all other do elements. It is likely that most pages implemen t only one do element of the type "pr ev". The author of the WAP service is always responsible for the wo rking navigation model within the service. If there is a need fo r back functionality, it should be explicitly def ined with the "prev" type do element. The WAP bro wser does not have any implicit back functionality. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 17
Forum.Nokia.com 3.6 WML Input Processing 3.6.1 Input elements Figure 9: Input element â focus is in the input box with numeric format . An input element specifies a text entry ob ject for data input. It is shown as an input box in a card. The text entered in the input element can be dete rmined by the format attribute. The format string specifies that a part icular character mu st be a number, an uppercas e character, or a lowercase character, for example. The user can enter any characters in th e input field but the ch aracters that do not currently m atch the format are drawn in red color and ar e underlined (so that incorrect spaces or missing characte rs become visible). In addition , every time the user enters a different type of input than the browser was e x p e c t i n g , a n a p p r o p r i a t e i n f o m e s s a g e i n a n " I n c o r r e c t i n p u t d i a l o g b o x " w i l l b e d i s p l a y e d . A l l characters that do m atch the format are drawn in black (normal body text color). The author can specify a m aximum length for the entr y either with the format or with the maxlength attribute. If the maximum length is reached, the inpu t element will not insert any ch aracters in the field, but will beep and disp lay an info message. The author can specify with the emptyok attribute t hat the entry must match the form at mask. If there are input elements that do h ave that requirem ent, but the entry in those elements does not match the mask (such as when the v alue is empty) an d a task is initiated ( either by a user action or timer), the Missing Input dialog box will appear. Once the user has closed the dialog box, the focus will move to the first of those input elements on the card. Note that the user can exit the card only if all input elements hav e a valid value or if the y are allowed to be em pty. <wml> <card id="Form" title="Registration Form"> <p> Please login:<br/> </p> <p align="right"> <small>User name:</small> <input name="user" type="text" title="Max. 8 char. long" format="*A" emptyok="false" maxlength="8" size="25"/><br/> <small>User password:</small> <input name="user pw" type="password" title="Max 16 char. Long" format="*A" emptyok="false" maxlength="16" size="25"/><br/> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 18
Forum.Nokia.com </p> <p> Input your birthday:<br/> </p> <p align="right"> <small>Date of birth:</small> <input name="birth" type="text" title="dd/mm/yyyy" format= "NN\/NN\/4N" emptyok="false" maxlength="14 size="25"/><br/> </p> <do type="accept" label="Enter"> <go href="#confirm" method="get"/> </do> <do type="prev" label="Back"> <prev/> </do> </card> </wml> Example 6: Input el ement â Input box. 3.6.2 Selection lists Figure 10: Simple single-selection list. Selection lists are an input element that specifies a list of options for the use r to choose from. The selection list can be either single-select ion or mult iple-selectio n element. Each option is specified by an option element. Options can be organised into groups by using th e optgroup element. A selection list is opened by focusing on the input box and pressin g the 1 st CBA button for "Change". The select list appe ars. A single-selection list has a title of the title attribut e, and if it hasn't been defined, the title displays the text "Selection" by default. A multipl e-selection list has two windows; the left one is for unselecte d items and the right one contains the selected items. The title of the non- selected items pane is the select elementâÂÂs title or if one has not been def ined, the default text displayed is "Not selected". The title of the selected items pane is "s elected". The user can switch focus between the two dialog bo xes with the tab key. If the options have been grouped with an optgroup element, the optgroup titl e will be shown as a bold item in the selection li st. All options under the optgrou p element are intended an d shown under the optgroup item. Note th at Nokia 9200 Communica tor Series o nly supports one level of optgroups. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 19
Forum.Nokia.com Optgroup on a deeper level is ignored and its options are handled as if they were under the firs t level optgroup (that is, intended as one level). Figure 11: Multiple-selection list. <wml> <card id="phones" title="Information Request"> <p align="left"> Choose your age from the list:<br/> <select title="Your age"> <option title="12-30">12-30</option> <option title="31-50">31-50</option> <option title="51-">51-</option> </select><br/> <br/>Send me more information about:<br/> <select name="models" title="Products" multiple="true"> <optgroup title="Phones"> <option>Nokia 3310</option> <option>Nokia 6210</option> <option>Nokia 9210 Communicator</option> </optgroup> <optgroup title="Accessories"> <option>Battery</option> <option>Desktop stand</option> <option>Charger</option> <option value="Headset">Headset</option> </optgroup> </select><br/> <br/>Input your name:<br/> <input name="name" type="text" title="Name" size="30"/> </p> <do type="accept" label="Enter" optional="false"> <go href="#confirm" method="get" sendreferer="false"/> </do> <do type="prev" label="Back" optional="false"> <prev/> </do> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 20
Forum.Nokia.com </card> </wml> Example 7: Selection lists. 3.7 Titles and Labels 3.7.1 Titles A title bar is divide d in two parts, on the left is the card title and on the right is space for element titles, which are shown only when the element is focus ed. The card title is displayed con tinuously and if there is no card title, the actual URL of t he card is displayed instea d. Below is a list of element titles, which u se the righ t side of the title bar. ⢠Link, attribute "title" ⢠Image, attribute "alt" ⢠Input, attribute "title" ⢠Select, attribute "title" In addition, there are elements, which ha ve a title, bu t it is not shown on the main title bar. These are tables whose title att ribute value is show n on its own title bar, select elements title attribute value is shown on main title bar when the input box is focuse d. After opening the select list, the same title is shown on the select lists own title bar. The optgroup title attributes value is sho wn as a bold item in select list. 3.7.2 Labels The only element with a l abel attribute is the do elem ent. Cards currently accessib le do elements are listed in the options list on the left side of a pplication area, whe re their label attribute values are shown. An exception to this is the "prev" t ype do element (see sectio n 3.5.2). 3.8 Limitations 3.8.1 WML charact er sets. The WAP browser uses the character sets defined an d used in the Symbian OS platform, this includes the usage of UNICOD E as necessary. Whe re multiple characte r sets are found the reference-processing model specifi ed in Section 6.1 of the WML spec ification is use d. 3.8.2 Features not supported in W ML 1.1 â classâ attributes as describe d in the WML Specification, section 8.9. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 21
Forum.Nokia.com 4 General Usability Issues â Guidelines for Design 4.1 WML History Navigation Due to the differences in the processin g of the history between WAP and WEB, only the history processing described i n the WML specifications is fo llow ed. This means that the service p rovider has to take care of the navigation as a whole. 4.2 Validate Your WML There are several XML validators availabl e that validate your documents against WML Do cument Type Definition. It is recommended t hat authors validate their WAP pages, because invalid WML is always treated as an error and dis carded (t hat is, it is not shown to the user! ). Several XML vali dators can be found at http://www.w apdevelopers.org/xml.tpl?CAL LER=index.tpl . 4.3 Site Organization 4.3.1 Avoid âÂÂdoormatâ pages The user accesses your WAP site over a GSM data call, an d pays per second. It is not recommende d that your site begins with a âÂÂdo ormatâ page, which serves no purpose other than perhaps to greet the visitor and to displ ay a logo. It is better that your site allows users to access you r service directly. If there is a need to use a timer, it shoul d not take lo nger than ~1.5 seconds, if it takes a longer time, add a 'continue' link to give the user possibility to exit the card. 4.3.2 Automatically Detect the Browser If you are using a modern Web site hosting environment, it is possible to detect the browser as well as the language mode an d supply the correct content tr ansparently, without requirin g user interaction. Nokia 9200 Communicator Series display is larger th an normal phone displays, and thus has more possibilities that are worth taking advantage of. 4.3.3 Optimise for Size The size of the content is critical. If you have large de cks (listings, large tables, etc.), consider splitting them in multiple pa rts for faster downloadin g. As for the total downloading time, som e studies plac e an u pper limit for acceptable delay to 10 to 15 seconds, including all images, on a PC-based bro wse r. It is highly recommende d to have a response time (excludin g connection time) of less than 10 seconds in mobile environ ments. 4.3.4 Choose Descriptive Card Titles It is highly useful to give a desc riptive name for the card. It might be a goo d idea to start the title with your serviceâÂÂs name and kee p the total length of the title short. It also pays to use mean ingful URLs since the user sees the URL of the currently selected link on the screen and can use it as a navigational h elp, especially when images have not been loaded. 4.3.5 Pay Attention to the First Screenful Because of the communicator's form factor, the first (topmost) screenful of any page is the most important one. All of the often-used n avigational li nks, search fields, login screens, and bulk of the information should reside there, if at all. The user is then able to navigate fo rward before the rest of the card has been loaded, and the user do es not have to scroll the card. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 22
Forum.Nokia.com 4.3.6 Use of do elements Always use descriptive and short labels for all do elements. Favor local do elements instead of anchored links that are totally out of co ntext. Always include the prev element in each card to enable backward navigation. 4.4 Pictures, Tables, and Color 4.4.1 Avoid Useless Images Downloading images takes time, and many users may switch o ff the loading of images for more speed. Try to optimise the size of images. If you have large im ages on your site, consider using thumbnails for th e image in dex. Always provide an alte rnative text (using the ALT attrib ute of the IMG element) for images that co nvey information. Always use a null alternativ e text (ALT = âÂÂâÂÂ) for images, which do not convey information, or are used for page layout or decorative purposes only . 4.4.2 Use Reasonable Image Sizes The maximum image widt h on the WAP browser screen is 490 pixels. Images larger than th at will be automatically scaled do wn to fit the screen. Using any larger im ages than 490 pixels is a w aste of bandwidth and will slow down the service conne ct ion. A maximum size for images downloaded through data calls is about 60 KB although 30 KB is recommended m aximum. 4.4.3 Colormap WAP does not include any support for colors, but Nokia 9200 Communicator Series WAP browser supports image form ats with color (other th an the WBMP im age format). Nokia 9200 Communicator Series su pports 4096 colors. Th e true color i s specified by 24 bits, 8 bi ts for each color component (red, green, and blue). Nokia 9200 Communicator Series uses the most significant 4 bits of each part of the color compon ent, resulting in a color depth of 12 bits. All other colors will either be dithered or mapped t o the cl osest color available, depe nding o n the applicati on. When creating graphics with uniform f ills, use only the colors, which will not be dithered. Some image processing tools may be able to reduce t he size of images if you res trict the number of colors to the exact 4096 col ors supported by Nokia 9200 Communi cator Series. Do not use colors, which are too close to each other (c olors that differ only in the least significant four bits of each co lor component). This may result in the colors bein g mapped to the exact s ame color. 4.4.4 Use Reasonable Table Sizes If the table size exceeds the maximum widt h of the WAP services applicatio n screen due to the number of columns, the horizont al scroll bar will appear. Anyhow, to keep the cell content readabl e, special attention should be paid on tabl e structuring. 4.5 Use of Card Titles and Element Labels Card titles describe the co ntent of the display an d their use is re commended. They help the user to navigate because they function as a reminder of wher e the user is in the application. The header text should be determined by the item previously selected by the user. For instance, the card title âÂÂBookmarksâ tells the user that the display contains a l ist of bookmarks in the application and that the opti ons item previo usly se lected wa s Bookmarks . WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 23
Forum.Nokia.com Proportional fonts are used in head er te xts, and if the heade r text is too long, it is automati cally truncated. Truncation is usually bette r than abbrev iation, because the user might b e confused by unfamiliar abbreviat ions that are difficult to underst and. 4.6 Perform Usability Test It is always good to perform a usab ility test for new applications. People who have not been involved in the design or developme nt of the application tend to notice potential usability problems ofte n not obvious to those who know the design by heart. Usability tests should always be perfo rmed as early as possible in the development process. Any necessary changes resulting from the tests can then be implemented within the development schedule. Try to recruit users who are representat ive of the end users of the application, and try to conduct the usabil ity test on a smaller scale, if the schedule does not allow for extensive testing . WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 24
Forum.Nokia.com 5 Terms and Abbreviations Term or Abbreviation Description Card A single WML unit of navi gation and user interface. Deck A collection of WML cards th at is the smallest downloadable unit. A single car d in a deck cannot be downloaded; the entire deck must be downloaded. Service developers shoul d be aware of this, and not creat e large app licatio ns in a sing le deck. Do element A way of defining the binding between events (su ch as a user selection) and a task (for example, to go somewhere). DTMF tone Standard tone used to transmit numeric data via telephone. Generated when numeric keys are pressed. GUI Graphical User Inte rface. HTML Hypertext Markup Langua ge. The markup language used for publishing hypertext on the Wo rld Wide Web. HTTP Hypertext Transfer Prot ocol . An application-level protocol for transferring HT ML documents on t he Internet. Hyperlink A link within a documen t or card that allo ws quick navigation to another document (card). IDE Integrated Development Environ ment. A tool for application de velopers. Input element A markup element t hat allows for interaction with the user, that is, lettin g the user input te xtual values. These can be used f or inputs to lo cally stored scripts, or for parsing to origin serv ers. Multiselection list A selection list that allows the user to scroll and select several (or no) options to be active. Navigation The concept of moving between menu items, decks, and cards. Proportional font A font in which different letter widths do not necessarily have the same number of pixels. "W" an d "I" are good e xamples. SDK Software De velopment Ki t. A kit for software developers that inclu des, e.g., emulator, sampl e codes, reference docu mentation. Selection list List of user-selectable options. SIS Symbian Installation System. A system that provides a simple and consistent use r interface for installin g applications, data, or configuration information to Symbian OS devices. Symbian OS applic ations are installed to the device packag ed in installation (.sis) files. Soft key The phone has one or more function keys whose function depends on the state of the phone. These keys are called soft keys b ecause there is a n associated te xt on the display. UI User Interface. URL Uniform Reso urce Locator. String that identifies resources in the Web. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 25
Forum.Nokia.com Word wrapping Formatting rule for text appear ance. WML Wireless Mark up Language. Markup language based on Extensible Markup L anguage (XML), w hich is int ended for use in specifying cont ent and user interface for narrowband devices, including cellular phones and pagers. WSP Wireless Session Protocol. A layer of WAP stack, which is optimized for low b andwidth bearer networks with long latency. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 26
Forum.Nokia.com 6 References ⢠User's guide for Nokia 9200 Communicator Series devices, http://www.nokia.com ⢠Nokia Mobile Internet Toolk it, http://www.forum.nokia.com ⢠Nokia 9200 Communicator Series SDK for Symbian OS ( including an emulator ), http://www.forum.nokia.com ⢠Wireless application protocol specificatio ns, http://www.openmobilealliance.org WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 27
Forum.Nokia.com 7 Appendix A. Wireless Application Protocol (WAP) 7.1 Introduction The Wireless Applicatio n Protocol (WAP) is a set of protocols that allow the development of applications and services for use w ith mobile phones and othe r mobile devices. The WAP Forum maintains these protocols and their re lated standa rds and spec ifications. The WAP Forum consists of a number of high-tech companies f rom the information technology, software, and telecommunication industries. The objectives of the WAP Forum are to: ⢠Bring Internet content and advan ced data applications t o digital mobile phones ⢠Create a global wireless protoc ol specificat ion that work s ac ross different wireless network technologies ⢠Enable the creation of content and applications th at scal e across a wide range of bearer networks and device types ⢠Embrace existing standards and technology wherever possible 7.2 WAP Architecture 7.2.1 WAP and Internet ar chitecture In order to apply as much leverage to the existing Internet standard as poss ible, the WAP stack closely follows the Internet model. This is illustrated in Figu re 12. Internet HTML JavaScript TM HTTP TLS - SSL TCP/IP UDP/IP SMS USSD CSD IS-136 CDMA CDPD PDC-P Etc.. Bearers: Wireless Application Wireless A pplication Environment (WAE) Wireless Session Layer (WSP) Wireless Tran sport Layer Sec urity (WTLS) Wireless Datagram Protocol (WDP) Other Services and Applications Wireless Tra nsaction Pr otocol (WTP) Figure 12: Comparison of In ternet and WAP Architecture This layered archite cture allows applicat ions to utilise the features of the WAP stack through well- defined interf aces. This close link to the Interne t arch itecture allows develop ers to utilise their existing knowledge and expertise when develo ping applications for mobile terminals. 7.2.2 Wireless Application Environment (WAE) The Wireless Application Environ men t (WAE) is a general-purpose application environment that uses a combination of Internet and mobile terminal technology. It provides a framework for the development of applications on a mobile termin al. WAE contains support for the followin g functionality: WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 28
Forum.Nokia.com ⢠Wireless Markup L anguage (WML) - a lightweight pres entation langu age, similar to HyperText Markup Language (HTML) bu t optimised for use w ith mobile terminals. ⢠Wireless Markup Language Script (WMLS) - a lightw eight script language, similar to Java Script TM . ⢠Wireless Telephony Application / Interface (WTA / WT AI) - telephony services an d programming interfaces. ⢠Content formats - defin ed data form ats, such as vCard and vCalendar. 7.2.3 Wireless Session Protocol (WSP) The Wireless Session Protocol (WSP) pro vides the a pplication layer of WAP with an interface for two session services. The first is a co nnection-oriented s ervice that opera tes above the transaction layer protocol. The second is a connectionless s ervice that operates abov e a secure or non-secure datagram service. The WSP is optimised for lo w bandwidth bear er networks with long l atency. 7.2.4 Wireless Transport Protocol (WTP) The Wireless Transport Protocol (WTP) runs on top of the datagram service an d provides a lightweight transaction-oriente d protocol, suitable fo r use in mo bile termin als. WTP operat es over secure or non- secure wireles s datagram networks. 7.2.5 Wireless Transport Layer Security (WTLS) Wireless Transport Layer Security (WTLS) is based on the industry stan dard Transport L ayer Security (TLS) and is optimised for use over narrowband co mmunication channels. WTL S may be used for secure communicatio n between terminals, an d applications can sele ctively enable WTLS features . 7.3 Developing Applications for Mobile Browsing Application develope rs can use the prin ciples of WAP to develo p new services or adapt existing Internet applicat ions for use with mo bile terminals. Appl ications are w ritten in Wireless Markup Language (WML) and WML Script, and stored on either a nor mal Web server (origin server) o r directly on the WAP gateway. The content sto red on the Web server is accessible from mobile termin als via the cellular network and a WAP gateway or proxy. The proxy server acts as a gateway between the cellular ne twork and the Internet or Intranet. The data sent between the origin server and the handset is binary enco ded to optimise transmissio n over the narrow bandwidth of the cellul ar network. Note that the content stored on the Web server might be in either textual or binary format. When the WAP gateway fetches textual content, it automat ically compiles this to the encoded form at to minimise network load. Figure 13 sh ows the network-related elements required for dev eloping and offering se rvices to mobile users. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 29
Forum.Nokia.com WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 30 Wireless Netw ork WA P Proxy WT A Server Binar y Binary WML HTML Filte r WML WML HTML Web Server Figure 13: Elements related to mobile browsing. Web server The Web server stores the appl ications written in WM L. Alternatively, exist ing HTML applicati ons can be used. HTML filter Any applications written in HTML will have to be conve rted to WML before they are sent to the mobile terminal. This HTML filter may form part of the Web server o r the WAP proxy. WAP proxy The WAP proxy acts as the gateway be tween the cellular network and the Inte rnet or Intranet. It encodes the information, which is to be sent to th e mobile terminal in b inary format and decodes information sent f rom the mobile terminal. WTA server The WTA server h andles network-specific applications. These applications are not discussed in this document. 7.4 Additional Information Further information on WAP is available at the Open Mobile Alliance web site, http://www.openmobilealliance.o rg.
Forum.Nokia.com Build Test Sell Build Test Sell Developing and m arketing mobile a pplications with Nokia Developing and m arketing mobile a pplications with Nokia 1 Go to Forum.Nokia.com Go to Forum.Nokia.com Forum.Nokia.com provides the tools and resources you need for con tent and application develo pment as well as the channels fo r sales to op erators, enterpris e s, and consumers. Forum.Nokia.com provides the tools and resources you need for con tent and application develo pment as well as the channels fo r sales to op erators, enterpris e s, and consumers. Forum.Nokia.com Forum.Nokia.com Download tools and emulators Download tools and emulators 2 Forum.Nokia.com/tools has links to tool s from Noki a and other industry leaders inclu ding Borland, Adobe, AppForge, Macromed ia, Metrowerks, and Sun. Forum.Nokia.com/tools has links to tool s from Noki a and other industry leaders inclu ding Borland, Adobe, AppForge, Macromed ia, Metrowerks, and Sun. Forum.Nokia.com/tools Forum.Nokia.com/tools Get documents and specifications Get documents and specifications 3 The documents area contains useful whit e papers, FA Qs, tutorials, and APIs for Sy mbian OS and Series 60 Platform, J2ME, messaging (in cluding MMS), and other technologies. Forum.Nok ia.com/devices lists detailed technical specifications for Nokia devices. The documents area contains useful whit e papers, FA Qs, tutorials, and APIs for Sy mbian OS and Series 60 Platform, J2ME, messaging (in cluding MMS), and other technologies. Forum.Nok ia.com/devices lists detailed technical specifications for Nokia devices. Forum.Nokia.com/document s Forum.Nokia.com/devices Forum.Nokia.com/document s Forum.Nokia.com/devices Test your application and g et support Test your application and g et support 4 Forum Nokia offers free and fee-b ased support that pr ovides you w ith direct access to Nokia en gineers and equipment and conne cts you with other developers around the worl d. The Nokia OK testing program enables your application to enjoy premium placement in Nokia's sales channels. Forum Nokia offers free and fee-b ased support that pr ovides you w ith direct access to Nokia en gineers and equipment and conne cts you with other developers around the worl d. The Nokia OK testing program enables your application to enjoy premium placement in Nokia's sales channels. Forum.Nokia.com/support Forum.Nokia.com/ok Forum.Nokia.com/support Forum.Nokia.com/ok Market through Nokia channels Market through Nokia channels 5 Go to Forum.Nokia.com/business to learn about all of the marketing channels op en to you, including Nokia Tradepoint, an online B2B ma rketplace. Go to Forum.Nokia.com/business to learn about all of the marketing channels op en to you, including Nokia Tradepoint, an online B2B ma rketplace. Forum.Nokia.com/business Forum.Nokia.com/business Reach buyers around the globe Reach buyers around the globe 6 Place your applications in Nokia Tradepoint an d they're available to dozens of b uying organizations around the world, ranging from leading global op erators and enterpris es to regional oper ators and XSPs. Your company an d applications wi ll also be co nsidere d for the regional Nok ia Software M arkets as well as other global and regional opportunities, including personal intro ductions to operators, on- device and in-box placement, and particip ation in invitation-only events around the world. Place your applications in Nokia Tradepoint an d they're available to dozens of b uying organizations around the world, ranging from leading global op erators and enterpris es to regional oper ators and XSPs. Your company an d applications wi ll also be co nsidere d for the regional Nok ia Software M arkets as well as other global and regional opportunities, including personal intro ductions to operators, on- device and in-box placement, and particip ation in invitation-only events around the world. Forum.Nokia.com/business Forum.Nokia.com/business WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 31
Forum.Nokia.com Contents 1 Introduc tion ................................................................................................................... ...................................... 5 2 Introduction to the User Int erface of Nokia 9 200 Comm unicator Se r ies ........................................... 6 2.1 WAP Browser Tech nical Features ................................................................................................. .............6 2.2 Keypad ................................................................................................................................................................6 2.3 Display - Detailed Description ................................................................................................. ....................6 2.3.1 Overview ....................................................................................................................... ....................6 2.3.2 Display co lormap ............................................................................................................... .............7 2.4 WAP Browser Display ............................................................................................................ .........................7 2.4.1 Card view...........................................................................................................................................7 2.4.2 Bookmarks view ................................................................................................................. ............8 3 Nokia 9210 Communicator User Interface Elements of W ML ................................................................. 9 3.1 Browser Di splay ...............................................................................................................................................9 3.2 Formatting Elemen ts ............................................................................................................ ...................... 10 3.2.1 Text form atting ................................................................................................................ ............ 10 3.2.2 Paragraph ...................................................................................................................... ................ 11 3.2.3 Line Break ..................................................................................................................... ................. 11 3.2.4 Fieldset....................................................................................................................... ..................... 11 3.3 Tables ............................................................................................................................................................... 11 3.4 Images, Links, and Ti mers ...................................................................................................... ................... 13 3.4.1 Img â Im ages ................................................................................................................... ............. 13 3.4.2 Anchors ........................................................................................................................ ................... 14 3.4.3 Timer .......................................................................................................................... ..................... 15 3.5 Dynamic Buttons ................................................................................................................ .......................... 15 3.5.1 Do ele ments .................................................................................................................... .............. 15 3.5.2 Prev type do el ements .......................................................................................................... ..... 17 3.6 WML Input Processing ........................................................................................................... ..................... 18 3.6.1 Input el ements ................................................................................................................. ............ 18 3.6.2 Selection lists ................................................................................................................ ................ 19 3.7 Titles an d Labe ls .............................................................................................................. ............................. 21 3.7.1 Titles ......................................................................................................................... ....................... 21 3.7.2 Labels ......................................................................................................................... ..................... 21 3.8 Limitati ons .................................................................................................................... ................................. 21 3.8.1 WML character sets. ............................................................................................................ ........ 21 3.8.2 Features not support ed in WML 1.1 ...................................................................................... 21 4 General Usability Issues â Guidelines for De sign............................................................................... ...... 22 4.1 WML History Navigation ......................................................................................................... ................... 22 WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 1
Forum.Nokia.com 4.2 Validate Yo ur WML .............................................................................................................. ......................... 22 4.3 Site Orga nization .............................................................................................................. ........................... 22 4.3.1 Avoid âÂÂdoorma tâ pages.......................................................................................................... ..... 22 4.3.2 Automatically Detect the Browser ......................................................................................... 22 4.3.3 Optimise for Size.............................................................................................................. ............ 22 4.3.4 Choose Descriptive Card Titles ................................................................................................ 2 2 4.3.5 Pay Attention to the First Screenful ...................................................................................... 22 4.3.6 Use of do elements ............................................................................................................. ........ 23 4.4 Pictures, Tables, and Color .................................................................................................... .................... 23 4.4.1 Avoid Useles s Images ........................................................................................................... ...... 23 4.4.2 Use Reasonable Image Sizes ................................................................................................... 23 4.4.3 Colormap ....................................................................................................................... ................. 23 4.4.4 Use Reasonable Table Si zes ..................................................................................................... 23 4.5 Use of Card Titles and Element Labels .......................................................................................... ......... 23 4.6 Perform Usab ility Test ......................................................................................................... ....................... 24 5 Terms and Abbr eviati ons ........................................................................................................ ....................... 25 6 Refere nces .......................................................................................................................................................... 27 7 Appendix A. Wireless Appl ication Proto c ol (WAP) ................................................................................ .. 28 7.1 Introduc tion ................................................................................................................... ................................ 28 7.2 WAP Archit ecture ............................................................................................................... .......................... 28 7.2.1 WAP and Internet architec ture ............................................................................................... 28 7.2.2 Wireless Application En vironment (WAE)............................................................................ 28 7.2.3 Wireless Session Pr otocol (WSP) ............................................................................................ 29 7.2.4 Wireless Transport Pr otocol (WTP)........................................................................................ 29 7.2.5 Wireless Transport Laye r Security (WTLS) ........................................................................... 29 7.3 Developing Applications for Mobile Browsing ................................................................................... 2 9 7.4 Additional In formation ......................................................................................................... ..................... 30 WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 2
Forum.Nokia.com Change History 03 March 2003 V1.0 Initial document relea se. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 3
Forum.Nokia.com Disclaimer The information in this document is provided âÂÂas is,â with no warranties whatsoever, including any warranty of merchantability, fitness for a ny particular purpose , or any warranty otherwise ar ising out of any proposal, specification, or sample. Furthermore, information provided i n this document is preliminary, and may be changed substantially prior to final release. This docume nt is provided for i nformational purposes only. Nokia Corporation disclaims all liability, including liabilit y for infringeme nt of any proprietary rights, relating to implementation of information presen ted in this document. Nokia Corporat ion does not warrant or represent that such use will not inf ringe such rights. Nokia Corporation re tains the right to make c hanges to this specification at any time, without notice. The phone UI images shown in this document are for illustra tive purposes and do not re present any real device . Copyright é 2003 Nokia Co rporation. Nokia and Nokia Connecting People are regist ered trademarks of Nokia Corporation. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. Other product and company names ment ioned herein may be trademarks or trade names of their respective owners. License A license is hereby granted to downlo ad and print a copy of this specific ation for persona l use only. No other license to any other intellectual pr operty rights is granted here in. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 4
Forum.Nokia.com WAP Service DeveloperâÂÂs Guide for Nokia 9200 Communicator Series Version 1.0; March 03, 2003 1 Introduction This WAP Service Develop er's Guide for Nokia 9 200 Communicator Series provides information and practical examples for developers who want to devel op WAP services for Nokia 920 0 Communicator Series devices. This document is adapt able for the following devices: ⢠Nokia 9210 Communic ator ⢠Nokia 9210i Communicator ⢠Nokia 9290 Communic ator ⢠Nokia 9210c Communicator The communicator is an adv anced communication s device with a featu re-rich WAP services application. This document highli ghts the poss ibilities, limitations, and requ irements of service development and provides a good introduction to the Nokia style of designing user interfaces. The Wireless Application Protocol (WAP) enhances th e functionality of mobile handsets through real- time interactive serv ices. The protocol has been designed especially fo r small screens and low bandwidth, and it offers a wide variety of wireless services over the Inte rnet for handsets. However, the WAP services screen size in Nokia 9200 Co mmunicator Series differs fro m that of common handsets and should be taken into account when design ing services that are both fast and easy to use, and offer the user maximum en joyment. Besides including issues that are Nok ia 9210 Communicator -specific, many of the instruct ions in this document can be used to maximise interoperability and ease of use of v arious other browsers. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 5
Forum.Nokia.com 2 Introduction to the User Interface of Nokia 9200 Communicator Series Figure 1: Communicator i nterface, WML browser display. This section gives a short o verview of the user interface of Nokia 9200 Communicator Series. Nokia 9200 Communicator Series is a device wit h both a communic ator interface and a phone interfac e. The WAP services appl ication is implemente d in the communicator interface toge ther with Internet services. The phone interface in the CMT part does not contain a WML browser. 2.1 WAP Browser Technical Features Data call bearer fo r WAP. GSM data tr ansports: HSCSD 2 2 / 3 1 / 1 1 with either 9600 bps or 14400 bps ch annel coding. WAP version 1 .1 The operating system is Symbian OS, which is optimise d for mobile devices. Symb ian OS is categorised according to screen size. No kia 9200 Communicator Se ries belongs to the Crystal category (64 0 x 200 display). 2.2 Keypad Nokia 9200 Communicator Series devices have a QWER TY keyboard (See Figu re 1) with a menu key for application-sp ecific menus. 2.3 Display - Detailed Description 2.3.1 Overview Nokia 9200 Communicator Series display (resolut ion 64 0 x 200 pixels) contains the followin g elements (from left to right): an Indicator area, applicatio n area and comman d button area (CBA) with four soft buttons. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 6
Forum.Nokia.com ⢠The width of th e indicator area. The width of the wi de indicator are a is 92 pixels and the width of the narrow indic ator area, which is displ ayed with the WAP browser, is 32 pixels. A space is reserved for d ifferent kinds of info rmation, such as inbox and outbox, clock and profile. ⢠The width of th e indicator area. The width of the wi de indicator are a is 92 pixels and the width of the narrow indic ator area, which is displ ayed with the WAP browser, is 32 pixels. A space is reserved for d ifferent kinds of info rmation, such as inbox and outbox, clock and profile. ⢠The width of the co mmand button area is dyn amic, and depen ds on the longest comman d text in the view. The width change s only if the whole view changes, that is, t he width remain the same when only the button te xts change in the same view. The command texts are aligned to the right. The mini mum widt h of the com mand button area is 8 0 pixels, t he maximum b eing 130 pixels. ⢠The width of the co mmand button area is dyn amic, and depen ds on the longest comman d text in the view. The width change s only if the whole view changes, that is, t he width remain the same when only the button te xts change in the same view. The command texts are aligned to the right. The mini mum widt h of the com mand button area is 8 0 pixels, t he maximum b eing 130 pixels. ⢠The width of th e application area is 490 p ixels. In full screen mo de the width is 625 pixels. He ight is always 165 pixels. ⢠The width of th e application area is 490 p ixels. In full screen mo de the width is 625 pixels. He ight is always 165 pixels. Narrow Indicator area Command button area Application area Figure 2: Different parts of the display. 2.3.2 Display colormap Nokia 9210 Communicator supports 4096 colors. The normal âÂÂtrue colorâ is specified by 24 bits, 8 bits for each color component (red, green, and blue). Nokia 9200 Communicator Series uses the most significant 4 bits of each of the color component, re sulting in a color depth of 12 bits. All other colors are either dithered or mapped to the cl osest co lor available, depending on the application. Although WAP does not support colors, Nokia 9200 Communicator Series WAP browser supports image formats with colors (other than the WBMP imag e format). 2.4 WAP Browser Display There are two views in the WAP browser: the Book marks view and the Card view. The Card view consists of a rendered card, options list, and a title bar. The Bookmarks view consis ts of a hierarchical list of saved bookmarks and a title bar. Both view s have their o wn menus that provide access to the viewâÂÂs different functions. 2.4.1 Card view WML cards are displayed in the Card view. Only one ca rd of a WML deck is shown at a time. The v ertical scroll bar is visible when the vert ical length of the active card e xceeds the screen size. The horizontal scroll bar is visible when a table or a non-br eaking paragraph e xceeds the scree n width. On the left side of the card is an options list, wh ich lists all currently active do element labels. The narrow indicator area and CBA are v isible unless in full scre en mode. The user can switch focus between the card and t he options list wit h the tab key and the left and right arrow keys. The browser remembers the focus on both the Card an d the options list. For example, if the focus on a card is on an anchor and th e user focuses on the options list and then returns the focus to the Card, WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 7
Forum.Nokia.com the focus is automatically set on that same anchor. The same applies to the options list. The browser also remembers whether t he focus was on the card o r on the options list if th e user initiates a task that causes another card to be loaded. Once the ne w card has been displ ayed, the focus is set on the card area if it had focus bef ore the action. If the us er had focused on the options l ist before the action, it remains focused after the card has been displayed. The focus on the options lis t is on the first item after the card has been fetched. T he focus is not moved after a refresh task, however. The first button is a context sensitive â actionâ button, that is, when a select or an anchor element is focused, the 1 st CBA will be "Select". If no app ropriate element has been selecte d, the button label is dimmed. The first CBA button is always the def ault button in the card v iew and may be launched by pressing <ENTER>. 2.4.2 Bookmarks view In the Bookmarks view, the user creates and ma nages WAP connectio ns. The Bookmarks view is opened when the browser is laun ched without an URL. The user can switch to the Bookmarks v iew from the Card view by sel ecting the 3 rd CBA button, Bookmark. The Bookmarks view consists of a hierarchical list of s aved bo okmarks, and a title bar. When the user focuses on a bookmark, its URL will be displayed in an info message. The URL address may be abbreviat ed, that is, part of the path name ma y be replaced with three dots, if necessary. The first and the last components of the URL (that is, th e domain name and the fil e name) are visible. If there is no space fo r both the first and t he last component of the URL, the first one is display ed and the URL is simply truncated. If the scheme of the URL is different than âÂÂhttp://âÂÂ, it is displayed before the domain. Only one bookmark item (a co nnection bookmark or a fol der) can be selected at a time. Zooming is not possible in Bookmarks view. The first CBA button is always the defau lt button in the Bookmarks view and may be launch ed by pressing <ENTER>. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 8
Forum.Nokia.com 3 Nokia 9210 Communicator User Interface Elements of WML 3 Nokia 9210 Communicator User Interface Elements of WML This chapter describes ho w to use WML in desi gning serv ices aimed at Nokia 9200 Communicator Series. It gives an overview of the graphical us er interface elements and th eir WML capabilities supported by the browser. The document does not include all possible WML el ements and attributes. Nokia 9200 Communicator Series supports WML v1.1. This chapter describes ho w to use WML in desi gning serv ices aimed at Nokia 9200 Communicator Series. It gives an overview of the graphical us er interface elements and th eir WML capabilities supported by the browser. The document does not include all possible WML el ements and attributes. Nokia 9200 Communicator Series supports WML v1.1. The elements are briefly de scribed and shown in sa m ple pictures and WML code. The code examples include only the essential part in using th e elements, that is, the document prologue is not shown. The elements are briefly de scribed and shown in sa m ple pictures and WML code. The code examples include only the essential part in using th e elements, that is, the document prologue is not shown. 3.1 Browser Display 3.1 Browser Display Options list Options list Card name Card name Ti tle bar Ti tle bar Card Card Command button area Command button area Figure 3: WML browser C ard view with diffe rent display areas. Nokia 9200 Communi cator Series has a high qu ality active mat rix display, with 640 x 200 pixels and 4096 colors. As pixel size is smaller than in laptop s, the screen is sharper. In the WAP browser, the application area is divide d as follows: 30 pi xels title bar on th e top, a WML rendering ar ea, and an options list on the left side. The wi dth of options list is 100 pi xels, but it is displayed only if there are active do elements on the card. So, de pending on th e presen ce of options list, the WML rende ring area width is between 390 an d 490 pixels. The dim ensions in full screen mode are 525 and 62 5 pixels. The height is always 165 pixels. The vertical scroll bar is visible when the vertical length of the active card exceeds the screen size. The horizontal scroll bar is visible only when a tabl e or a non-bre aking paragraph exceeds the screen width. On the left side of the card is the options list, which lists all curre ntly active do element label s with their possible icons and ho tkeys. The narrow indica tor area and CBA are visible u nless in full screen mode. The user can switch focus between the card and the options list with the t ab key. The title bar is divided in two parts. On t he left, the ti tle of the card is shown. On the right, the title of the active element is shown. If both title s are too lo n g to fit the title bar, th e title of the active element is displayed as whole and th e title of the card is trun cated or, both of them are t runcated. If there is no card name, the URL is displayed inste ad. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 9
Forum.Nokia.com 3.2 Formatting Elements The table below contains all text layout-formatting ele ments. These are described in more details in this chapter later o n. Element Formatting em Italics font of color red Strong Bold, italics font of color green b Bold font I Italics font U Underlined font Big Font size is set to big Small Font size is set to small P A paragraph break is inserted in the text Br A line break is in serted in the text Table 1: Text layout fo rmats. 3.2.1 Text formatting Figure 4: Card demonstrating text-for matting elements. The browser supports all te xt formatting elements of WML. Emph asis and strong elements are shown in colors. The picture above demonstrat es how different formatting elements are rende red as text, also specified in th e table above. <wml> <card id="text" title="Text formatting elements"> <p align="center"> This card demonstrates the formatting elements:<br/> </p> <p align="right"> <b>bold,</b><br/> <u>underline,<i>italic,<b>bold,</b></i></u><br/> <big>big,<u>underline,<i>italic,<b>bold,</b></i>< /u> </big><br/> <small>small,<u>underline,<i>italic,<b>bold,</b>< WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 10
Forum.Nokia.com /i> </u></small><br/> <em>emphasis,<i>italic,</i><u>underline,</u></em> <br/> <strong>strong,<I>italic,</i><u>underline,</u> </strong><br/> </p> <do type="prev"> <prev/> </do> </card> </wml> Example 1: Text formatting elements. 3.2.2 Paragraph Paragraph <p> determines the text groups. A new para graph alway s starts on a new line. Text inside a paragraph can be aligned to the left , center, or right, but left alignment is used by default. Alignment is determine d in paragr aph attributes (fo r example, <p align="right" >). 3.2.3 Line Break New lines in text can be defined by the line break elem ent <br>. The <br> element can be used within other elements as long as it belongs to a paragraph. 3.2.4 Fieldset The fieldset element can be used for grouping eleme nts. It implies a paragraph bre ak between the elements, and the title of the element is used as the active elementâ s title if it has no title of its own. Note that fieldset title is not supported f or text, that is, text in a card can not be given a title by using fieldset element. 3.3 Tables Figure 5: A sample table. A table element <table>, and its cont ent elements <tr> an d <td > are used to create columns and rows of text and images in a ca rd surrou nded by a gray border. Table elements do not specify column or intercolumn widths; the width of the column is same as the width of the widest cell in the column. If there is a title attribute o n the table element, it w ill be rendered as the first row of the table, with a bold font and white font color on a blue backgroun d. There can be multipl e tables in one card. A line WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 11
Forum.Nokia.com break is inserted before and after each table. Th e table may also contain images and links, which are focused from left to right and from top to bottom order. The maximum nu mber of columns in a table is 30. All cell contents of t ables over 30 columns are rendered in the l ast column of the table. <wml> <card id="card1" title="Table element"> <p> <table columns="4" align="LCCL" title=Weather Forecast> <tr> <td><b>Date</b></td><td><b>F'cast</b></td><td><b>T° C </b></td><td><b>Description</b></td> </tr> <tr> <td>M 6/7</td><td><img src="rainy.gif" alt="rain" width="30"/> </td><td>Hi 20°C, Lo 3°C</td><td>Rainy</td> </tr> <tr> <td>T 6/8</td><td><img src="partcldy.gif" alt="part cldy" width="30"/></td><td>Hi 25°C, Lo 15°C</td> <td>Partly cloudy</td> </tr> <tr> <td>W 6/9</td><td><img src="cloudy.gif" alt="cloudy" width="30" /></td><td>Hi 22°C, Lo °C</td><td>Cloudy</td> </tr> <tr> <td>T 6/10</td><td><img src="rainy.gif" alt="rainy" width="30" /></td><td>Hi 20°C, Lo 3°C</td><td>Rainy</td> </tr> <tr> <td>F 6/11</td><td><img src="sunny.gif" alt="sunny" width="30" /></td><td>Hi 28°C, Lo 0°C</td><td>Sunny</td> </tr> </table> </p> <do type="prev"> <prev/> </do> </card> </wml> Example 2: Table element. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 12
Forum.Nokia.com 3.4 Images, Links, and Timers 3.4.1 Img â Images Figure 6: Different types of imag es. In addition to WBMP image format Nokia 9210 Co mmunicator suppo rts all the most commonly know image formats. Note: some WAP Ga teways may not support all these con tent types. Nokia WAP Gateway products su pport all these conte nt types listed here: ⢠a WBMP (Wireless Bitm ap), "image/vnd.wap.wbmp" ⢠a JPEG File (incl. progress ive), ".JPG", "image/jpeg" ⢠a GIF file, ".GIF", "image/gif" ⢠a PNG file, ".PNG", "im age/png" The image element is used for displaying an imag e in a card. The maximum image size is 64 KB. Although there are no absolute limits to an image' s physical measurements. However, for taller images, the user must scroll down and f or images wider than the browser area, images are scale d down to fit the screen. I mages can also be use d inside a table and as links (see Example 4). The img element should have width an d height attribut es defined in pixels. If either one or both of the width and height attributes hav e been defined in pixels, they are us ed as the size of the image and the pla ceholder. A fetche d image is scal ed to fit the spec ified size. Width and height attri bute values specified in pe rcentages a re ignored. An image is always forced into the horizontal spa ce availabl e. That is, if t he image is wider than the screen, it will be scaled (width and height un iformly) to fit the ho rizontal space available. If the horizontal m argin (hspace) or ve rtical marg in (vspace) has been def ined for the img el ement, the number of pixels specif ied are left as a m argin between the surrounding text f low and the image. Again, hspace and vspa ce specified in per centages are ignored. When the user focuses on an image and it has not been (completel y) fetched and is not inside an anchor element, the first CBA butto n will change to "Lo ad Image". If the user selects it, the image will be fetched and displ ayed as it arrives f rom the network (or cache). If the image is inside an anchor or A element, the anchorâÂÂs UI behaviour will override the imageâÂÂs beh aviour. If the user focuses on a completely loaded image, or if the focus is on an image that is being fetched and the fetch is completed, the first CBA button will ch ange to "Save Image". If the user presses it, the standard Save As dialog box opens and the use r can save the i mage in its orig inal format ( WBMP). <wml> <card id="card1" title="Image element"> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 13
Forum.Nokia.com <p> Format:GIF <img src="games.gif" alt="Games"/> JPEG<img src="ClubN.jpg" alt="ClubNokia"/> <br/> Stretched JPEG:<img src="N6210.jpg" alt="Nokia 6210 - Streched!" width="150"/> </p> <do type="prev"> <prev/> </do> </card> </wml> Example 3: Image element. 3.4.2 Anchors A and anchor elements s pecify the head of links to an other card or deck, for exampl e. A link provides easy navigation through an application. An anchor may consist of text, an image, or a combin ation of text and an image. The < a> element is a short form of the anchor elemen t. In general it is recommended to use t he < a> element instead of anchor where possible. An u nselected anchor is rende red as under lined (an im age is frame d), wh ile the color of a selected anchor is inverted. Figure 7: Text and image links. An i mage within a table selected. <wml> <template> <do type="prev" label="go"> <prev/> </do> </template> <wml> <card id="card1" title="Anchor element"> <p> Here's a  <a title="Link to Products">link<go href="#products"/></a>  to another card. Tables can contain links and an image can be a link, too. <a title="Link to Nokia Group" href="#group"><img src= "Nokia_n1.gif" alt="nokia"/></a> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 14
Forum.Nokia.com </p> <p align="right"> <table columns="2" title="Weather Forecast"> <tr> <td>Monday 6/7</td> <td><a title="See more about the weather..." href="#rain"> <img src="rainy.gif" alt="rainy" width="30"/></a></td> </tr> <tr> <td>Tuesday 6/8</td> <td><img src="sunny.gif" alt="sunny" width="30"/></td> </tr> <tr> <td>Wednesday 6/9</td><td><img src="partcldy.gif" alt="part cldy" width="30"/></td> </tr> <tr> <td>Thursday 6/10</td> <td><img src="cloudy.gif" alt="cloudy" width="30"/></td> </tr> <tr> <td>Friday 6/11</td><td><img src="rainy.gif" alt="rainy" width="30"/></td> </tr> </table> </p> </card> </wml> Example 4: Anchor element. 3.4.3 Timer The timer element def ines a card timer, which processe s inactivity or idle time. Timer s tarts the count immediately after the card is loaded. This element can be used only o nce in card and its unit is 1/10 s. 3.5 Dynamic Buttons 3.5.1 Do elements The do element binds a task to a user act ion, which ca n be executed in an options list on the left side of the screen. The options list contains all curr ently access ible do elements (options). The text representing each do el ement is the do elementâÂÂs l abel attribute value, or if it has not been defined, the UI string corresponding to the elemen tâÂÂs type attribute value. The labels are updated with current values whenever a refresh task is executed but th e focus in a list is not changed. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 15
Forum.Nokia.com Figure 8: Do elements in an option s list. The options list is focused. Each WML deck can have a template el ement. The template contains do elements that are to be displayed on each card of the deck. A cardâÂÂs do eleme nts can either override or hide the templateâÂÂs do elements. Hidden do eleme nts will not be shown. The order of the cardâÂÂs do elements in the options li st is the same as in which they are defined o n the card, unless they override the templat eâÂÂs do elements. The templateâÂÂs do elements are l ast on the options list, that is, after all t he cardâÂÂs do elements . If a do element on a card overrides the do element on a template, the cardâÂÂs do element replaces the templateâÂÂs do element in the list. All optional do elements are displayed. Do elements of the type âÂÂprevâ are handled as an exce ption. (See section 3. 5.2) <wml> <template> <do type="accept" name="news" label="News"> <go href="http://.../news.wml"/></do> <do type="accept" name="contactus" label="Contact us"> <go href="http://.../contact.wml"/></do> <do type="accept" label="Help" name="helphelp" optional="false"> <go href="http://.../help.wml"/></do> </template> <card id="form" title="Registration Form"> <p> Company Information<br/> </p> <p align="right"> <small>Company name:</small> <input name="company" type="text" title="Company name" format="*A" emptyok="false" size="25"/><br/> <small>Street address:</small> <input name="address" type="text" title="Street address" emptyok="false" size="25"/><br/> <small>Postal Code:</small> <input name="code" type="text" title="Postal code" emptyok="false" size="25"/><br/> <small>City:</small> <input name="city" type="text" title="City" emptyok="false" size="25"/><br/> <small>Country:</small> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 16
Forum.Nokia.com <select name="country" multiple="true"> <option value="-">-</option> <option value="Australia">Australia</option> <option value="Canada" size="25">Canada</option> <option value="Denmark">Denmark</option> <option value="Finland">Finland</option> <option value="France">France</option> <option value="Germany">Germany</option> <option value="Italy">Italy</option> </select> </p> <do type="accept" label="Enter" optional="false"> <go href="#confirm" method="get" sendreferer="false"/> </do> <do type="prev" label="Back" optional="false"> <prev/> </do> </card> </wml> Example 5: Do element - options list items. 3.5.2 Prev type do e lements Whenever a new card is shown, a new history l ist item is created. When activating the prev task on a WML card, the target URL is the p revious history list item and the current card (in which p rev was activated) is n ot retained in the h istory list (the re is no "forward" funct ion). Do elements of the type âÂÂprevâ are handl ed as an exception to other types of do elements (see s ection 4.5.1). If there is only on e "prev" type do element active, it is not shown on the o ptions list. Instead, it is bound to the 2 nd CBA button and it is labelled as "Back". The 2 nd CBA is dimme d if there is zero o r more than one "prev" ty pe do element active and do elements are displayed on th e options list like all other do elements. It is likely that most pages implemen t only one do element of the type "pr ev". The author of the WAP service is always responsible for the wo rking navigation model within the service. If there is a need fo r back functionality, it should be explicitly def ined with the "prev" type do element. The WAP bro wser does not have any implicit back functionality. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 17
Forum.Nokia.com 3.6 WML Input Processing 3.6.1 Input elements Figure 9: Input element â focus is in the input box with numeric format . An input element specifies a text entry ob ject for data input. It is shown as an input box in a card. The text entered in the input element can be dete rmined by the format attribute. The format string specifies that a part icular character mu st be a number, an uppercas e character, or a lowercase character, for example. The user can enter any characters in th e input field but the ch aracters that do not currently m atch the format are drawn in red color and ar e underlined (so that incorrect spaces or missing characte rs become visible). In addition , every time the user enters a different type of input than the browser was e x p e c t i n g , a n a p p r o p r i a t e i n f o m e s s a g e i n a n " I n c o r r e c t i n p u t d i a l o g b o x " w i l l b e d i s p l a y e d . A l l characters that do m atch the format are drawn in black (normal body text color). The author can specify a m aximum length for the entr y either with the format or with the maxlength attribute. If the maximum length is reached, the inpu t element will not insert any ch aracters in the field, but will beep and disp lay an info message. The author can specify with the emptyok attribute t hat the entry must match the form at mask. If there are input elements that do h ave that requirem ent, but the entry in those elements does not match the mask (such as when the v alue is empty) an d a task is initiated ( either by a user action or timer), the Missing Input dialog box will appear. Once the user has closed the dialog box, the focus will move to the first of those input elements on the card. Note that the user can exit the card only if all input elements hav e a valid value or if the y are allowed to be em pty. <wml> <card id="Form" title="Registration Form"> <p> Please login:<br/> </p> <p align="right"> <small>User name:</small> <input name="user" type="text" title="Max. 8 char. long" format="*A" emptyok="false" maxlength="8" size="25"/><br/> <small>User password:</small> <input name="user pw" type="password" title="Max 16 char. Long" format="*A" emptyok="false" maxlength="16" size="25"/><br/> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 18
Forum.Nokia.com </p> <p> Input your birthday:<br/> </p> <p align="right"> <small>Date of birth:</small> <input name="birth" type="text" title="dd/mm/yyyy" format= "NN\/NN\/4N" emptyok="false" maxlength="14 size="25"/><br/> </p> <do type="accept" label="Enter"> <go href="#confirm" method="get"/> </do> <do type="prev" label="Back"> <prev/> </do> </card> </wml> Example 6: Input el ement â Input box. 3.6.2 Selection lists Figure 10: Simple single-selection list. Selection lists are an input element that specifies a list of options for the use r to choose from. The selection list can be either single-select ion or mult iple-selectio n element. Each option is specified by an option element. Options can be organised into groups by using th e optgroup element. A selection list is opened by focusing on the input box and pressin g the 1 st CBA button for "Change". The select list appe ars. A single-selection list has a title of the title attribut e, and if it hasn't been defined, the title displays the text "Selection" by default. A multipl e-selection list has two windows; the left one is for unselecte d items and the right one contains the selected items. The title of the non- selected items pane is the select elementâÂÂs title or if one has not been def ined, the default text displayed is "Not selected". The title of the selected items pane is "s elected". The user can switch focus between the two dialog bo xes with the tab key. If the options have been grouped with an optgroup element, the optgroup titl e will be shown as a bold item in the selection li st. All options under the optgrou p element are intended an d shown under the optgroup item. Note th at Nokia 9200 Communica tor Series o nly supports one level of optgroups. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 19
Forum.Nokia.com Optgroup on a deeper level is ignored and its options are handled as if they were under the firs t level optgroup (that is, intended as one level). Figure 11: Multiple-selection list. <wml> <card id="phones" title="Information Request"> <p align="left"> Choose your age from the list:<br/> <select title="Your age"> <option title="12-30">12-30</option> <option title="31-50">31-50</option> <option title="51-">51-</option> </select><br/> <br/>Send me more information about:<br/> <select name="models" title="Products" multiple="true"> <optgroup title="Phones"> <option>Nokia 3310</option> <option>Nokia 6210</option> <option>Nokia 9210 Communicator</option> </optgroup> <optgroup title="Accessories"> <option>Battery</option> <option>Desktop stand</option> <option>Charger</option> <option value="Headset">Headset</option> </optgroup> </select><br/> <br/>Input your name:<br/> <input name="name" type="text" title="Name" size="30"/> </p> <do type="accept" label="Enter" optional="false"> <go href="#confirm" method="get" sendreferer="false"/> </do> <do type="prev" label="Back" optional="false"> <prev/> </do> WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 20
Forum.Nokia.com </card> </wml> Example 7: Selection lists. 3.7 Titles and Labels 3.7.1 Titles A title bar is divide d in two parts, on the left is the card title and on the right is space for element titles, which are shown only when the element is focus ed. The card title is displayed con tinuously and if there is no card title, the actual URL of t he card is displayed instea d. Below is a list of element titles, which u se the righ t side of the title bar. ⢠Link, attribute "title" ⢠Image, attribute "alt" ⢠Input, attribute "title" ⢠Select, attribute "title" In addition, there are elements, which ha ve a title, bu t it is not shown on the main title bar. These are tables whose title att ribute value is show n on its own title bar, select elements title attribute value is shown on main title bar when the input box is focuse d. After opening the select list, the same title is shown on the select lists own title bar. The optgroup title attributes value is sho wn as a bold item in select list. 3.7.2 Labels The only element with a l abel attribute is the do elem ent. Cards currently accessib le do elements are listed in the options list on the left side of a pplication area, whe re their label attribute values are shown. An exception to this is the "prev" t ype do element (see sectio n 3.5.2). 3.8 Limitations 3.8.1 WML charact er sets. The WAP browser uses the character sets defined an d used in the Symbian OS platform, this includes the usage of UNICOD E as necessary. Whe re multiple characte r sets are found the reference-processing model specifi ed in Section 6.1 of the WML spec ification is use d. 3.8.2 Features not supported in W ML 1.1 â classâ attributes as describe d in the WML Specification, section 8.9. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 21
Forum.Nokia.com 4 General Usability Issues â Guidelines for Design 4.1 WML History Navigation Due to the differences in the processin g of the history between WAP and WEB, only the history processing described i n the WML specifications is fo llow ed. This means that the service p rovider has to take care of the navigation as a whole. 4.2 Validate Your WML There are several XML validators availabl e that validate your documents against WML Do cument Type Definition. It is recommended t hat authors validate their WAP pages, because invalid WML is always treated as an error and dis carded (t hat is, it is not shown to the user! ). Several XML vali dators can be found at http://www.w apdevelopers.org/xml.tpl?CAL LER=index.tpl . 4.3 Site Organization 4.3.1 Avoid âÂÂdoormatâ pages The user accesses your WAP site over a GSM data call, an d pays per second. It is not recommende d that your site begins with a âÂÂdo ormatâ page, which serves no purpose other than perhaps to greet the visitor and to displ ay a logo. It is better that your site allows users to access you r service directly. If there is a need to use a timer, it shoul d not take lo nger than ~1.5 seconds, if it takes a longer time, add a 'continue' link to give the user possibility to exit the card. 4.3.2 Automatically Detect the Browser If you are using a modern Web site hosting environment, it is possible to detect the browser as well as the language mode an d supply the correct content tr ansparently, without requirin g user interaction. Nokia 9200 Communicator Series display is larger th an normal phone displays, and thus has more possibilities that are worth taking advantage of. 4.3.3 Optimise for Size The size of the content is critical. If you have large de cks (listings, large tables, etc.), consider splitting them in multiple pa rts for faster downloadin g. As for the total downloading time, som e studies plac e an u pper limit for acceptable delay to 10 to 15 seconds, including all images, on a PC-based bro wse r. It is highly recommende d to have a response time (excludin g connection time) of less than 10 seconds in mobile environ ments. 4.3.4 Choose Descriptive Card Titles It is highly useful to give a desc riptive name for the card. It might be a goo d idea to start the title with your serviceâÂÂs name and kee p the total length of the title short. It also pays to use mean ingful URLs since the user sees the URL of the currently selected link on the screen and can use it as a navigational h elp, especially when images have not been loaded. 4.3.5 Pay Attention to the First Screenful Because of the communicator's form factor, the first (topmost) screenful of any page is the most important one. All of the often-used n avigational li nks, search fields, login screens, and bulk of the information should reside there, if at all. The user is then able to navigate fo rward before the rest of the card has been loaded, and the user do es not have to scroll the card. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 22
Forum.Nokia.com 4.3.6 Use of do elements Always use descriptive and short labels for all do elements. Favor local do elements instead of anchored links that are totally out of co ntext. Always include the prev element in each card to enable backward navigation. 4.4 Pictures, Tables, and Color 4.4.1 Avoid Useless Images Downloading images takes time, and many users may switch o ff the loading of images for more speed. Try to optimise the size of images. If you have large im ages on your site, consider using thumbnails for th e image in dex. Always provide an alte rnative text (using the ALT attrib ute of the IMG element) for images that co nvey information. Always use a null alternativ e text (ALT = âÂÂâÂÂ) for images, which do not convey information, or are used for page layout or decorative purposes only . 4.4.2 Use Reasonable Image Sizes The maximum image widt h on the WAP browser screen is 490 pixels. Images larger than th at will be automatically scaled do wn to fit the screen. Using any larger im ages than 490 pixels is a w aste of bandwidth and will slow down the service conne ct ion. A maximum size for images downloaded through data calls is about 60 KB although 30 KB is recommended m aximum. 4.4.3 Colormap WAP does not include any support for colors, but Nokia 9200 Communicator Series WAP browser supports image form ats with color (other th an the WBMP im age format). Nokia 9200 Communicator Series su pports 4096 colors. Th e true color i s specified by 24 bits, 8 bi ts for each color component (red, green, and blue). Nokia 9200 Communicator Series uses the most significant 4 bits of each part of the color compon ent, resulting in a color depth of 12 bits. All other colors will either be dithered or mapped t o the cl osest color available, depe nding o n the applicati on. When creating graphics with uniform f ills, use only the colors, which will not be dithered. Some image processing tools may be able to reduce t he size of images if you res trict the number of colors to the exact 4096 col ors supported by Nokia 9200 Communi cator Series. Do not use colors, which are too close to each other (c olors that differ only in the least significant four bits of each co lor component). This may result in the colors bein g mapped to the exact s ame color. 4.4.4 Use Reasonable Table Sizes If the table size exceeds the maximum widt h of the WAP services applicatio n screen due to the number of columns, the horizont al scroll bar will appear. Anyhow, to keep the cell content readabl e, special attention should be paid on tabl e structuring. 4.5 Use of Card Titles and Element Labels Card titles describe the co ntent of the display an d their use is re commended. They help the user to navigate because they function as a reminder of wher e the user is in the application. The header text should be determined by the item previously selected by the user. For instance, the card title âÂÂBookmarksâ tells the user that the display contains a l ist of bookmarks in the application and that the opti ons item previo usly se lected wa s Bookmarks . WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 23
Forum.Nokia.com Proportional fonts are used in head er te xts, and if the heade r text is too long, it is automati cally truncated. Truncation is usually bette r than abbrev iation, because the user might b e confused by unfamiliar abbreviat ions that are difficult to underst and. 4.6 Perform Usability Test It is always good to perform a usab ility test for new applications. People who have not been involved in the design or developme nt of the application tend to notice potential usability problems ofte n not obvious to those who know the design by heart. Usability tests should always be perfo rmed as early as possible in the development process. Any necessary changes resulting from the tests can then be implemented within the development schedule. Try to recruit users who are representat ive of the end users of the application, and try to conduct the usabil ity test on a smaller scale, if the schedule does not allow for extensive testing . WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 24
Forum.Nokia.com 5 Terms and Abbreviations Term or Abbreviation Description Card A single WML unit of navi gation and user interface. Deck A collection of WML cards th at is the smallest downloadable unit. A single car d in a deck cannot be downloaded; the entire deck must be downloaded. Service developers shoul d be aware of this, and not creat e large app licatio ns in a sing le deck. Do element A way of defining the binding between events (su ch as a user selection) and a task (for example, to go somewhere). DTMF tone Standard tone used to transmit numeric data via telephone. Generated when numeric keys are pressed. GUI Graphical User Inte rface. HTML Hypertext Markup Langua ge. The markup language used for publishing hypertext on the Wo rld Wide Web. HTTP Hypertext Transfer Prot ocol . An application-level protocol for transferring HT ML documents on t he Internet. Hyperlink A link within a documen t or card that allo ws quick navigation to another document (card). IDE Integrated Development Environ ment. A tool for application de velopers. Input element A markup element t hat allows for interaction with the user, that is, lettin g the user input te xtual values. These can be used f or inputs to lo cally stored scripts, or for parsing to origin serv ers. Multiselection list A selection list that allows the user to scroll and select several (or no) options to be active. Navigation The concept of moving between menu items, decks, and cards. Proportional font A font in which different letter widths do not necessarily have the same number of pixels. "W" an d "I" are good e xamples. SDK Software De velopment Ki t. A kit for software developers that inclu des, e.g., emulator, sampl e codes, reference docu mentation. Selection list List of user-selectable options. SIS Symbian Installation System. A system that provides a simple and consistent use r interface for installin g applications, data, or configuration information to Symbian OS devices. Symbian OS applic ations are installed to the device packag ed in installation (.sis) files. Soft key The phone has one or more function keys whose function depends on the state of the phone. These keys are called soft keys b ecause there is a n associated te xt on the display. UI User Interface. URL Uniform Reso urce Locator. String that identifies resources in the Web. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 25
Forum.Nokia.com Word wrapping Formatting rule for text appear ance. WML Wireless Mark up Language. Markup language based on Extensible Markup L anguage (XML), w hich is int ended for use in specifying cont ent and user interface for narrowband devices, including cellular phones and pagers. WSP Wireless Session Protocol. A layer of WAP stack, which is optimized for low b andwidth bearer networks with long latency. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 26
Forum.Nokia.com 6 References ⢠User's guide for Nokia 9200 Communicator Series devices, http://www.nokia.com ⢠Nokia Mobile Internet Toolk it, http://www.forum.nokia.com ⢠Nokia 9200 Communicator Series SDK for Symbian OS ( including an emulator ), http://www.forum.nokia.com ⢠Wireless application protocol specificatio ns, http://www.openmobilealliance.org WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 27
Forum.Nokia.com 7 Appendix A. Wireless Application Protocol (WAP) 7.1 Introduction The Wireless Applicatio n Protocol (WAP) is a set of protocols that allow the development of applications and services for use w ith mobile phones and othe r mobile devices. The WAP Forum maintains these protocols and their re lated standa rds and spec ifications. The WAP Forum consists of a number of high-tech companies f rom the information technology, software, and telecommunication industries. The objectives of the WAP Forum are to: ⢠Bring Internet content and advan ced data applications t o digital mobile phones ⢠Create a global wireless protoc ol specificat ion that work s ac ross different wireless network technologies ⢠Enable the creation of content and applications th at scal e across a wide range of bearer networks and device types ⢠Embrace existing standards and technology wherever possible 7.2 WAP Architecture 7.2.1 WAP and Internet ar chitecture In order to apply as much leverage to the existing Internet standard as poss ible, the WAP stack closely follows the Internet model. This is illustrated in Figu re 12. Internet HTML JavaScript TM HTTP TLS - SSL TCP/IP UDP/IP SMS USSD CSD IS-136 CDMA CDPD PDC-P Etc.. Bearers: Wireless Application Wireless A pplication Environment (WAE) Wireless Session Layer (WSP) Wireless Tran sport Layer Sec urity (WTLS) Wireless Datagram Protocol (WDP) Other Services and Applications Wireless Tra nsaction Pr otocol (WTP) Figure 12: Comparison of In ternet and WAP Architecture This layered archite cture allows applicat ions to utilise the features of the WAP stack through well- defined interf aces. This close link to the Interne t arch itecture allows develop ers to utilise their existing knowledge and expertise when develo ping applications for mobile terminals. 7.2.2 Wireless Application Environment (WAE) The Wireless Application Environ men t (WAE) is a general-purpose application environment that uses a combination of Internet and mobile terminal technology. It provides a framework for the development of applications on a mobile termin al. WAE contains support for the followin g functionality: WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 28
Forum.Nokia.com ⢠Wireless Markup L anguage (WML) - a lightweight pres entation langu age, similar to HyperText Markup Language (HTML) bu t optimised for use w ith mobile terminals. ⢠Wireless Markup Language Script (WMLS) - a lightw eight script language, similar to Java Script TM . ⢠Wireless Telephony Application / Interface (WTA / WT AI) - telephony services an d programming interfaces. ⢠Content formats - defin ed data form ats, such as vCard and vCalendar. 7.2.3 Wireless Session Protocol (WSP) The Wireless Session Protocol (WSP) pro vides the a pplication layer of WAP with an interface for two session services. The first is a co nnection-oriented s ervice that opera tes above the transaction layer protocol. The second is a connectionless s ervice that operates abov e a secure or non-secure datagram service. The WSP is optimised for lo w bandwidth bear er networks with long l atency. 7.2.4 Wireless Transport Protocol (WTP) The Wireless Transport Protocol (WTP) runs on top of the datagram service an d provides a lightweight transaction-oriente d protocol, suitable fo r use in mo bile termin als. WTP operat es over secure or non- secure wireles s datagram networks. 7.2.5 Wireless Transport Layer Security (WTLS) Wireless Transport Layer Security (WTLS) is based on the industry stan dard Transport L ayer Security (TLS) and is optimised for use over narrowband co mmunication channels. WTL S may be used for secure communicatio n between terminals, an d applications can sele ctively enable WTLS features . 7.3 Developing Applications for Mobile Browsing Application develope rs can use the prin ciples of WAP to develo p new services or adapt existing Internet applicat ions for use with mo bile terminals. Appl ications are w ritten in Wireless Markup Language (WML) and WML Script, and stored on either a nor mal Web server (origin server) o r directly on the WAP gateway. The content sto red on the Web server is accessible from mobile termin als via the cellular network and a WAP gateway or proxy. The proxy server acts as a gateway between the cellular ne twork and the Internet or Intranet. The data sent between the origin server and the handset is binary enco ded to optimise transmissio n over the narrow bandwidth of the cellul ar network. Note that the content stored on the Web server might be in either textual or binary format. When the WAP gateway fetches textual content, it automat ically compiles this to the encoded form at to minimise network load. Figure 13 sh ows the network-related elements required for dev eloping and offering se rvices to mobile users. WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 29
Forum.Nokia.com WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 30 Wireless Netw ork WA P Proxy WT A Server Binar y Binary WML HTML Filte r WML WML HTML Web Server Figure 13: Elements related to mobile browsing. Web server The Web server stores the appl ications written in WM L. Alternatively, exist ing HTML applicati ons can be used. HTML filter Any applications written in HTML will have to be conve rted to WML before they are sent to the mobile terminal. This HTML filter may form part of the Web server o r the WAP proxy. WAP proxy The WAP proxy acts as the gateway be tween the cellular network and the Inte rnet or Intranet. It encodes the information, which is to be sent to th e mobile terminal in b inary format and decodes information sent f rom the mobile terminal. WTA server The WTA server h andles network-specific applications. These applications are not discussed in this document. 7.4 Additional Information Further information on WAP is available at the Open Mobile Alliance web site, http://www.openmobilealliance.o rg.
Forum.Nokia.com Build Test Sell Build Test Sell Developing and m arketing mobile a pplications with Nokia Developing and m arketing mobile a pplications with Nokia 1 Go to Forum.Nokia.com Go to Forum.Nokia.com Forum.Nokia.com provides the tools and resources you need for con tent and application develo pment as well as the channels fo r sales to op erators, enterpris e s, and consumers. Forum.Nokia.com provides the tools and resources you need for con tent and application develo pment as well as the channels fo r sales to op erators, enterpris e s, and consumers. Forum.Nokia.com Forum.Nokia.com Download tools and emulators Download tools and emulators 2 Forum.Nokia.com/tools has links to tool s from Noki a and other industry leaders inclu ding Borland, Adobe, AppForge, Macromed ia, Metrowerks, and Sun. Forum.Nokia.com/tools has links to tool s from Noki a and other industry leaders inclu ding Borland, Adobe, AppForge, Macromed ia, Metrowerks, and Sun. Forum.Nokia.com/tools Forum.Nokia.com/tools Get documents and specifications Get documents and specifications 3 The documents area contains useful whit e papers, FA Qs, tutorials, and APIs for Sy mbian OS and Series 60 Platform, J2ME, messaging (in cluding MMS), and other technologies. Forum.Nok ia.com/devices lists detailed technical specifications for Nokia devices. The documents area contains useful whit e papers, FA Qs, tutorials, and APIs for Sy mbian OS and Series 60 Platform, J2ME, messaging (in cluding MMS), and other technologies. Forum.Nok ia.com/devices lists detailed technical specifications for Nokia devices. Forum.Nokia.com/document s Forum.Nokia.com/devices Forum.Nokia.com/document s Forum.Nokia.com/devices Test your application and g et support Test your application and g et support 4 Forum Nokia offers free and fee-b ased support that pr ovides you w ith direct access to Nokia en gineers and equipment and conne cts you with other developers around the worl d. The Nokia OK testing program enables your application to enjoy premium placement in Nokia's sales channels. Forum Nokia offers free and fee-b ased support that pr ovides you w ith direct access to Nokia en gineers and equipment and conne cts you with other developers around the worl d. The Nokia OK testing program enables your application to enjoy premium placement in Nokia's sales channels. Forum.Nokia.com/support Forum.Nokia.com/ok Forum.Nokia.com/support Forum.Nokia.com/ok Market through Nokia channels Market through Nokia channels 5 Go to Forum.Nokia.com/business to learn about all of the marketing channels op en to you, including Nokia Tradepoint, an online B2B ma rketplace. Go to Forum.Nokia.com/business to learn about all of the marketing channels op en to you, including Nokia Tradepoint, an online B2B ma rketplace. Forum.Nokia.com/business Forum.Nokia.com/business Reach buyers around the globe Reach buyers around the globe 6 Place your applications in Nokia Tradepoint an d they're available to dozens of b uying organizations around the world, ranging from leading global op erators and enterpris es to regional oper ators and XSPs. Your company an d applications wi ll also be co nsidere d for the regional Nok ia Software M arkets as well as other global and regional opportunities, including personal intro ductions to operators, on- device and in-box placement, and particip ation in invitation-only events around the world. Place your applications in Nokia Tradepoint an d they're available to dozens of b uying organizations around the world, ranging from leading global op erators and enterpris es to regional oper ators and XSPs. Your company an d applications wi ll also be co nsidere d for the regional Nok ia Software M arkets as well as other global and regional opportunities, including personal intro ductions to operators, on- device and in-box placement, and particip ation in invitation-only events around the world. Forum.Nokia.com/business Forum.Nokia.com/business WAP Service DeveloperâÂÂs Guide for Nokia 92 00 Communicator Seri es 31