hit counter script
Nokia 6210 Developer's Manual
  1. Manuals
  2. Brands
  3. Nokia Manuals
  4. Cell Phone
  5. NAVIGATOR 6210
  6. Developer's manual
Nokia 6210 Developer's Manual

Nokia 6210 Developer's Manual

Wap service developer's guide
Hide thumbs Also See for 6210:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Service Manual, User Manual
1 (29)
Developer's
WAP Service
Guide for Nokia 6210 and Nokia 6250
October 2000

Advertisement

Table of Contents
loading

Related Manuals for Nokia 6210

Summary of Contents for Nokia 6210

  • Page 1 1 (29) Developer's WAP Service Guide for Nokia 6210 and Nokia 6250 October 2000...
  • Page 2 Nokia Mobile Phones Limited does not warrant or represent that such use will not infringe such rights. Nokia Mobile Phones Limited retains the right to make changes to this specification at any time without notice. License: A license is hereby granted to download and print a copy of this specification for personal use only.

  • Page 3: Table Of Contents

    Introduction ................................... 6 WAP Architecture ................................. 6 Developing Applications with WAP ..........................7 Further Information ................................8 INTRODUCTION TO THE USER INTERFACE OF THE NOKIA 6210..................9 Keypad - detailed description............................9 Display - detailed description............................9 WAP Browser Display.................................10 NOKIA 6210 USER INTERFACE ELEMENTS OF WML......................14...

  • Page 4: Introduction

    We at Nokia are very proud of our user interfaces and we have put a lot of effort into constantly improving them. In this guide we have collected a lot of what we have learned to help developers improve their services.
  • Page 5 5 (29) Terminology Display The word ‘display’ refers to the 4 lines of text (not including the Header text) that are visible at the same time in one view. You move from one display to another by rolling the roller down 4 times. Card A single WML unit of navigation and user interface.

  • Page 6: Wireless Application Protocol - Wap

    6 (29) 2. WIRELESS APPLICATION PROTOCOL - WAP 2.1 Introduction The Wireless Application Protocol (WAP) is a set of protocols that allow the development of applications and services for use with Mobile Phones and other mobile devices. These protocols and their related standards and specifications are maintained by the WAP Forum.

  • Page 7: Developing Applications With Wap

    7 (29) Wireless Mark-up Language (WML) - a lightweight presentation language, similar to HyperText Mark- up Language (HTML) but optimized for use with mobile terminals. Wireless Mark-up Language Script (WMLS) - a lightweight script language, similar to Java Script Wireless Telephony Application/Interface (WTA/WTAI) - telephony services and programming interfaces. Content Formats - defined data formats, such as vCard and vCalendar.

  • Page 8: Further Information

    8 (29) Figure 2 – Network-Related Elements for WAP Applications Web Server : The Web Server stores the applications written in WML. Alternatively, existing HTML applications can be used. HTML Filter : Any applications written in HTML will have to be converted to WML before they are sent to the mobile terminal.

  • Page 9: Introduction To The User Interface Of The Nokia 6210

    3.2 Display - detailed description The Nokia 6210 display is a full dot matrix display with a display resolution of 96 pixels (horizontal) by 60 pixels (vertical). The display consists of the application area with header text and the area used for...

  • Page 10: Wap Browser Display

    3.2.2 Display Fonts Font size in the Nokia 6210 is 8 pixels plus 2 pixels line break. All fonts used in the Nokia 6210 are proportional fonts. Proportional fonts give a dynamic and minimized width for each character, they give improved readability of the display texts, and they generally allow more characters to be displayed per line.
  • Page 11 Do-elements), and also ‘fixed’ browser options (Bookmark handling, etc). The contents and ordering of the options are listed below and are followed by a more detailed description of the fixed browser options. Context-sensitive options are included in chapter 5. Nokia 6210 user interface elements of WML.
  • Page 12 3.3.3 Bookmark handling The Bookmark handling of the Nokia 6210 is entered using the Bookmarks item contained under the options in the left soft key, Options. The user can save URLs as bookmarks while browsing on that page, by adding them manually or by saving a bookmark that has been sent as an over the air message. The maximum amount of bookmarks that can be stored is 15.
  • Page 13 13 (29) The user can scroll through the list using the scrollkey and select a number by pressing the Select-soft key. Selecting a number will exit the browser and paste the number into the normal phone Standby Mode. From the Phone Standby Mode, the user can call the number, save it or send a short message directly to it.

  • Page 14: Nokia 6210 User Interface Elements Of Wml

    4. NOKIA 6210 USER INTERFACE ELEMENTS OF WML This chapter is a guide to using WML in designing services specifically for the Nokia 6210. It is an overview of the graphical user interface elements, i.e. the WML elements that are critical for the rendering point of view and their WML capabilities supported by the browser.
  • Page 15 15 (29) Figure 4-2 Text and image aligning Example 4-1 Align <align> <wml> <card id="card1" title="Align" ordered="true" newcontext="false"> <p align="center"> Align &quot;center&quot; </p> <p align="right"> Align &quot;right&quot; </p> <p align="right"> <img alt="8210" src="file:///C|/USERS/wml/8210.wbmp" align="top" hspace="0" vspace="0"/> </p> <do type="previous" label="Back" optional="false"> <prev/>...
  • Page 16 16 (29) Figure 4-3 Line break in text Example 4-2 Line break <br> <wml> <card id="card1" title="Break" ordered="true" newcontext="false"> <p align="left"> Here's a page containing only plain text. <br/> Text-pages may sometimes be longer than 4 lines </p> <do type="previous" label="Back" optional="false"> <prev/>...
  • Page 17 17 (29) Figure 4-4 Figure 4-5 Figure 4-6 Example 4-3 <table> <wml> <template> <do type="previous" label="Back"> <prev/> </do> </template> <card id="card1" title="Weather Forecast"> <p align="left"> <table align="LCC" columns="3"> <tr> <td>Date</td> <td>F'cast</td> <td>T °C</td> </tr> <tr> <td> <anchor title="date">M 6/7 <go href="#date" method="get" sendreferer="false"/> </anchor>...

  • Page 18: Images, Links And Timers

    (used as an attribute) is shown on the screen during the load time or if the image cannot be displayed at all. However, in the Nokia 6210, showing images is optional and can be turned off in the browser's appearance settings. Image sizes can be 1.3 Kb or less; there are no actual limits to the physical measurements of an image;...
  • Page 19 <card id="card1" title="Images"> <p align="center"> A small image <img alt="part cldy" src="file://…/partcldy.wbmp"/> displayed with text </p> <p align="center"> <img alt="8210" src="file:///C|/USERS/6210doku/WML/8210.wbmp"/> <img alt="nokia" src="file:///C|/USERS/6210doku/WML/120nokia3.wbmp"/> </p> <do type="previous" label="Back" optional="false"> <prev/> </do> </card> </wml> 4.2.2 Anchors Use the <anchor> element to create a link. A link provides easy navigation through an application...
  • Page 20 </anchor>or an image </p> <p align="center"> <anchor> <img alt="part cldy" src="file://…/partcldy.wbmp"/> <go href="#card2"/> </anchor> </p> </card> <card id="card2" title="Link2"> <p align="left"> Did you know that in the Nokia 6210 links can be placed inside a table as well! </p> </card> </wml>...

  • Page 21: Wml Do Construct

    21 (29) 4.2.3 Timer The timer element declares a card timer, which exposes a means of processing inactivity or idle time. This element can be used only once in a card and its unit is 1/10s. 4.3 WML DO Construct The <do>...
  • Page 22 22 (29) 4.3.2 Do element The do element can be expressed in two ways: in card wide scope (like 'Enter' in Example 3-7) or in deckwide scope as in the template (like 'Ask Help', 'Contact' and 'Back' in Example 3-7). Do elements will be stored in the browser’s options list together with the preloaded options (Figure 4-13).

  • Page 23: Wml Input Processing

    23 (29) 4.4 WML Input processing Input processing enables the user to input requested information into the service. There are two kinds of input elements: text fields determined by input-elements and selection lists determined by select- elements. Option elements are used to specify a single choice option in a select element. Option elements can be grouped by using the optgroup-element (see Example 4-7).
  • Page 24 Figure 4-18 Selecting from the group 'Accessories' using an optgroup list. Example 4-9 Select and optgroup <wml> <card id="phones" title="Information Request"> <p align="left"> Send me more information about: <select name="models" title="Products" multiple="true"> <optgroup title="Phones"> <option value="Nokia 8210"> 8210 </option> <option value="Nokia 7110"> 7110 </option> <option value="Nokia 6110"> 6210...

  • Page 25: Labels And Titles

    The label of a <do> element is used in the Service options behind the 'options'-soft button. 4.6 Limitations This section includes the technical limitations of the WAP services application. The total cache size in the Nokia 6210 is 50 Kb.
  • Page 26 26 (29) The maximum item size is about 1.3 kilobytes binary. This is the maximum size both for an encoded WML deck and for an image. The WML deck and images are downloaded separately. 4.6.1 Rendering Limitations Emphasis tags are not supported Links are always on their own line Images are always on their own line Input fields are always on their own line...

  • Page 27: General Usability Issues - Guidelines For Design

    5. GENERAL USABILITY ISSUES – GUIDELINES FOR DESIGN Nokia phones are renowned for their ease of use and intuitive user interface. In order to create a service that will be perceived as usable and easy to understand, Nokia Mobile Phones provides some general guidelines to help service providers develop their applications.

  • Page 28: Pictures, Tables And Colour

    28 (29) 5.3.4 Choose Descriptive Card Titles It is very useful to give a descriptive name to the card. It might be a good idea to start the title with your service’s name and keep the total length of the title short. It also pays to use meaningful URLs since the user sees the URL of the currently selected link on the screen and can use it as a navigational aid, especially when images have not been loaded.

  • Page 29: Use Of Card Titles And Element Labels

    29 (29) 5.6 Use of card titles and element labels Card titles describe the content of the display and their use is recommended. They help the user to navigate in the application because they function as a reminder of where the user is in the application. The header text should be determined by the item previously selected by the user.

This manual is also suitable for:

6250

Table of Contents