DOCSLIB.ORG

Sustainable Technologies for Mobile Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Sustainable Technologies for Mobile Applications Sustainable Technologies for Mobile Applications Approved: ____________________________________________ Date: _________________ Prof. Dr. Christoph Wentzel - Committee Chair Approved: ____________________________________________ Date: _________________ Prof. Qi Yang, Ph.D. - Committee Member Approved: ____________________________________________ Date: _________________ Prof. Dr. Bernhard Kreling - Committee Member Sustainable Technologies for Mobile Applications A Thesis presented to the Graduate Faculties University of Wisconsin Platteville (UWP) and University of Applied Sciences Darmstadt (h_da) In Partial Fulfillment of the Requirement for the Degree Master of Science By Simon Heckmann Committee Chair: Prof. Dr. Christoph Wentzel (h_da) Committee Member: Prof. Dr. Bernhard Kreling (h_da) Committee Member: Prof. Qi Yang, Ph.D. (UWP) Start date: 02/16/2011 End date: 08/16/2011 Statement of Authorship Statement of Authorship I hereby declare that this thesis is written on my own solely by using the sources quoted in the thesis body. All contents (including text, figures, and tables), which are taken from sources, both verbally and in terms of meanings, are clearly marked and referenced. The thesis has not been previously submitted to any other examination board, neither in this nor in a similar form. ___________________________________ Simon Heckmann i Acknowledgments Acknowledgments First of all I would like to thank my advising professors, Dr. Wentzel, Dr. Yang and Dr. Kreling for helping me with this thesis. The great discussions about my ideas, results and findings helped me a lot during the entire creation process of this document. Secondly, I owe special thanks to my supervisors and colleges at Merck for their great sug- gestions and support. Especially, I would like to thank Dr. Michaela Bühler and Matthias Feldmann for their professional guidance and continuous motivation to tackle the challenges of this thesis. Furthermore, I want to thank Matthias Schwab, who never got tired of answer- ing my continuous questions about the current Merck Toolbox implementation. Furthermore, I want thank everyone who spent their valuable time proofreading and cor- recting this thesis. Last but not least, I would like to thank my family in particular my parents and my fiancé Christine for their great support. Your love, open ears and continuous motivation kept me going. Thank you for seeing the best in me and being there for me no matter what! You all made it happen! Thank you! ii English Abstract English Abstract With the continuously increasing availability of powerful mobile devices such as smartphones, tablets and notebook computers it is now possible to provide sophisticated software applications that can be used anywhere and anytime. However, when developing such mobile applications, developers find themselves confronted with a broad variety of different operating systems and hardware platforms. Unfortunately, each of these comes with support for different programming languages, development frameworks and libraries. An application that runs on one device can often not be easily run on another. Therefore, the process of bringing an application to many different mobile devices is often a time con- suming and expensive endeavor. As this thesis shows, using standardized and open web technologies such as the HyperText Markup Language, Cascading Style Sheets and JavaScript provides a feasible way to develop mobile applications for a broad variety of different mobile platforms in a cost-efficient way. Nevertheless, until today such open standard web applications are not yet entirely capable of competing with native applications or web applications with plugins as they still lack some capabilities. Fortunately, this is about to change as many new upcoming web standards and specifications are about to address these limitations. This thesis discusses why such web applications support nearly every available platform and how the upcoming standard candidates will allow open web applications to compete with native and plugin-based approaches and thereby save money by reducing development, deployment and maintenance costs. iii German Abstract German Abstract Mit der kontinuierlich wachsenden Verfügbarkeit von leistungsstarken mobilen Endgeräten, wie beispielsweise Smartphones, Tablets und Notebook Computern, ist es inzwischen mög- lich, komplexe Softwareanwendungen zu entwickeln, die zu jeder Zeit und an jedem Ort ver- fügbar sind. Bei der Entwicklung solcher mobilen Anwendungen werden Entwickler jedoch oft mit der großen Vielfalt an verschiedenen Betriebssystemen und Hardwareplattformen konfrontiert. Leider unterstützt jede davon unterschiedliche Programmiersprachen und Entwicklungsbibliotheken. Eine Anwendung, die auf einem mobilen Endgerät läuft, ist daher oft nicht zwingend ohne weiteres auch auf anderen Geräten lauffähig. Das Erstellen von An- wendungen für eine Vielzahl von mobilen Endgeräten ist daher oft ein zeitaufwendiges und kostenintensives Unterfangen. Wie in dieser Arbeit gezeigt wird, bieten standardisierte und offene Webtechnologien, wie beispielsweise Hypertext Markup Language, Cascading Style Sheets und JavaScript einen praktikablen Weg, kosteneffizient mobile Anwendungen für viele unterschiedlicher Geräte zu entwickeln. Trotzdem sind solche offenen Webanwendungen bis heute noch nicht in der Lage, es in allen Bereichen mit nativen Anwendungen oder Plugin-basierten Webanwendun- gen aufzunehmen, da ihnen noch einige Fähigkeiten fehlen. Glücklicherweise sind bereits weitere Webstandards und Spezifikationen in Arbeit, die diese momentanen Unzulänglich- keiten beheben sollen. In dieser Arbeit wird ausführlich diskutiert, wie es Webanwendungen auf eine einfache Art und Weise gestatten, plattformübergreifend zu entwickeln. Weiterhin wird erläutert, wie die angehenden Standards webbasierte Anwendungen ermöglichen, die in der Lage sind, es mit nativen oder Plugin-basierten Ansätzen aufzunehmen und wie gleichzeitig Entwicklungs-, Bereitstellungs- und Wartungskosten reduziert werden können. iv Table of Contents Table of Contents 1. Introduction 1 1.1. Goal ................................................................................................................... 2 1.2. Differentiation .................................................................................................. 3 1.3. Thesis Overview ................................................................................................ 4 2. Mobile Application Development 5 2.1. Classification of Mobile Computing Devices ..................................................... 5 2.2. Development platforms .................................................................................... 9 2.2.1. Operating Systems ........................................................................... 9 2.2.2. Programming Languages and Frameworks .................................... 11 2.3. Summary ......................................................................................................... 16 3. Web Applications 18 3.1. Architecture of Web Applications ................................................................... 19 3.2. Standardization Organizations ........................................................................ 21 3.2.1. World Wide Web Consortium ........................................................ 21 3.2.2. Web Hypertext Application Technology Working Group .............. 24 3.2.3. Khronos Group ............................................................................... 25 3.2.4. ECMA International ........................................................................ 26 3.3. Terminology .................................................................................................... 26 3.4. Web browsers ................................................................................................. 29 3.5. Future Web Standard Candidates ................................................................... 32 3.5.1. Presentation tier ............................................................................ 32 3.5.2. Logic tier ........................................................................................ 39 3.5.3. Data tier ......................................................................................... 43 3.5.4. Featured Technologies ................................................................... 45 3.6. Prefixing .......................................................................................................... 46 3.7. Compatibility Tests and Ratings ...................................................................... 47 v Table of Contents 3.8. Summary ......................................................................................................... 48 4. Feasibility Analysis 50 4.1. Merck Toolbox ................................................................................................ 50 4.2. Implementing the Prototype .......................................................................... 51 4.3. Open Issues ..................................................................................................... 56 4.4. Platform Independence .................................................................................. 57 4.5. Web Applications on iOS ................................................................................. 60 4.6. Summary ......................................................................................................... 61 5. Conclusion and Outlook
Load more

Recommended publications
  • Machine Learning in the Browser
    Machine Learning in the Browser The Harvard community has made this article openly available. Please share how this access benefits you. Your story matters Citable link http://nrs.harvard.edu/urn-3:HUL.InstRepos:38811507 Terms of Use This article was downloaded from Harvard University’s DASH repository, and is made available under the terms and conditions applicable to Other Posted Material, as set forth at http:// nrs.harvard.edu/urn-3:HUL.InstRepos:dash.current.terms-of- use#LAA Machine Learning in the Browser a thesis presented by Tomas Reimers to The Department of Computer Science in partial fulfillment of the requirements for the degree of Bachelor of Arts in the subject of Computer Science Harvard University Cambridge, Massachusetts March 2017 Contents 1 Introduction 3 1.1 Background . .3 1.2 Motivation . .4 1.2.1 Privacy . .4 1.2.2 Unavailable Server . .4 1.2.3 Simple, Self-Contained Demos . .5 1.3 Challenges . .5 1.3.1 Performance . .5 1.3.2 Poor Generality . .7 1.3.3 Manual Implementation in JavaScript . .7 2 The TensorFlow Architecture 7 2.1 TensorFlow's API . .7 2.2 TensorFlow's Implementation . .9 2.3 Portability . .9 3 Compiling TensorFlow into JavaScript 10 3.1 Motivation to Compile . 10 3.2 Background on Emscripten . 10 3.2.1 Build Process . 12 3.2.2 Dependencies . 12 3.2.3 Bitness Assumptions . 13 3.2.4 Concurrency Model . 13 3.3 Experiences . 14 4 Results 15 4.1 Benchmarks . 15 4.2 Library Size . 16 4.3 WebAssembly . 17 5 Developer Experience 17 5.1 Universal Graph Runner .
    [Show full text]
  • Practical API Design: Confessions Practical API Design of a Java™ Framework Architect
    CYAN YELLOW MAGENTA BLACK PANTONE 123 C BOOKS FOR PROFESSIONALS BY PROFESSIONALS® THE EXPERT’S VOICE® IN JAVA™ TECHNOLOGY Companion eBook Available Practical API Design: Confessions API Design Practical of a Java™ Framework Architect Dear Reader, Maybe you’re standing in a bookstore, holding this book in your hand, and ask- ing yourself, “Should I buy it?” Here is your answer. If you’ve ever written code and handed it to others to let them compile their code against yours, then you’re ready to enter the API design world and this book will help you explore it. Practical However, this book doesn’t attempt to “teach API design in five easy lessons.” It cannot be read in “only three days!” If you’re looking for a quick handbook, this book is probably not for you. On the other hand, if you’re interested in a deeper knowledge of API design, in knowing not only the how, but also the why, let me introduce myself to you before you put this book back on the shelf. My name is Jaroslav Tulach and I am the founder and initial architect of the NetBeans™ project, which is not just a well-known IDE, but also the first modu- lar desktop application framework written in the Java™ language. This book is based on notes that I’ve collected over the last ten years, while designing and API Design maintaining NetBeans APIs and transferring this knowledge to the rest of our developers. It’s a journal from the heart of the NetBeans laboratory, describing our problems, our growing understanding of them, the solutions we’ve chosen, ™ and the conclusions we made after applying them.
    [Show full text]
  • Webcl for Hardware-Accelerated Web Applications
    WebCL for Hardware-Accelerated Web Applications Won Jeon, Tasneem Brutch, and Simon Gibbs What is WebCL? • WebCL is a JavaScript binding to OpenCL. • WebCL enables significant acceleration of compute-intensive web applications. • WebCL currently being standardized by Khronos. 2 tizen.org Contents • Introduction – Motivation and goals – OpenCL • WebCL – Demos – Programming WebCL – Samsung’s Prototype: implementation & performance • Standardization – Khronos WebCL Working Group – WebCL robustness and security – Standardization status • Conclusion – Summary and Resources 3 tizen.org Motivation • New mobile apps with high compute demands: – augmented reality – video processing – computational photography – 3D games 4 tizen.org Motivation… • GPU offers improved FLOPS and FLOPS/watt as compared to CPU. FLOPS/ GPU watt CPU year 5 tizen.org Motivation… • Web-centric platforms 6 tizen.org OpenCL: Overview • Features – C-based cross-platform programming interface – Kernels: subset of ISO C99 with language extensions – Run-time or build-time compilation of kernels – Well-defined numerical accuracy (IEEE 754 rounding with specified maximum error) – Rich set of built-in functions: cross, dot, sin, cos, pow, log … 7 tizen.org OpenCL: Platform Model • A host is connected to one or more OpenCL devices • OpenCL device – A collection of one or more compute units (~ cores) – A compute unit is composed of one or more processing elements (~ threads) – Processing elements execute code as SIMD or SPMD 8 tizen.org OpenCL: Execution Model • Kernel – Basic unit
    [Show full text]
  • Redalyc.NEW WEB TECHNOLOGIES for ASTRONOMY
    Revista Mexicana de Astronomía y Astrofísica ISSN: 0185-1101 [email protected] Instituto de Astronomía México Sprimont, P-G.; Ricci, D.; Nicastro, L. NEW WEB TECHNOLOGIES FOR ASTRONOMY Revista Mexicana de Astronomía y Astrofísica, vol. 45, 2014, pp. 75-78 Instituto de Astronomía Distrito Federal, México Available in: http://www.redalyc.org/articulo.oa?id=57132995026 How to cite Complete issue Scientific Information System More information about this article Network of Scientific Journals from Latin America, the Caribbean, Spain and Portugal Journal's homepage in redalyc.org Non-profit academic project, developed under the open access initiative RevMexAA (Serie de Conferencias) , 45 , 75–78 (2014) NEW WEB TECHNOLOGIES FOR ASTRONOMY P-G. Sprimont, 1 D. Ricci, 2 and L. Nicastro 1 RESUMEN Gracias a las nuevas capacidades de HTML5, y las grandes mejoras del lenguaje JavaScript es posible disen˜ar interfaces web muy complejas e interactivas. Adem´as, los servidores que eran una vez monol´ıticos y orientados a servir archivos, est´an evolucionando a aplicaciones de servidor f´acilmente programables, capaces de lidiar con interacciones complejas gracias a la nueva generaci´onde navegadores. Nosotros creemos que la comunidad de astr´onomos profesionales y aficionados entera puede beneficiarse del potencial de estas nuevas tecnolog´ıas. Nuevas interfaces web pueden ser disen˜adas para proveer al usuario con herramientas mucho m´as intuitivas e interactivas. Acceder a archivos de datos astron´omicos, controlar y monitorear observatorios y en particu- lar telescopios rob´oticos, supervisar pipelines de reducci´on de datos, son todas capacidades que pueden ser imp lementadas en una aplicaci´on web JavaScript.
    [Show full text]
  • Webgl, Webcl and Beyond!
    WebGL, WebCL and Beyond! Neil Trevett VP Mobile Content, NVIDIA President, Khronos Group © Copyright Khronos Group, 2011 - Page 1 Two WebGL-focused Sessions Today • Industry ecosystem and standards for 3D and compute - What is 3D anyway – jungle survival primer - Khronos and open standard acceleration APIs for native apps - The evolution of pervasive 3D on mobile platforms - WebGL and WebCL as part of HTML5 - Web apps and use cases beyond games – augmented reality • Hands-On with WebGL - Steve Baker - Intific WebGL Reference Cards at end of session! © Copyright Khronos Group, 2011 - Page 2 What is Real-time 3D Graphics? © Copyright Khronos Group, 2011 - Page 3 3D Pipeline Basics • The art of “faking” realistic looking scenes or objects using heuristic techniques learned over the years • The objects making up a scene are held in a database • Surfaces of objects are broken down into a grid of polygons • The vertices of the polygons are located in 3D coordinate space - x,y,z • Each vertex has a “material” – color and reflective properties • Vertices are positioned in 3D space – matrix math zooms and rotates y x2,y2,z2 x1,y1,z1 z x3,y3,z3 x © Copyright Khronos Group, 2011 - Page 4 3D Pipeline Basics – Pixel Shading • Project each polygon onto the screen Interpolate colors - Determine which pixels are affected between vertices • Smooth Shading Lighting - Run lighting equation at each vertex equation each - Compute vertex color depending vertex on how lights interact with surface angles and properties - Interpolate colors between the vertices
    [Show full text]
  • Introduction to API Documentation Workbook July 28, 2018 Peter Gruenbaum
    Introduction to API Documentation Workbook July 28, 2018 Peter Gruenbaum Table of Contents Exercise 1: Markdown............................................................................................................ 3 Exercise 2: Create a JSON file ................................................................................................. 4 Exercise 3: Document JSON files............................................................................................. 7 Exercise 4: Making REST Requests ........................................................................................ 11 Exercise 5: Documenting Method and URL ........................................................................... 16 Exercise 6: Using Query Parameters ..................................................................................... 17 Exercise 7: Documenting Query Parameters ......................................................................... 19 Discounts for Online Classes ................................................................................................ 21 Schedule for July 28, 2018 8:30 Registration and Introduction 9:00 Markdown 9:30 Data Types and JSON 10:15 Documenting JSON 11:00 Break 11:15 Structured Data for Docs 11:30 REST: Methods 12:15 Lunch 12:45 REST: URLs 1:30 REST: Query parameters 2:15 Break 2:30 Tools and Next Steps 2:45 Q&A © 2018 SDK Bridge, all rights reserved 2 Exercise 1: Markdown Follow these steps: 1. Go to https://stackedit.io/ 2. Click on Start Writing at the top 3. Delete any text that currently
    [Show full text]
  • Webcl™ Kernel Validator Request for Quotations
    WebCL™ Kernel Validator Request for Quotations Notice ALL KHRONOS SPECIFICATIONS AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” KHRONOS MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Information furnished is believed to be accurate and reliable. However, Khronos assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication or otherwise under any patent or patent rights of Khronos. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied. Trademarks Khronos, WebCL and WebGL, and associated logos are trademarks or registered trademarks of Khronos Group Inc. OpenCL is a trademark of Apple Inc. and used under license by Khronos. All other product names, trademarks, and/or company names are used solely for identification and belong to their respective owners. Copyright © 2013 The Khronos Group All rights reserved. WebCL RFQ Page 1 of 9 1. Background The WebCL™ API is designed with security as a primary requirement. The Validator is a security tool to enforce compliance of WebCL™ kernels with the defined WebCL™ language restrictions, and prevent out of bounds memory accesses. The WebCL™ kernel Validator will enforce out of bounds memory protections and perform syntactic validation of WebCL™ kernels. 2. Requirements The project will deliver the design, implementation and documentation for a Validator for WebCL™ kernels.
    [Show full text]
  • Webgl: the Standard, the Practice and the Opportunity Web3d Conference August 2012
    WebGL: The Standard, the Practice and the Opportunity Web3D Conference August 2012 © Copyright Khronos Group 2012 | Page 1 Agenda and Speakers • 3D on the Web and the Khronos Ecosystem - Neil Trevett, NVIDIA and Khronos Group President • Hands On With WebGL - Ken Russell, Google and WebGL Working Group Chair © Copyright Khronos Group 2012 | Page 2 Khronos Connects Software to Silicon • Khronos APIs define processor acceleration capabilities - Graphics, video, audio, compute, vision and sensor processing APIs developed today define the functionality of platforms and devices tomorrow © Copyright Khronos Group 2012 | Page 3 APIs BY the Industry FOR the Industry • Khronos standards have strong industry momentum - 100s of man years invested by industry leading experts - Shipping on billions of devices and multiple operating systems • Khronos is OPEN for any company to join and participate - Standards are truly open – one company, one vote - Solid legal and Intellectual Property framework for industry cooperation - Khronos membership fees to cover expenses • Khronos APIs define core device acceleration functionality - Low-level “Foundation” functionality needed on every platform - Rigorous conformance tests for cross-vendor consistency • They are FREE - Members agree to not request royalties Silicon Software © Copyright Khronos Group 2012 | Page 4 Apple Over 100 members – any company worldwide is welcome to join Board of Promoters © Copyright Khronos Group 2012 | Page 5 API Standards Evolution WEB INTEROP, VISION MOBILE AND SENSORS DESKTOP OpenVL New API technology first evolves on high- Mobile is the new platform for Apps embrace mobility’s end platforms apps innovation. Mobile unique strengths and need Diverse platforms – mobile, TV, APIs unlock hardware and complex, interoperating APIs embedded – mean HTML5 will conserve battery life with rich sensory inputs become increasingly important e.g.
    [Show full text]
  • Backup Server Archive API Company
    REFERENCE MANUAL | PUBLIC SAP Adaptive Server Enterprise 16.0 SP03 Document Version: 1.0 – 2019-01-15 Reference Manual: Backup Server Archive API company. All rights reserved. All rights company. affiliate THE BEST RUN 2019 SAP SE or an SAP SE or an SAP SAP 2019 © Content 1 Overview.................................................................. 3 1.1 Syntax.....................................................................3 1.2 Byte Stream Archive Command Options.............................................4 2 Application Programming Interface..............................................5 3 API Routines............................................................... 8 3.1 syb_defineapi................................................................8 3.2 syb_queryapi................................................................9 3.3 set_params................................................................ 10 3.4 syb_open..................................................................10 3.5 syb_close..................................................................11 3.6 syb_read.................................................................. 12 3.7 syb_write..................................................................13 4 Error Messages.............................................................15 4.1 Localization................................................................ 15 4.2 Error and Informational Messages................................................ 15 5 Dynamically Loadable Library..................................................17
    [Show full text]
  • Application/Json Headers Content-Type: Application/Json
    Documenting APIs with Swagger TC Camp Peter Gruenbaum Introduction } Covers } What is an API Definition? } YAML } Open API Specification } Writing Documentation } Generating Documentation } Alternatives to Swagger and the Open API Specification } Presentation and workbook at sdkbridge.com/downloads © 2018 SDK Bridge Peter Gruenbaum } PhD in Applied Physics from Stanford } Commercial Software Developer } Boeing, Microsoft, start-ups } C#, C++, Java, JavaScript, Objective-C } API Writer } Brought together writing and technology } Since 2003 } President of SDK Bridge } Teacher: Programming at middle, high school, and college © 2018 SDK Bridge API Definition } Swagger and the Open API Specification are ways to define an API } What is an API? } What can you do with an API definition? © 2018 SDK Bridge What are APIs? } Application Programming Interface } It defines how two pieces of software talk to each other } For this seminar, we are talking about Web APIs © 2018 SDK Bridge Web APIs API request API response Creative Commons Attribution 3.0. webdesignhot.com Creative Commons Attribution 3.0. Not a full web page ─ just the data! openclipart.org The API definition describes: • What requests are available • What the response looks like for each request © 2018 SDK Bridge REST } Swagger and the Open API Specification are designed for RESTful APIs } REST is a type of web API REpresentational State Transfer © 2018 SDK Bridge REST Requests and Responses Please send me the state of my feed API request API response I am transferring to you some data
    [Show full text]
  • Technical Writer
    Technical writer A technical writer (also called a technical communicator) is a professional writer who designs, writes, creates, maintains, and updates technical documentation. This documentation includes online help, user guides, white papers, design specifications, system manuals, and other documents. Engineers, scientists, and other professionals may also produce technical writing, usually handing their work to a professional technical writer for proofreading, editing, and formatting. A technical writer produces technical documentation for technical, business, and consumer audiences. Contents 1 Skill set 2 Qualifications 3 Methodology 4 Environment 5 Career growth 6 See also 7 References 8 External links Skill set In addition to solid research, language, and writing skills, a technical writer may have skills in: Information design Information architecture Training material development Illustration Typography Technical writing may be on any subject that requires explanation to a particular audience. A technical writer is not usually a subject matter expert (SME), but possesses and applies expertise to interview SMEs and conduct research necessary to produce accurate, comprehensive documents. Companies, governments, and other institutions typically hire technical writers not for expertise in a particular subject, but for expertise in technical writing, i.e., their ability to gather information, analyze subject and audience and produce clear documentation. A good technical writer creates documentation that is accurate, complete, unambiguous, and as concise as possible. Technical writers create documentation in many forms: printed, web-based or other electronic documentation, training materials, and industrial film scripts. Qualifications Technical writers work under many job titles, including Technical Communicator, Information Developer, Data Development Engineer, and Technical Documentation Specialist. In the United Kingdom and some other countries, a technical writer is often called a technical author or knowledge author.
    [Show full text]
  • Neil Trevett Vice President Mobile Ecosystem, NVIDIA President, Khronos Group
    Neil Trevett Vice President Mobile Ecosystem, NVIDIA President, Khronos Group © Copyright Khronos Group 2014 - Page 1 Khronos Connects Software to Silicon Open Consortium creating ROYALTY-FREE, OPEN STANDARD APIs for hardware acceleration Defining the roadmap for low-level silicon interfaces needed on every platform Graphics, compute, rich media, vision, sensor and camera processing Rigorous specifications AND conformance tests for cross- vendor portability Acceleration APIs BY the Industry FOR the Industry Well over a BILLION people use Khronos APIs Every Day… © Copyright Khronos Group 2014 - Page 2 Khronos Standards 3D Asset Handling - 3D authoring asset interchange - 3D asset transmission format with compression Visual Computing - 3D Graphics - Heterogeneous Parallel Computing Over 100 companies defining royalty-free APIs to connect software to silicon Acceleration in HTML5 - 3D in browser – no Plug-in - Heterogeneous computing for JavaScript Sensor Processing - Vision Acceleration - Camera Control - Sensor Fusion © Copyright Khronos Group 2014 - Page 3 3D Needs a Transmission Format! • Compression and streaming of 3D assets becoming essential - Mobile and connected devices need access to increasingly large asset databases • 3D is the last media type to define a compressed format - 3D is more complex – diverse asset types and use cases • Needs to be royalty-free - Avoid an ‘internet video codec war’ scenario • Eventually enable hardware implementations of successful codecs - High-performance and low power – but pragmatic adoption strategy
    [Show full text]