Nokia SERIES 30 دليل المستخدم

ملخص المحتوى في الصفحة رقم 1

FOR U M NO KI A
WAP Service Developer's Guide for
Nokia Series 30 Phones with WML Browser
Version 1.1; June 09, 2003
Browsing

ملخص المحتوى في الصفحة رقم 2

Forum.Nokia.com Contents 1 Introduction................................................................................................................................................ 7 1.1 Chapter Topics...........................................................................................................................................7 2 Guidelines for Design..............................................................................................................................

ملخص المحتوى في الصفحة رقم 3

Forum.Nokia.com 4.1.2 Line break .................................................................................................................................15 4.1.3 Fieldset element .....................................................................................................................16 4.1.4 Pre element..............................................................................................................................16 4.2 Table ...............................

ملخص المحتوى في الصفحة رقم 4

Forum.Nokia.com Additional Information ......................................................................................................................................32 WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser 4

ملخص المحتوى في الصفحة رقم 5

Forum.Nokia.com Change History 04 Nov 2002 V1.0 Initial document release. 09 June 2003 V1.1 Template changed, Nokia 3510i and Nokia 8910i information removed. WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser 5

ملخص المحتوى في الصفحة رقم 6

Forum.Nokia.com Disclaimer The information in this document is provided ”as is,” with no warranties whatsoever, including any warranty of merchantability, fitness for any particular purpose, or any warranty otherwise arising out of any proposal, specification, or sample. Furthermore, information provided in this document is preliminary, and may be changed substantially prior to final release. This document is provided for informational purposes only. Nokia Corporation disclaims all liabil

ملخص المحتوى في الصفحة رقم 7

Forum.Nokia.com WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser Version 1.1; June 09, 2003 1 Introduction The following document provides information and practical examples for developers who want to optimize their WAP services for Nokia Series 30 devices with a WML browser. It is written for service developers as well as anyone involved in creating the wireless information society who needs to know more about service creation on mobile terminals. This gu

ملخص المحتوى في الصفحة رقم 8

Forum.Nokia.com 2 Guidelines for Design The Nokia Series 30 UI is designed to be easy to use and intuitive. The following section offers general guidelines to help developers create browsing applications that will be perceived as usable and easy to understand. 2.1 Applications for Mobile Use When deciding what information to include in various applications on a mobile terminal, developers should consider the types of situations where the mobile phone will be used. The content of the se

ملخص المحتوى في الصفحة رقم 9

Forum.Nokia.com 2.3.4 Infrastructure optimization The latency between the WAP gateway and content server should be minimized. Each query traverses this link twice, once as a request and once as a response. The WAP gateway should be placed close to the GPRS gateway. (The GPRS gateway is technically called a “Gateway GPRS Support Node,” or GGSN.) “Close” in this instance refers to both latency and the probability of packet loss. Lost messages cause additional delays due to HTTP retransmissi

ملخص المحتوى في الصفحة رقم 10

Forum.Nokia.com 2.4.5 The first screen The first (topmost) screenful of any page is the most important. All often-used navigational links, search fields, login screens, and the bulk of the information should reside there. The user can then navigate forward before the rest of the page has been loaded, and will not have to scroll the page. Wasting the top of the page on banner advertisements or non-informative graphics should be avoided. It is better to place advertisements at the left or

ملخص المحتوى في الصفحة رقم 11

Forum.Nokia.com Proportional fonts are used in header text, and if the header text is too long, it is cut automatically. Cut titles are usually better than abbreviations, because the user may be confused by unfamiliar abbreviations. Although short words are recommended for element labels, acronyms that are not well known by the target user group should be avoided. The same label should always be used for the same thing, especially with function labels such as Delete, Remove, Erase, Clear,

ملخص المحتوى في الصفحة رقم 12

Forum.Nokia.com 3 Introduction to the User Interface The following chapter offers a brief overview of the user interface style in 96 x 65 pixel screen resolution phones. The main focus is on the WAP services element (WAP browser) of the phone. The WAP browser user interface is designed to comply with the user interaction handling known from other applications in the phone. The user interface style is a combination of specific user interface hardware such as keys and display; user intera

ملخص المحتوى في الصفحة رقم 13

Forum.Nokia.com Figure 1: Structure of the browser screen The application area is 96 pixels (horizontal) by 45 pixels (vertical). It includes four lines of main text and can also be used for displaying graphics, which can be scrolled four ways (picture viewer) until the maximum deck size. 3.2.2 Keys in Two Soft Key User Interface The Send/Talk key works as a selection key. The End key exits a data call/GRPS connection and goes into idle state when pressed twice. The two soft keys are

ملخص المحتوى في الصفحة رقم 14

Forum.Nokia.com an input element is used in the editor title. The label of a do element is used in the Service options behind the Options soft key. 3.6 Scrolling The user can move up and down in a card view when it contains elements (hotlinks, input elements, and selection list items) and static text areas between them. This is done by ”jumping” from element to element. Scrolling through long static sections (that is, text lines) is done line by line. The first element of a card is high

ملخص المحتوى في الصفحة رقم 15

Forum.Nokia.com 4 WML Elements for the Nokia User Interface This chapter serves as a guide for using WML in designing services. It provides an overview of graphical user interface elements, that is, the WML elements that are critical from the rendering point of view and their WML capabilities supported by the browser. The document does not include all possible WML elements and attributes. WAP service developers should pay special attention to Sections 4.2: Table and 4.3: Images. The WML

ملخص المحتوى في الصفحة رقم 16

Forum.Nokia.com 4.1.3 Fieldset element The fieldset element allows the grouping of related fields and text. The basic idea of grouping is to show the grouped items on the same display if possible. If the items cannot be displayed on the same display, the user is not given any notification. Fieldset always starts a new line and ends with a line break. 4.1.4 Pre element The pre element is supported. When the pre element is used, the content shown is rendered as “preformatted” to the exte

ملخص المحتوى في الصفحة رقم 17

Forum.Nokia.com 27°C W 6/9 24°C T 6/10 28°C F 6/11

ملخص المحتوى في الصفحة رقم 18

Forum.Nokia.com 4.3.1 Animated GIF 1 Most recent Nokia browsers support image format animated gif (.gif 89a). The maximum number of frames allowed is 13 (note, maximum file size is 2.4 kb). The animation can be viewed in the browser view. After running the animation in looping mode for 50 loops the animation will stop. The last frame of the animation will be shown as a static gif. 4.4 Links The anchored link element specifies a hotlink. Links are underlined; in Nokia 3510i links are di

ملخص المحتوى في الصفحة رقم 19

Forum.Nokia.com Static text Type Accept OK Prev Back Help Help Reset Reset Options Options Delete Erase Unknown Unknown Table 1: do elements label default text 4.5.1 Prev task The author of the WAP service is always responsible for the working navigation model inside its own service. If there is a need for back functionality, it should be explicitly defined with the prev type do element. The WAP browser does not have any implicit back functionality. 4.5.2 Cardwide and deckwid

ملخص المحتوى في الصفحة رقم 20

Forum.Nokia.com

Please, register
Username: أدلة المستخدم البديلة