DOCSLIB.ORG

WAP Service Developer´S Guide for Nokia 9200 Communicator

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
WAP Service Developer´S Guide for Nokia 9200 Communicator FORUM NOKIA WAP Service Developer’s Guide for Nokia 9200 Communicator Series Version 1.0; March 03, 2003 Browsing Forum.Nokia.com Contents 1 Introduction .........................................................................................................................................................5 2 Introduction to the User Interface of Nokia 9200 Communicator Series ...........................................6 2.1 WAP Browser Technical Features ..............................................................................................................6 2.2 Keypad................................................................................................................................................................6 2.3 Display - Detailed Description.....................................................................................................................6 2.3.1 Overview ...........................................................................................................................................6 2.3.2 Display colormap............................................................................................................................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 WML.................................................................9 3.1 Browser Display...............................................................................................................................................9 3.2 Formatting Elements ..................................................................................................................................10 3.2.1 Text formatting............................................................................................................................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 Timers.........................................................................................................................13 3.4.1 Img – Images................................................................................................................................13 3.4.2 Anchors...........................................................................................................................................14 3.4.3 Timer ...............................................................................................................................................15 3.5 Dynamic Buttons..........................................................................................................................................15 3.5.1 Do elements ..................................................................................................................................15 3.5.2 Prev type do elements...............................................................................................................17 3.6 WML Input Processing ................................................................................................................................18 3.6.1 Input elements.............................................................................................................................18 3.6.2 Selection lists................................................................................................................................19 3.7 Titles and Labels...........................................................................................................................................21 3.7.1 Titles ................................................................................................................................................21 3.7.2 Labels ..............................................................................................................................................21 3.8 Limitations .....................................................................................................................................................21 3.8.1 WML character sets.....................................................................................................................21 3.8.2 Features not supported in WML 1.1 ......................................................................................21 4 General Usability Issues – Guidelines for Design..................................................................................... 22 4.1 WML History Navigation ............................................................................................................................22 WAP Service Developer’s Guide for Nokia 9200 Communicator Series 1 Forum.Nokia.com 4.2 Validate Your WML.......................................................................................................................................22 4.3 Site Organization .........................................................................................................................................22 4.3.1 Avoid ‘doormat’ pages...............................................................................................................22 4.3.2 Automatically Detect the Browser.........................................................................................22 4.3.3 Optimise for Size..........................................................................................................................22 4.3.4 Choose Descriptive Card Titles ................................................................................................22 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 Useless Images.................................................................................................................23 4.4.2 Use Reasonable Image Sizes ...................................................................................................23 4.4.3 Colormap........................................................................................................................................23 4.4.4 Use Reasonable Table Sizes .....................................................................................................23 4.5 Use of Card Titles and Element Labels...................................................................................................23 4.6 Perform Usability Test................................................................................................................................24 5 Terms and Abbreviations............................................................................................................................... 25 6 References.......................................................................................................................................................... 27 7 Appendix A. Wireless Application Protocol (WAP).................................................................................. 28 7.1 Introduction...................................................................................................................................................28 7.2 WAP Architecture .........................................................................................................................................28 7.2.1 WAP and Internet architecture...............................................................................................28 7.2.2 Wireless Application Environment (WAE)............................................................................28 7.2.3 Wireless Session Protocol (WSP) ............................................................................................29 7.2.4 Wireless Transport Protocol (WTP)........................................................................................29 7.2.5 Wireless Transport Layer Security (WTLS)...........................................................................29 7.3 Developing Applications for Mobile Browsing ...................................................................................29 7.4 Additional Information..............................................................................................................................30
Load more

Recommended publications
  • Palm Security WP.Qxd
    Palm® Mobility Series: Security Smartphone and handheld security for mobile business. Mobile computing: Opportunities and risk By providing professionals with convenient mobile access to email, business applications, customer information and critical corporate data, businesses can become more productive, streamline business processes and enable better decision making. With the new ease of access to information comes a responsibility to protect the organization's data as well as the investment in mobile devices. In many ways, security risks for mobile computing are similar to those for other computing platforms. There are the usual concerns of protecting data, authenticating users, and shielding against viruses and other malicious Contents code. But because of their mobility and compact size, smartphones and handhelds present some additional challenges: Mobile computing: Opportunities and risk...................................................... 1 Know thy enemy: Security risks...................................................................... 2 • Smartphones and handhelds are more easily lost or stolen than Theft and loss ............................................................................................ 2 laptop or desktop computers. Password cracking .................................................................................... 2 Data interception ...................................................................................... 2 • Users often treat smartphones and handhelds as personal devices Malicious code
    [Show full text]
  • Nokia Phones: from a Total Success to a Total Fiasco
    Portland State University PDXScholar Engineering and Technology Management Faculty Publications and Presentations Engineering and Technology Management 10-8-2018 Nokia Phones: From a Total Success to a Total Fiasco Ahmed Alibage Portland State University Charles Weber Portland State University, [email protected] Follow this and additional works at: https://pdxscholar.library.pdx.edu/etm_fac Part of the Engineering Commons Let us know how access to this document benefits ou.y Citation Details A. Alibage and C. Weber, "Nokia Phones: From a Total Success to a Total Fiasco: A Study on Why Nokia Eventually Failed to Connect People, and an Analysis of What the New Home of Nokia Phones Must Do to Succeed," 2018 Portland International Conference on Management of Engineering and Technology (PICMET), Honolulu, HI, 2018, pp. 1-15. This Article is brought to you for free and open access. It has been accepted for inclusion in Engineering and Technology Management Faculty Publications and Presentations by an authorized administrator of PDXScholar. Please contact us if we can make this document more accessible: [email protected]. 2018 Proceedings of PICMET '18: Technology Management for Interconnected World Nokia Phones: From a Total Success to a Total Fiasco A Study on Why Nokia Eventually Failed to Connect People, and an Analysis of What the New Home of Nokia Phones Must Do to Succeed Ahmed Alibage, Charles Weber Dept. of Engineering and Technology Management, Portland State University, Portland, Oregon, USA Abstract—This research intensively reviews and analyzes the management made various strategic changes to take the strategic management of technology at Nokia Corporation. Using company back into its leading position, or at least into a traditional narrative literature review and secondary sources, we position that compensates or reduces the losses incurred since reviewed and analyzed the historical transformation of Nokia’s then.
    [Show full text]
  • Symbian Smartphones for the Enterprise
    Symbian Smartphones for the Enterprise Working without boundaries The growth of wireless computing belongs to the smartphone, a powerful device that extends the superb voice functionality of a mobile phone into the realm of data communications. From inception, it has been Symbian’s mission to supply operating systems that enable a mass market for enhanced communications and information services based on mobile phones. Already, Symbian OS is the industry’s standard choice for feature-rich phones that not only can handle calendars, contacts, messaging, email and Web browsing, but that can also integrate with virtually any enterprise information system. Though the market has already embraced smartphones, with over ten million of them sold in 2003, most people don’t fully grasp the impact that they will have on working life as these devices become more pervasive. For the enterprise, smartphones will have an impact on par with that of mobile telephony itself. Most of us already take for granted our ability to place and receive voice calls from anywhere at any time. But few of us yet take advantage of instantly having any data we wish at any time from that very same mobile phone. The implications are far reaching. For business travelers (or even managers and other workers that spend a lot of time away from their desks) it will mean having access to time-sensitive data and the ability to “stay in touch” with work teams on important issues in a manner that hasn’t previously been possible. This is readily achieved by delivering email, web access and instant messaging directly to the user’s phone.
    [Show full text]
  • 1 United States District Court Eastern District of Texas
    Case 2:18-cv-00412-RWS-RSP Document 22 Filed 02/21/19 Page 1 of 24 PageID #: 656 UNITED STATES DISTRICT COURT EASTERN DISTRICT OF TEXAS MARSHALL DIVISION TRAXCELL TECHNOLOGIES, LLC, ) Plaintiff, ) ) Civil Action No. 2:18-cv-412 v. ) ) NOKIA SOLUTIONS AND ) NETWORKS US LLC; NOKIA ) SOLUTIONS AND NETWORKS OY; ) JURY TRIAL DEMANDED NOKIA CORPORATION; NOKIA ) TECHNOLOGIES OY; ) ALCATEL-LUCENT USA, INC.; HMD ) GLOBAL OY; AND T-MOBILE, USA, ) INC. ) Defendants. ) PLAINTIFF’S FIRST AMENDED COMPLAINT FOR PATENT INFRINGEMENT Traxcell Technologies, LLC (“Traxcell”) files this First Amended Complaint and demand for jury trial seeking relief from patent infringement by Nokia Solutions and Networks US LLC (“Nokia Networks”), Nokia Solutions and Networks Oy (“Nokia Finland”), Nokia Corporation, Nokia Technologies Oy, Alcatel-Lucent USA Inc. (“ALU”) (collectively “Nokia”), HMD Global Oy ( “HMD”), and T-Mobile USA, Inc. (“T-Mobile”). HMD, Nokia, and T-Mobile collectively referred to as Defendants, alleging as follows: I. THE PARTIES 1. Plaintiff Traxcell is a Texas Limited Liability Company with its principal place of business located at 1405 Municipal Ave., Suite 2305, Plano, TX 75074. 2. Nokia Networks is a limited liability company organized and existing under the laws of Delaware with principal places of business located at (1) 6000 Connection Drive, MD E4-400, Irving, TX 75039; (2) 601 Data Dr., Plano, TX 75075; and (3) 2400 Dallas Pkwy., Plano, TX 75093, and a registered agent for service of process at National Registered Agents, Inc., 1 Case 2:18-cv-00412-RWS-RSP Document 22 Filed 02/21/19 Page 2 of 24 PageID #: 657 16055 Space Center, Suite 235, Houston, TX 77062.
    [Show full text]
  • Apple and Nokia: the Transformation from Products to Services
    9 Apple and Nokia: The Transformation from Products to Services In the mid- to late 2000s, Nokia flourished as the world’s dominant mobile phone – and mobile phone operating software – producer. Founded in 1871 originally as a rubber boots manufacturer, by 2007 Nokia produced more than half of all mobile phones sold on the planet, and its Symbian mobile operating system commanded a 65.6 percent global market share. 1 But within half a decade, Nokia would falter and be surpassed in the smartphone market not only by Apple’s revolu- tionary iPhone but also by competitors including Google and Samsung. And in September 2013, Nokia would sell its mobile phone business to Microsoft for $7 billion. 2 Apple literally came out of nowhere – it sold exactly zero mobile phones before the year 2007 (the year Nokia held more than half of the global market share) – but by the first quarter of 2013, Apple had captured almost 40 percent of the US smartphone market and over 50 percent of the operating profit in the global handset industry.3 In fiscal year 2013, Apple would sell five times more smart- phones than Nokia: 150 million iPhones compared to Nokia’s sales of 30 million Lumia Windows phones. 4 In contrast to Nokia, Apple real- ized it wasn’t just about the mobile device itself, it was about leveraging software to create a platform for developing compelling mobile experi- ences – including not just telephony but also music, movies, applica- tions, and computing – and then building a business model that allows partners to make money alongside the company (e.g., Apple’s iTunes and AppStore) and, in so doing, perpetuate a virtuous cycle of making the iPhone attractive to customers over multiple life cycles through ever-ex- panding feature sets.
    [Show full text]
  • The Symbian OS Architecture Sourcebook
    The Symbian OS Architecture Sourcebook The Symbian OS Architecture Sourcebook Design and Evolution of a Mobile Phone OS By Ben Morris Reviewed by Chris Davies, Warren Day, Martin de Jode, Roy Hayun, Simon Higginson, Mark Jacobs, Andrew Langstaff, David Mery, Matthew O’Donnell, Kal Patel, Dominic Pinkman, Alan Robinson, Matthew Reynolds, Mark Shackman, Jo Stichbury, Jan van Bergen Symbian Press Head of Symbian Press Freddie Gjertsen Managing Editor Satu McNabb Copyright 2007 Symbian Software, Ltd John Wiley & Sons, Ltd The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England Telephone (+44) 1243 779777 Email (for orders and customer service enquiries): [email protected] Visit our Home Page on www.wileyeurope.com or www.wiley.com All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except under the terms of the Copyright, Designs and Patents Act 1988 or under the terms of a licence issued by the Copyright Licensing Agency Ltd, 90 Tottenham Court Road, London W1T 4LP, UK, without the permission in writing of the Publisher. Requests to the Publisher should be addressed to the Permissions Department, John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England, or emailed to [email protected], or faxed to (+44) 1243 770620. Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners.
    [Show full text]
  • User Guide Nokia 150 Dual SIM
    User Guide Nokia 150 Dual SIM Online EN v1_1 For your safety Read these simple guidelines. Not following them may be dangerous or against local laws and regulations. For further info, read the complete user guide. SWITCH OFF IN RESTRICTED AREAS Switch the device off when mobile phone use is not allowed or when it may cause interference or danger, for example, in aircraft, in hospitals or near medical equipment, fuel, chemicals, or blasting areas. Obey all instructions in restricted areas. ROAD SAFETY COMES FIRST Obey all local laws. Always keep your hands free to operate the vehicle while driving. Your first consideration while driving should be road safety. INTERFERENCE All wireless devices may be susceptible to interference, which could affect performance. QUALIFIED SERVICE Only qualified personnel may install or repair this product. BATTERIES, CHARGERS, AND OTHER ACCESSORIES Use only batteries, chargers, and other accessories approved by HMD Global for use with this device. Do not connect incompatible products. KEEP YOUR DEVICE DRY Your device is not water-resistant. Keep it dry. PROTECT YOUR HEARING To prevent possible hearing damage, do not listen at high volume levels for long periods. Exercise caution when holding your device near your ear while the loudspeaker is in use. SAR This device meets RF exposure guidelines when used either in the normal use position against the ear or when positioned at least 5 mm away from the body. The specific maximum SAR values can be found in the Certification Information (SAR) section of this user guide. For more info, go to www.sar- tick.com.
    [Show full text]
  • Symbian Phone Security
    Symbian phone Security Job de Haas ITSX Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Overview • Symbian OS. • Security Risks and Features. • Taking it apart. • Conclusions. Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian History • Psion owner of EPOC OS, originally from 1989, released EPOC32 in 1996 • EPOC32 was designed with OO in C++ • 1998: Symbian Ltd. formed by Ericsson, Nokia, Motorola and Psion. • EPOC renamed to Symbian OS • Currently ~30 phones with Symbian and 15 licensees. Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian Organization • Symbian licenses the main OS • Two GUI’s on top of Symbian: – Series 60, led by Nokia – UIQ, subsidiary of Symbian • Ownership: – Nokia 47.5% Panasonic 10.5% – Ericsson 15.6% Siemens 8.4% – SonyEricsson 13.1% Samsung 4.5% Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian Versions • EPOC32 • EPOC R5 • Symbian v6.0 • Symbian v7.0 • Symbian v8.0 • Symbian v9.0 announced for Q3 ‘05 Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Series60 versions • 1st edition • 2nd edition • 3rd edition, announced feb. 2005 Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 UIQ versions • UIQ 1.0 • UIQ 2.1 • UIQ 3.0 released feb 2005 Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian OS Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian OS • Multitasking, preemptive kernel. • MMU protection of kernel and process spaces. • Strong Client – Server architecture • Plug-in patterns • Filesystem in ROM, Flash, RAM and on SD-card Symbian phone Job de Haas BlackHat Security ITSX BV Amsterdam 2005 Symbian development • Symbian v6 and v7 are compiled with a modified GCC.
    [Show full text]
  • Using Codewarrior for Macintosh
    CS106B Handout #5M Winter 04-05 January 7, 2005 Using CodeWarrior for Macintosh In CS106, you have the option of writing your programs on the Mac or PC. For the Macintosh environment, you will write your programs using the C++ compiler by Metrowerks called CodeWarrior Professional. The current version of CodeWarrior, Pro 8, has been site-licensed to Stanford and can be downloaded from the Software page on the course web site. CodeWarrior provides a very nice editing environment and debugger, and it is the state-of-the-art C++ compiler for the Mac. One of the consequences of using a state-of-the-art compiler is that the system requirements for CodeWarrior Pro 8 are somewhat high – it requires Mac OS 9.2.2 or later, 700MB of hard drive space, and at least 64 MB of RAM. You also have to have CarbonLib 1.5, since Pro 8 is written for Mac OS X as well. If you have OS X, then you need 128MB of RAM to run CodeWarrior Pro 8, and you don’t need CarbonLib as this is already part of OS X. You can download CarbonLib from Apple—more on this later. Using CodeWarrior at a cluster CodeWarrior is available for use in the Lair (the Tresidder Macintosh cluster), on the Macs in Meyer library, and in the residential computer clusters. Often it will already be in the Applications folder on the machine’s hard disk. If there is a folder there named something like Metrowerks CodeWarrior 8, then the application can be found within that folder.
    [Show full text]
  • This Introduction to the Metrowerks Codewarrior Software Development Tools
    Tutorial Introduction PURPOSE: - Provides an overview of the Metrowerks CodeWarrior toolset and explains how the toolset is organized and operates OBJECTIVES - Describe the CodeWarrior integrated development environment (IDE) - Identify the components of the CodeWarrior build system. - Identify the hosts on which the IDE executes. - Define a target. CONTENT: - 14 pages - 3 questions LEARNING TIME: - 20 minutes Welcome to this introduction to the Metrowerks CodeWarrior software development tools. This tutorial explains how CodeWarrior combines the programs required to write software into one seamless, integrated work environment. CodeWarrior tools run on several different platforms and can generate machine code for a variety of desktop and embedded systems. Upon completion of this tutorial, you’ll be able to describe the components of the CodeWarrior build system and the general organization of the software package. You’ll also be able to define a target and describe the operating systems that will host the software. 1 What is an IDE? • The IDE consists of tools that are used throughout the software development process. Project Manager Compiler Editor Assembler Search engine Linker Source code browser Debugger GUI designer • The tools are integrated fully and seamlessly. • A single environment is provided for software development. -- consistent operation -- move among all the tools freely -- a non-modal design In the CodeWarrior toolset, the Editor, Compiler, Linker, Debugger, and other software modules operate within an Integrated Development Environment, or IDE. The IDE oversees the control and execution of the tools. It provides an interface to the tools that is consistent and predictable. The operation of the development tools is seamless.
    [Show full text]
  • Nathan Miller (Final)
    Nathan Miller 5300 Parkview Drive #2062 Lake Oswego, OR 97035 541.954.0531 [email protected] SKILLS Overview I have extensive experience in all stages of the application development process, including requirement gathering and translation, functional specification compilation, technology evaluation, architecture\design, implementation, and maintenance\quality assurance. Languages\Frameworks • 8 years C\C++, designing and implementing all manner of desktop and network- communicating applications on Windows-based desktops (Windows SDK, MFC, ATL servers, COM objects and NT Services); handhelds (MS Embedded Visual C++ for Windows CE\Smartphone OS devices); and the embedded architecture found on Palm OS-based handheld devices. I also have experience designing and implementing cross platform ANSI-C compliant architectures • 8 years designing and implementing all manner of desktop applications in C#\ .NET Framework (versions 1.1\2.0\3.0) including interop via COM and InteropServices • 4 years Java, primarily made of modifying and enhancing the user interface of 3D vertebrate-modeling and animation software • Experience leveraging and modifying open source technologies to suit specific application needs. I have integrated third-party and open source technologies such as the OpenSSL encrypted network communication library, the log4NET logging framework, and the Xerces-c++ xml parsing framework, as well as modified the expat C++ xml parsing library to run on the memory- and processing performance-constrained embedded micro-architectures found
    [Show full text]
  • Nokia in 2014 at Nokia, We’Re Excited by Where Technology Will Lead Us
    Nokia in 2014 At Nokia, we’re excited by where technology will lead us. We’re reimagining a world where technology blends into our lives. Technology that works for us, discreetly yet magically in the background, enriching our lives. But for some, this new technology world, where everything and everybody are connected, can be challenging. Fear of intrusion, technology that seems hard to understand or control, and the complexity of choice, can be overwhelming. That’s why our focus is, and has always been, on people. We work together, with our partners, customers, and across our businesses, to create human technology that helps people thrive. Effortless, simple, and intuitive technology, designed to enable new and extraordinary experiences in people’s lives each day. We see the possibilities of technology. The human possibilities. Read more online: company.nokia.com The year 2014 was one of fundamental rapidly evolving world of technology which is change for Nokia, a new chapter in our storied as much about connecting things as about history, which stretches back to the founding connecting people. We expect to see more of a small paper mill in southern Finland in than 50 billion connected things—devices, 1865. Following the sale of substantially all of modules and sensors—by year 2025. The our Devices & Services business to Microsoft opportunity is extraordinary—not just for us, (the “Sale of the D&S Business”), which was but for the world at large. completed on April 25, 2014, Nokia emerged with three businesses—Nokia Networks, HERE We have a powerful role to play in this and Nokia Technologies—and a significantly increasingly connected world.
    [Show full text]