DOCSLIB.ORG

Programming the Mobile Web

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Programming the Mobile Web Maximiliano Firtman Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo Programming the Mobile Web by Maximiliano Firtman Copyright © 2010 Maximiliano Firtman. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Simon St.Laurent Indexer: Jay Marchand Production Editor: Loranah Dimant Cover Designer: Karen Montgomery Copyeditor: Rachel Head Interior Designer: David Futato Proofreader: Jennifer Knight Illustrator: Robert Romano Production Services: Newgen, Inc. Printing History: July 2010: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Programming the Mobile Web, the image of a jerboa, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein. TM This book uses RepKover™, a durable and flexible lay-flat binding. ISBN: 978-0-596-80778-8 [M] 1279131278 For my parents, Stella Maris and Edgardo, my brother, Sebastián, and my lovely wife, Ani, who have supported me during all of my projects Table of Contents Preface . xiii 1. The Mobile Jungle . ... .................................................. 1 Myths of the Mobile Web 1 It’s Not the Mobile Web; It’s Just the Web! 1 You Don’t Need to Do Anything Special About Your Desktop Website 2 One Website Should Work for All Devices (Desktop, Mobile, TV, etc.) 2 Mobile Web Is Really Easy; Just Create a WML File 2 Just Create an HTML File with a Width of 240 Pixels, and You Have a Mobile Website 3 Native Mobile Applications Will Kill the Mobile Web 3 People Are Not Using Their Mobile Browsers 3 The Mobile Ecosystem 4 What Is a Mobile Device? 4 Mobile Device Categories 6 Mobile Knowledge 11 Display 11 Brands, Models, and Platforms 16 Apple 16 Nokia 18 BlackBerry 22 Samsung 23 Sony Ericsson 24 Motorola 24 LG Mobile 25 HTC 26 Android 26 Windows Mobile 27 Palm 28 Symbian Foundation 30 Other Platforms 31 Technical Information 31 v Market Statistics 32 2. Mobile Browsing . .................................................. 39 The Mobile Browsing Experience 39 Browsing Types 40 Zoom Experience 41 Reflow Engines 42 Direct Versus Proxied Browsers 43 Multipage Experience 43 The WebKit Engine 44 Preinstalled Browsers 45 User-Installable Browsers 51 Browser Overview 53 Mobile Web Eras 54 WAP 1 54 WAP 2.0 56 Mobile Web 2.0 59 3. Architecture and Design . ............................................ 61 Website Architecture 61 Navigation 61 Context 62 Progressive Enhancement 63 Different Version Approach 64 Design and Usability 65 Touch Design Patterns 70 Official UI Guidelines 73 4. Setting Up Your Environment . ....................................... 75 Setting Up a Development Environment 75 Working with Code 75 Emulators and Simulators 75 Production Environment 92 Web Hosting 93 Domain 93 Error Management 93 Statistics 94 5. Markups and Standards . ............................................ 95 First, the Old Ones 95 WML 96 Current Standards 102 Politics of the Mobile Web 102 vi | Table of Contents Delivering Markup 104 XHTML Mobile Profile and Basic 109 Available Tags 109 Official Noncompatible Features 111 Creating Our First Compatible Template 111 Markup Additions 112 CSS for Mobile 114 WCSS Extensions 114 Confusion 119 6. Coding Markup . ... .................................................. 121 Heading Structure 121 Icons for the Mobile Web 122 Hey! I’m Mobile Friendly 124 The Document Body 128 Main Structure 129 Images 131 Lists 138 Links 138 Forms 152 Tables 166 Frames 169 Plug-ins and Extensions 170 Adobe Flash 171 Microsoft Silverlight 174 SVG 174 Canvas 178 7. CSS for Mobile Browsers . ........................................... 179 Where to Insert the CSS 179 Media Filtering 180 Selectors 183 CSS Techniques 185 Reset CSS Files 185 Box Model 187 Text Format 187 Common Patterns 197 Display Properties 197 CSS Sprites 205 Samples and Compatibility 206 CSS Sprites Alternatives 210 WebKit Extensions 211 Text Stroke and Fill 211 Table of Contents | vii Border Image 212 Safari-Only Extensions 217 8. JavaScript Mobile . ... ................................................ 219 Supported Technologies 220 Document Object Model 220 Ajax 221 JSON 221 HTML 5 APIs 221 Platform Extensions 222 Coding JavaScript for Mobile Browsers 222 Code Execution 223 JavaScript Mobile Compatibility 225 DOM 241 Scripting Styles 246 Event Handling 247 Touch Gestures 259 9. Ajax, RIA, and HTML 5 . ............................................ 267 Ajax Support 267 XML Parsing 268 JSON Parsing 269 JSONP and Lazy Loading 270 Comet Techniques 271 JavaScript Libraries 272 Mobile Libraries 273 WebKit CSS Extensions 275 WebKit Functions 275 Gradients 276 Reflection Effects 277 Masked Images 278 Transitions 279 Animations 281 Transformations 284 Mobile Rich Internet Applications 288 JavaScript UI Libraries 289 JavaScript Mobile UI Patterns 295 HTML 5 301 The Standard 301 Editable Content 303 New Input Types 303 Data Lists 304 The canvas Element 304 viii | Table of Contents Offline Operation 308 Client Storage 311 10. Server-Side Browser Detection and Content Delivery . ... 317 Mobile Detection 317 HTTP 318 Detecting the Context 323 Transcoders 326 Device Libraries 330 Content Delivery 343 Defining MIME Types 343 File Delivery 346 Application and Games Delivery 351 Java ME 353 Flash Lite Content 356 iPhone Applications 357 Multimedia and Streaming 357 Delivering Multimedia Content 358 Embedding Audio and Video 358 Streaming 359 Content Adaptation 361 Adaptation Frameworks 362 Microsoft ASP.NET Mobile Controls 364 mobileOK Pythia 365 Yahoo! Blueprint 365 Mobilizing WordPress and Other CMSs 366 WordPress 367 11. Geolocation and Maps . ............................................ 369 Location Techniques 369 Accuracy 369 Indoor Location 369 Client Techniques 370 Server Techniques 371 Asking the User 373 Detecting the Location 375 W3C Geolocation API 375 Google Gears 379 BlackBerry Location API 382 Widget APIs 383 GSMA OneAPI 383 Multiplatform Geolocation API 384 IP Geolocation 386 Table of Contents | ix Showing a Map 387 Google Maps API v3 388 Google Maps Static API 390 Following LBS 391 12. Widgets and Offline Webapps . ... ...................................... 393 Mobile Widget Platforms 394 Pros and Cons 394 Architecture 395 Standards 398 Packaging and Configuration Standards 398 Platform Access 399 Platforms 403 Symbian/Nokia 403 iPhone, iPod, and iPad 413 webOS 418 Android 420 Windows Mobile 422 BlackBerry 424 LG Mobile 426 Samsung Mobile 427 JIL 429 Opera Widgets 430 Operator-Based Widget Platforms 431 Widget Design Patterns 431 Multiple Views 432 Layout 432 Input Method 432 One-View Widget 432 Dynamic Application Engine 433 Multiplatform Widgets 433 13. Testing, Debugging, and Performance . 435 Testing and Debugging 435 Remote Labs 436 Server-Side Debugging 443 Markup Debugging 445 Client-Side Debugging 448 Performance Optimization 451 Measurement 452 Best Practices 453 x | Table of Contents 14. Distribution and Social Web 2.0 . 457 Mobile SEO 457 Spiders and Discoverability 458 How Users Find You 459 User Fidelizing 464 Mobile Web Statistics 466 Google Analytics for Mobile 467 Yahoo! Web Analytics 467 Mobilytics 467 Motally Web Analytics 467 Pion for Mobile Web 468 Mobile Web Advertising 468 Monetizing Your Website 468 AdMob 469 Other Companies 469 Mobile Web Social Features 469 Facebook 469 Share Content 470 Appendix: MIME Types for Mobile Content . 473 Index . 477 Table of Contents | xi Preface In your pocket is a device that has changed the lives of billions of people all over the world. The third personal screen (after the TV and the computer) is the most personal one, and bringing our services to it is one of the key business priorities of this decade. Mobile development, however, is a more challenging activity than desktop develop- ment. Platforms are severely fragmented, and developers have to work with minimal resources. Fortunately, the mobile web makes it easier to deal with this fragmentation, allowing developers to create applications that run on many more platforms than native (or installable) applications. As we will see later, the mobile web and installable appli- cations are not enemies. In fact, they work together very well. All of that sounds great: billions of devices, web technologies, multiplatform solu- tions…where’s the problem? More than half of your desktop web skills and the tips, hacks, and best practices you already know simply do not apply on the mobile web. The mobile web demands new usability patterns, new programming best practices, and new knowledge and abilities. At the time of this writing there are almost no books, websites, or training courses focused on concrete mobile web
Recommended publications
  • D 4.3 Additional Applications

    D 4.3 Additional Applications

    Grant Agreement No. ICT-2009-270082 Project Acronym PATHS Project full title Personalised Access To Cultural Heritage Spaces D 4.3 Additional Applications Authors: George Chrysochoidis, i-sieve Contributors: Paul D. Clough and Mark Stevenson, USFD Eneko Agirre and Arantxa Otegi, UPV/EHU Kate Fernie, MDR Project funded under FP7-ICT-2009-6 Challenge 4 – “Digital Libraries and Content” Status Final Distribution level Public Date of delivery 24/01/2014 Type Report Project website http://www.paths-project.eu Project Coordinator Dr. Mark Stevenson University of Sheffield PATHS Collaborative Project EU-ICT-270082 Change Log Version Date Amended by Changes 0.1 12/12/2014 Paul Clough (USFD) Outline + recommender system 0.2 13/12/2014 Eneko Agirre, Arantxa Otegi Additional recommender system (UPV/EHU) 0.3 23/12/2014 George Chrysochoidis, i-sieve Mobile application 0.4 16/01/2014 George Chrysochoidis, i-sieve Additional text 0.5 20/01/2014 Kate Fernie, MDR Edited text 1.0 24/01/2013 Mark Stevenson, USFD, Kate Final Fernie, MDR D4.3 Additional Applications Page 2 PATHS Collaborative Project EU-ICT-270082 Contents 1. Executive Summary .............................................................................................. 4 2. Introduction ........................................................................................................... 5 2.1. Culture on the go ............................................................................................ 5 2.2. Native and Web Mobile Applications – A Brief History ..................................
  • A Taxonomy and Business Analysis for Mobile Web Applications

    A Taxonomy and Business Analysis for Mobile Web Applications

    A Taxonomy and Business Analysis for Mobile Web Applications Kevin Hao Liu Working Paper CISL# 2009-01 January 2009 Composite Information Systems Laboratory (CISL) Sloan School of Management, Room E53-320 Massachusetts Institute of Technology Cambridge, MA 02142 A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Ph.D. Computer Science Victoria University Submitted to the System Design and Management Program in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering At the Massachusetts Institute of Technology February 2009 © 2009 Kevin H Liu. All rights reserved The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. Signature of Author Kevin H Liu System Design and Management Program February 2009 Certified by Stuart E Madnick John Norris Maguire Professor of Information Technology Sloan School of Management Professor of Engineering Systems School of Engineering Massachusetts Institute of Technology Thesis Supervisor Certified by Patrick Hale Director System Design & Management Program Massachusetts Institute of Technology A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Submitted to the System Design and Management Program in February 2009 in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering ABSTRACT Mobile web applications refer to web applications on mobile devices, aimed at personalizing, integrating, and discovering mobile contents in user contexts. This thesis presents a comprehensive study of mobile web applications by proposing a new taxonomy for mobile web applications, and conducting a business analysis in the field of mobile web applications.
  • The Javascript Revolution

    The Javascript Revolution

    Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Shockers: Scribble & Fortuna Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna Congrats on sneaky strategizing
  • Znetlive SSL Compatible Applications, Platforms & Operating

    Znetlive SSL Compatible Applications, Platforms & Operating

    ZNetLive SSL Compatible Applications, Platforms & Operating Systems Certificate Authority Root Apple MAC OS 9.0+ (circa 2002), includes 10.5.X and 10.6.X Future proof at 2048 bit, embedded in all Microsoft Windows XP, Vista, 7 and 8 (all devices and browsers and capable of upgrading versions inc 32/64 bit) weak encryption to a strong one is the most reliable Certificate Authority Root-GlobalSign. It is very important to ensure a flawless interaction of your online solutions with Default API Support within Hosting Control customers making connection with your web Panels server, reading emails, trusting your e- Ubersmith documents or running your code. Every WHMCS standard machine that uses trust of Public Key Infrastructure (PKI), e.g. S/MIME, SSL/TLS, Document Signing and Code Signing, has GlobalSign’s Root Certification present in it. Email Clients (S/MIME) ZNetLive’s SSL Certificates authenticated by GlobalSign have 2048 bit strength throughout Mulberry Mail complete Digital Certificate portfolio and Microsoft Outlook 99+ comply with recommendations of National Microsoft Entourage (OS/X) Institute of Standards and Technology (NIST) Qualcomm Eudora 6.2+ according to which all cryptographic keys Mozilla Thunderbird 1.0+ should be 2048 bit strength from 2011 onwards. Mail.app Anything weaker than 2048 bit encryption is Lotus Notes (6+) considered insecure. Because of this, the Netscape Communicator 4.51+ Certification Authorities and Browsers insists The Bat that all the EV SSL Certificates should be 2048 Apple Mail bit encryption.
  • Browser Wars

    Browser Wars

    Uppsala universitet Inst. för informationsvetenskap Browser Wars Kampen om webbläsarmarknaden Andreas Högström, Emil Pettersson Kurs: Examensarbete Nivå: C Termin: VT-10 Datum: 2010-06-07 Handledare: Anneli Edman "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of read- ing a document written on another computer, another word processor, or another network" - Sir Timothy John Berners-Lee, grundare av World Wide Web Consortium, Technology Review juli 1996 Innehållsförteckning Abstract ...................................................................................................................................... 1 Sammanfattning ......................................................................................................................... 2 1 Inledning .................................................................................................................................. 3 1.1 Bakgrund .............................................................................................................................. 3 1.2 Syfte ..................................................................................................................................... 3 1.3 Frågeställningar .................................................................................................................... 3 1.4 Avgränsningar .....................................................................................................................
  • Building Android Apps with HTML, CSS, and Javascript

    Building Android Apps with HTML, CSS, and Javascript

    SECOND EDITION Building Android Apps with HTML, CSS, and JavaScript wnload from Wow! eBook <www.wowebook.com> o D Jonathan Stark with Brian Jepson Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Building Android Apps with HTML, CSS, and JavaScript, Second Edition by Jonathan Stark with Brian Jepson Copyright © 2012 Jonathan Stark. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Brian Jepson Cover Designer: Karen Montgomery Production Editor: Kristen Borg Interior Designer: David Futato Proofreader: O’Reilly Production Services Illustrator: Robert Romano September 2010: First Edition. January 2012: Second Edition. Revision History for the Second Edition: 2012-01-10 First release See http://oreilly.com/catalog/errata.csp?isbn=9781449316419 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Building Android Apps with HTML, CSS, and JavaScript, the image of a maleo, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein.
  • M&A @ Facebook: Strategy, Themes and Drivers

    M&A @ Facebook: Strategy, Themes and Drivers

    A Work Project, presented as part of the requirements for the Award of a Master Degree in Finance from NOVA – School of Business and Economics M&A @ FACEBOOK: STRATEGY, THEMES AND DRIVERS TOMÁS BRANCO GONÇALVES STUDENT NUMBER 3200 A Project carried out on the Masters in Finance Program, under the supervision of: Professor Pedro Carvalho January 2018 Abstract Most deals are motivated by the recognition of a strategic threat or opportunity in the firm’s competitive arena. These deals seek to improve the firm’s competitive position or even obtain resources and new capabilities that are vital to future prosperity, and improve the firm’s agility. The purpose of this work project is to make an analysis on Facebook’s acquisitions’ strategy going through the key acquisitions in the company’s history. More than understanding the economics of its most relevant acquisitions, the main research is aimed at understanding the strategic view and key drivers behind them, and trying to set a pattern through hypotheses testing, always bearing in mind the following question: Why does Facebook acquire emerging companies instead of replicating their key success factors? Keywords Facebook; Acquisitions; Strategy; M&A Drivers “The biggest risk is not taking any risk... In a world that is changing really quickly, the only strategy that is guaranteed to fail is not taking risks.” Mark Zuckerberg, founder and CEO of Facebook 2 Literature Review M&A activity has had peaks throughout the course of history and different key industry-related drivers triggered that same activity (Sudarsanam, 2003). Historically, the appearance of the first mergers and acquisitions coincides with the existence of the first companies and, since then, in the US market, there have been five major waves of M&A activity (as summarized by T.J.A.
  • IFIP AICT 306, Pp

    IFIP AICT 306, Pp

    Chapter 9 FORENSIC ANALYSIS OF THE SONY PLAYSTATION PORTABLE Scott Conrad, Carlos Rodriguez, Chris Marberry and Philip Craiger Abstract The Sony PlayStation Portable (PSP) is a popular portable gaming device with features such as wireless Internet access and image, music and movie playback. As with most systems built around a processor and storage, the PSP can be used for purposes other than it was originally intended – legal as well as illegal. This paper discusses the features of the PSP browser and suggests best practices for extracting digital evidence. Keywords: Sony PlayStation Portable, forensic analysis 1. Introduction The Sony PlayStation Portable (PSP) is a popular portable video game system that has additional multimedia and Internet-related capa- bilities. Originally released in 2004, the PSP features a 4.3” widescreen LCD with 480×272 pixel resolution. It comes with a dual core 222 MHz R4000 CPU, 32 MB RAM and 4 MB of embedded DRAM, which holds the operating system [6]. The PSP uses a proprietary Universal Me- dia Disk (UMD) as its primary read-only storage media for games and movies. The device also features 802.11b Wi-Fi connectivity for multi- player games and utilizes a Pro Duo memory stick for secondary storage. In September 2007, Sony released a new version of the PSP that is 33% lighter and 19% thinner, appropriately dubbed the PSP Slim & Lite. The Slim & Lite version caches UMD data in memory to decrease game loading time and provides additional features such as a brighter screen, composite TV output, charging via USB and double the onboard RAM (64 MB) [8].
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014

    HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014

    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
  • Manual Do Utilizador Do Nokia 5310 Xpressmusic

    Manual Do Utilizador Do Nokia 5310 Xpressmusic

    Manual do Utilizador do Nokia 5310 XpressMusic 9203503 Edição 1 DECLARAÇÃO DE CONFORMIDADE NOKIA CORPORATION declara que este RM-303 está conforme com os requisitos essenciais e outras disposições da Directiva 1999/5/CE. É possível obter uma cópia da Declaração de Conformidade no endereço http://www.nokia.com/phones/declaration_of_conformity/. © 2007 Nokia. Todos os direitos reservados. Nokia, Nokia Connecting People, Visual Radio e Navi são marcas comerciais ou marcas registadas da Nokia Corporation. Nokia tune é uma marca sonora da Nokia Corporation. Os nomes de outros produtos e empresas mencionados neste documento poderão ser marcas comerciais ou nomes comerciais dos respectivos proprietários. É proibido reproduzir, transferir, distribuir ou armazenar a totalidade ou parte do conteúdo deste documento, seja sob que forma for, sem a prévia autorização escrita da Nokia. US Patent No 5818437 and other pending patents. T9 text input software Copyright © 1997-2007. Tegic Communications, Inc. All rights reserved. Includes RSA BSAFE cryptographic or security protocol software from RSA Security. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. This product is licensed under the MPEG-4 Visual Patent Portfolio License (i) for personal and noncommercial use in connection with information which has been encoded in compliance with the MPEG-4 Visual Standard by a consumer engaged in a personal and noncommercial activity and (ii) for use in connection with MPEG-4 video provided by a licensed video provider. No license is granted or shall be implied for any other use. Additional information, including that related to promotional, internal, and commercial uses, may be obtained from MPEG LA, LLC.
  • Forum Nokia Style Guide

    Forum Nokia Style Guide

    Forum Nokia Style Guide Version 3.0 March 2003 Forum Nokia Style Guide Version 3.0 Contents About This Guide............................................................................................................4 Using This Guide ........................................................................................................5 About This Version .....................................................................................................5 Style Guide Review and Updates.................................................................................5 A–Z Reference................................................................................................................6 A.................................................................................................................................6 B .................................................................................................................................7 C .................................................................................................................................8 D............................................................................................................................... 13 E ............................................................................................................................... 14 F ............................................................................................................................... 15 G..............................................................................................................................
  • Paper Proposes a Technique for Automatically Repair- Appearance of a Website’S UI

    Paper Proposes a Technique for Automatically Repair- Appearance of a Website’S UI

    Automated Repair of Layout Cross Browser Issues using Search-Based Techniques Sonal Mahajan Abdulmajeed Alameer University of Southern California, USA University of Southern California, USA Phil McMinn William G. J. Halfond University of Sheeld, UK University of Southern California, USA ABSTRACT e constantly increasing number of web browsers with which A consistent cross-browser user experience is crucial for the suc- users can access a website has introduced new challenges in prevent- cess of a website. Layout Cross Browser Issues (XBIs) can severely ing appearance related issues. Dierences in how various browsers undermine a website’s success by causing web pages to render in- interpret HTML and CSS standards can result in Cross Browser correctly in certain browsers, thereby negatively impacting users’ Issues (XBIs) — inconsistencies in the appearance or behavior of impression of the quality and services that the web page delivers. a website across dierent browsers. Although XBIs can impact Existing Cross Browser Testing (XBT) techniques can only detect the appearance or functionality of a website, the vast majority — XBIs in websites. Repairing them is, hitherto, a manual task that is over 90% — result in appearance related problems [42]. is makes labor intensive and requires signicant expertise. Addressing this XBIs a signicant challenge in ensuring the correct and consistent concern, our paper proposes a technique for automatically repair- appearance of a website’s UI. ing layout XBIs in websites using guided search-based techniques. Despite the importance of XBIs, their detection and repair poses Our empirical evaluation showed that our approach was able to numerous challenges for developers. First, the sheer number of successfully x 86% of layout XBIs reported for 15 dierent web browsers available to end users is large — an informal listing re- pages studied, thereby improving their cross-browser consistency.