DOCSLIB.ORG

The Future of Webgl

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

AFTERWORD The Future of WebGL What does the future hold for WebGL? In this afterword, we will discuss both what WebGL has going for it and some concerns, and speculate on its future. In order for WebGL to have a bright future and not fail like other past 3D browser attempts such as the Virtual Reality Markup Language (VRML), it needs the following: v Support v Adoption from the development community, especially game developers v Improvements and active development Support Here we will look at support from browsers and devices. Browser support As mentioned in the book introduction, Chrome and Firefox do a very good job of supporting WebGL. Safari and Opera are improving, and IE does not have plans to natively support WebGL anytime soon. While five years ago this could be a disaster, IE does not command the market share that it used to enjoy—Chrome has surpassed it and Firefox is not far behind. Mobile Device support The level of mobile devices that currently support WebGL is small but will improve with each new device released and should be much higher in 2013. Right now, there are several mobile browsers that support WebGL: Firefox Mobile, Android Browser, Opera Mobile (Android only), BlackBerry Playbook, and iOS Mobile Safari (supported for only iAd at the moment). The mobile market share is growing and is an important area in which to gain ground. As Adobe recently announced that it will be discontinuing mobile Flash support, WebGL has an even better opportunity to establish itself as the go-to technology for mobile 3D. The sitehttp://webglstats.com/ by Florian Boesch has some very interesting statistics on the current support of various WebGL metrics across browsers, devices, and operating systems. 299 AFTERWORD N THE FUTURE OF WEBGL Adoption As mentioned in this book, Google has used WebGL for its Body, Map, and Earth applications. We showed in Chapter 9 that Firefox is using WebGL for a new 3D debugging visualization of the Document Object Model (DOM). It is important to get support and usage from the big name companies, and this is happening with support from Google, Mozilla, Apple and Opera. It is also important to get well-written frameworks that lower the bar to 3D coding. Frameworks such as Three.js are already easy to use and will continue to get better. What WebGL Has Going for It v No plugin needed. v The timing is right. 3D in the browser is more useful now than back when VRML tried. GPUs are more powerful. WebGL is part of the larger movement of HTML5 and related technologies, which adds many browser enhancements which are making it possible to create applications previously only possible on the desktop. “For a couple of decades, the web has been sipping that power through a straw but with WebGL, it’s as if the straw had been replaced by a fire hose when it comes to graphic processing power . .” http://www.tnl.net/blog/2011/10/23/webgl-and-the-future- of-the-web/ v Web applications do not have platform compatibility issues or need to be installed. v WebGL frameworks are making it easier all the time to get started with WebGL. v For the experienced graphics programmers, the ability to tweak WebGL at a low level is extremely useful. v Many awe-inspiring demos. v Transparent development of the specification. v Experience and existing developers. Khronos is also in charge of OpenGL and Collada. There are many current OpenGL and OpenGL ES developers who can fairly easily pick up/transition to the WebGL API. Concerns WebGL is powerful and very promising. However it is a relatively new language and has some concerns which include these: v Lack of Microsoft support. As mentioned previously, this is not as big a deal as it would have been when Microsoft dominated the browser demographic. Whether it is not supporting WebGL because of security concerns or because of interest in its own DirectX technology, only Microsoft can say for certain. v Security concerns. GPU blacklists, and newer graphics cards with improved security will help with GPU concerns. Other web security measures such as cross-origin resource sharing will enable flexibility while maintaining security. v Flash or other technology being used for 3D instead. As mentioned, Flash discontinuing mobile support helps alleviate this concern. 300 AFTERWORD N THE FUTURE OF WEBGL v Performance issues with JavaScript . JavaScript is slow. Improvements have been made such as typed arrays, and more optimizations are being investigated. v Game developers need to get on board. This point will now be expanded upon. Game Developers An excellent blog entry at http://codeflow.org/entries/2011/sep/11/webgl-and-html5-challenges-for- the-future/ by Florian Boesch explains how WebGL needs game developers to adopt it. In the entry several features that are needed by game developers are listed with those relating to WebGL specifically being: multiple render targets, geometry instancing, texture lookup in the vertex shader, and floating-point textures. Current support for these features by browser can be found at the webglstats.com link mentioned here. Active Development The WebGL specification, future extensions, and owserbr implementations are all under active development. Extensions The WebGL language has extensions to the core hatt are in development and can be viewed at http://www.khronos.org/registry/webgl/extensions/. Of the extensions currently listed, three in particular that will be useful are these: v Anisotropic filtering, which improves the quality of textures that are viewed at an oblique angle v Depth textures for shadow maps v Compressed textures Future features that could be added soon include these: v More extensions, such as cross-context sharing or multiple render targets. v Multithreading in web workers. This would allow uploading textures and data without blocking the main thread. v Asynchronous context creation and resource sharing between contexts. The Final Word Nothing in technology is certain, but I firmly believe that WebGL is here to stay—or I wouldn’t have taken the time and energy to write this book. WebGL is a very promising technology being developed at the right time when browsers are under rapid release cycles and are supporting more advanced features daily. It is also a time when more and more powerful computers are being crammed into mobile devices everywhere. WebGL is already a very useable technology. Framework improvements will help lower the bar for new developers, more debug and utility tools will be created, and performance will continue to improve. 301 APPENDIX A Essential HTML5 and JavaScript There are many, many improvements and features that are either part of HTML5 or associated with it: geolocation, new input types, form validation, local storage, and web sockets (to name a few). Covering everything new is both not feasible and not desired here—there are recent large books that do so in depth. Essential HTML5 While you will not need to know everything new and great about HTML5 to follow along with this book, to maximize your understanding of the code samples we will present the relevant differences from HTML 4 that you need to be aware of. Brevity First, HTML5 allows more compact writing of a document by standardizing the opening tags and having shorthand for scripts and styles. In HTML 4, you would have something like code Listing A-1 below: Listing A-1. A minimalistic HTML 4 document <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <TITLE>Example</TITLE> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"> <style type="text/css"> body{ color: #222222; } </style> <script type="text/javascript"> . </script> </head> <body> <p>Some text</p> </body> </html> 303 APPENDIX A N ESSENTIAL HTML5 AND JAVASCRIPT With HTML5, the equivalent document is shorter and clearer to write, as shown in Listing A-2. You do not have to declare transitional or strict in your doctype, just the simple and clean <!doctype html>. We can also leave out the type attribute for the style and script tags because JavaScript and CSS are the default. Listing A-2. A minimalistic HTML5 document <!doctype html> <html> <head> <meta charset="UTF-8"> <title>Example</title> <style> body{ color: #222222; } </style> <script> . </script> </head> <body> <p>Some text</p> </body> </html> Semantic Areas We just showed that HTML5 has some nice shorthand over HTML 4. HTML 5 also lets you outline your document in a more natural and expressive manner. In the past, if you wanted a header and footer area of your page, one way of styling would be to group the relevant content in a <div> with an appropriately expressive id attribute value such as that shown in Listing A-3. Listing A-3. HTML 4 document with id used to mark major sections <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"> <title>Example</title> </head> <body> <div id="header"> my header stuff </div> <div id="main-content"> <p>Some text</p> </div> <div id="footer"> my footer stuff </div> </body> </html> 304 APPENDIX A N ESSENTIAL HTML5 AND JAVASCRIPT With HTML5, we have many new included tags such as <header> and <footer>, which make this markup cleaner and the sections more natural as shown in Listing A-4. Listing A-4. HTML5 document with new semantic tags for major page sections <!doctype html> <html> <head> <meta charset="UTF-8"> <title>Example</title> </head> <body> <header> my header stuff </header> <div id="main-content"> <p>Some text</p> </div> <footer> my footer stuff </footer> </body> </html> Other new structural elements are article, aside, figcaption, figure, hgroup, nav, and section.
Recommended publications
  • Differential Fuzzing the Webassembly

    Differential Fuzzing the Webassembly

    Master’s Programme in Security and Cloud Computing Differential Fuzzing the WebAssembly Master’s Thesis Gilang Mentari Hamidy MASTER’S THESIS Aalto University - EURECOM MASTER’STHESIS 2020 Differential Fuzzing the WebAssembly Fuzzing Différentiel le WebAssembly Gilang Mentari Hamidy This thesis is a public document and does not contain any confidential information. Cette thèse est un document public et ne contient aucun information confidentielle. Thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Technology. Antibes, 27 July 2020 Supervisor: Prof. Davide Balzarotti, EURECOM Co-Supervisor: Prof. Jan-Erik Ekberg, Aalto University Copyright © 2020 Gilang Mentari Hamidy Aalto University - School of Science EURECOM Master’s Programme in Security and Cloud Computing Abstract Author Gilang Mentari Hamidy Title Differential Fuzzing the WebAssembly School School of Science Degree programme Master of Science Major Security and Cloud Computing (SECCLO) Code SCI3084 Supervisor Prof. Davide Balzarotti, EURECOM Prof. Jan-Erik Ekberg, Aalto University Level Master’s thesis Date 27 July 2020 Pages 133 Language English Abstract WebAssembly, colloquially known as Wasm, is a specification for an intermediate representation that is suitable for the web environment, particularly in the client-side. It provides a machine abstraction and hardware-agnostic instruction sets, where a high-level programming language can target the compilation to the Wasm instead of specific hardware architecture. The JavaScript engine implements the Wasm specification and recompiles the Wasm instruction to the target machine instruction where the program is executed. Technically, Wasm is similar to a popular virtual machine bytecode, such as Java Virtual Machine (JVM) or Microsoft Intermediate Language (MSIL).
  • Dynamic Web Pages with the Embedded Web Server

    Dynamic Web Pages with the Embedded Web Server

    Dynamic Web Pages With The Embedded Web Server The Digi-Geek’s AJAX Workbook (NET+OS, XML, & JavaScript) Version 1.0 5/4/2011 Page 1 Copyright Digi International, 2011 Table of Contents Chapter 1 - How to Use this Guide ............................................................................................................... 5 Prerequisites – If You Can Ping, You Can Use This Thing! ..................................................................... 5 Getting Help with TCP/IP and Wi-Fi Setup ............................................................................................ 5 The Study Guide or the Short Cut? ....................................................................................................... 5 C Code ................................................................................................................................................... 6 HTML Code ............................................................................................................................................ 6 XML File ................................................................................................................................................. 6 Provide us with Your Feedback ............................................................................................................. 6 Chapter 2 - The Server-Client Relationship ................................................................................................... 7 Example – An Analogy for a Normal HTML page .................................................................................
  • Attacking AJAX Web Applications Vulns 2.0 for Web 2.0

    Attacking AJAX Web Applications Vulns 2.0 for Web 2.0

    Attacking AJAX Web Applications Vulns 2.0 for Web 2.0 Alex Stamos Zane Lackey [email protected] [email protected] Blackhat Japan October 5, 2006 Information Security Partners, LLC iSECPartners.com Information Security Partners, LLC www.isecpartners.com Agenda • Introduction – Who are we? – Why care about AJAX? • How does AJAX change Web Attacks? • AJAX Background and Technologies • Attacks Against AJAX – Discovery and Method Manipulation – XSS – Cross-Site Request Forgery • Security of Popular Frameworks – Microsoft ATLAS – Google GWT –Java DWR • Q&A 2 Information Security Partners, LLC www.isecpartners.com Introduction • Who are we? – Consultants for iSEC Partners – Application security consultants and researchers – Based in San Francisco • Why listen to this talk? – New technologies are making web app security much more complicated • This is obvious to anybody who reads the paper – MySpace – Yahoo – Worming of XSS – Our Goals for what you should walk away with: • Basic understanding of AJAX and different AJAX technologies • Knowledge of how AJAX changes web attacks • In-depth knowledge on XSS and XSRF in AJAX • An opinion on whether you can trust your AJAX framework to “take care of security” 3 Information Security Partners, LLC www.isecpartners.com Shameless Plug Slide • Special Thanks to: – Scott Stender, Jesse Burns, and Brad Hill of iSEC Partners – Amit Klein and Jeremiah Grossman for doing great work in this area – Rich Cannings at Google • Books by iSECer Himanshu Dwivedi – Securing Storage – Hackers’ Challenge 3 • We are
  • WEB-BASED ANNOTATION and COLLABORATION Electronic Document Annotation Using a Standards-Compliant Web Browser

    WEB-BASED ANNOTATION and COLLABORATION Electronic Document Annotation Using a Standards-Compliant Web Browser

    WEB-BASED ANNOTATION AND COLLABORATION Electronic Document Annotation Using a Standards-compliant Web Browser Trev Harmon School of Technology, Brigham Young University, 265 CTB, Provo, Utah, USA Keywords: Annotation, collaboration, web-based, e-learning. Abstract: The Internet provides a powerful medium for communication and collaboration through web-based applications. However, most web-based annotation and collaboration applications require additional software, such as applets, plug-ins, and extensions, in order to work correctly with the web browsers typically found on today’s computers. This in combination with the ever-growing number of file formats poses an obstacle to the wide-scale deployment of annotation and collaboration systems across the heterogeneous networks common in the academic and corporate worlds. In order to address these issues, a web-based system was developed that allows for freeform (handwritten) and typed annotation of over twenty common file formats via a standards-compliant web browser without the need of additional software. The system also provides a multi-tiered security architecture that allows authors control over who has access to read and annotate their documents. While initially designed for use in academia, flexibility within the system allows it to be used for many annotation and collaborative tasks such as distance-learning, collaborative projects, online discussion and bulletin boards, graphical wikis, and electronic grading. The open-source nature of the system provides the opportunity for its continued development and extension. 1 INTRODUCTION did not foresee the broad spectrum of uses expected of their technologies by today’s users. While serving While the telegraph and telephone may have cracked this useful purpose, such add-on software can open the door of instantaneous, worldwide become problematic in some circumstances because communication, the Internet has flung it wide open.
  • Mastering Ajax, Part 4: Exploiting DOM for Web Response Convert HTML Into an Object Model to Make Web Pages Responsive and Interactive

    Mastering Ajax, Part 4: Exploiting DOM for Web Response Convert HTML Into an Object Model to Make Web Pages Responsive and Interactive

    Mastering Ajax, Part 4: Exploiting DOM for Web response Convert HTML into an object model to make Web pages responsive and interactive Skill Level: Introductory Brett McLaughlin Author and Editor O'Reilly Media Inc. 14 Mar 2006 The great divide between programmers (who work with back-end applications) and Web programmers (who spend their time writing HTML, CSS, and JavaScript) is long standing. However, the Document Object Model (DOM) bridges the chasm and makes working with both XML on the back end and HTML on the front end possible and an effective tool. In this article, Brett McLaughlin introduces the Document Object Model, explains its use in Web pages, and starts to explore its usage from JavaScript. Like many Web programmers, you have probably worked with HTML. HTML is how programmers start to work on a Web page; HTML is often the last thing they do as they finish up an application or site, and tweak that last bit of placement, color, or style. And, just as common as using HTML is the misconception about what exactly happens to that HTML once it goes to a browser to render to the screen. Before I dive into what you might think happens -- and why it is probably wrong -- I want you need to be clear on the process involved in designing and serving Web pages: 1. Someone (usually you!) creates HTML in a text editor or IDE. 2. You then upload the HTML to a Web server, like Apache HTTPD, and make it public on the Internet or an intranet. Exploiting DOM for Web response Trademarks © Copyright IBM Corporation 2006 Page 1 of 19 developerWorks® ibm.com/developerWorks 3.
  • Document Object Model

    Document Object Model

    Document Object Model CITS3403: Agile Web Development Semester 1, 2021 Introduction • We’ve seen JavaScript core – provides a general scripting language – but why is it so useful for the web? • Client-side JavaScript adds collection of objects, methods and properties that allow scripts to interact with HTML documents dynamic documents client-side programming • This is done by bindings to the Document Object Model (DOM) – “The Document Object Model is a platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents.” – “The document can be further processed and the results of that processing can be incorporated back into the presented page.” • DOM specifications describe an abstract model of a document – API between HTML document and program – Interfaces describe methods and properties – Different languages will bind the interfaces to specific implementations – Data are represented as properties and operations as methods • https://www.w3schools.com/js/js_htmldom.asp The DOM Tree • DOM API describes a tree structure – reflects the hierarchy in the XTML document – example... <html xmlns = "http://www.w3.org/1999/xhtml"> <head> <title> A simple document </title> </head> <body> <table> <tr> <th>Breakfast</th> <td>0</td> <td>1</td> </tr> <tr> <th>Lunch</th> <td>1</td> <td>0</td> </tr> </table> </body> </html> Execution Environment • The DOM tree also includes nodes for the execution environment in a browser • Window object represents the window displaying a document – All properties are visible to all scripts – Global variables are properties of the Window object • Document object represents the HTML document displayed – Accessed through document property of Window – Property arrays for forms, links, images, anchors, … • The Browser Object Model is sometimes used to refer to bindings to the browser, not specific to the current page (document) being rendered.
  • Webgl™ Optimizations for Mobile

    Webgl™ Optimizations for Mobile

    WebGL™ Optimizations for Mobile Lorenzo Dal Col Senior Software Engineer, ARM 1 Agenda 1. Introduction to WebGL™ on mobile . Rendering Pipeline . Locate the bottleneck 2. Performance analysis and debugging tools for WebGL . Generic optimization tips 3. PlayCanvas experience . WebGL Inspector 4. Use case: PlayCanvas Swooop . ARM® DS-5 Streamline . ARM Mali™ Graphics Debugger 5. Q & A 2 Bring the Power of OpenGL® ES to Mobile Browsers What is WebGL™? Why WebGL? . A cross-platform, royalty free web . It brings plug-in free 3D to the web, standard implemented right into the browser. Low-level 3D graphics API . Major browser vendors are members of . Based on OpenGL® ES 2.0 the WebGL Working Group: . A shader based API using GLSL . Apple (Safari® browser) . Mozilla (Firefox® browser) (OpenGL Shading Language) . Google (Chrome™ browser) . Opera (Opera™ browser) . Some concessions made to JavaScript™ (memory management) 3 Introduction to WebGL™ . How does it fit in a web browser? . You use JavaScript™ to control it. Your JavaScript is embedded in HTML5 and uses its Canvas element to draw on. What do you need to start creating graphics? . Obtain WebGLrenderingContext object for a given HTMLCanvasElement. It creates a drawing buffer into which the API calls are rendered. For example: var canvas = document.getElementById('canvas1'); var gl = canvas.getContext('webgl'); canvas.width = newWidth; canvas.height = newHeight; gl.viewport(0, 0, canvas.width, canvas.height); 4 WebGL™ Stack What is happening when a WebGL page is loaded . User enters URL . HTTP stack requests the HTML page Browser . Additional requests will be necessary to get Space User JavaScript™ code and other resources WebKit JavaScript Engine .
  • Chapter 10 Document Object Model and Dynamic HTML

    Chapter 10 Document Object Model and Dynamic HTML

    Chapter 10 Document Object Model and Dynamic HTML The term Dynamic HTML, often abbreviated as DHTML, refers to the technique of making Web pages dynamic by client-side scripting to manipulate the document content and presen- tation. Web pages can be made more lively, dynamic, or interactive by DHTML techniques. With DHTML you can prescribe actions triggered by browser events to make the page more lively and responsive. Such actions may alter the content and appearance of any parts of the page. The changes are fast and e±cient because they are made by the browser without having to network with any servers. Typically the client-side scripting is written in Javascript which is being standardized. Chapter 9 already introduced Javascript and basic techniques for making Web pages dynamic. Contrary to what the name may suggest, DHTML is not a markup language or a software tool. It is a technique to make dynamic Web pages via client-side programming. In the past, DHTML relies on browser/vendor speci¯c features to work. Making such pages work for all browsers requires much e®ort, testing, and unnecessarily long programs. Standardization e®orts at W3C and elsewhere are making it possible to write standard- based DHTML that work for all compliant browsers. Standard-based DHTML involves three aspects: 447 448 CHAPTER 10. DOCUMENT OBJECT MODEL AND DYNAMIC HTML Figure 10.1: DOM Compliant Browser Browser Javascript DOM API XHTML Document 1. Javascript|for cross-browser scripting (Chapter 9) 2. Cascading Style Sheets (CSS)|for style and presentation control (Chapter 6) 3. Document Object Model (DOM)|for a uniform programming interface to access and manipulate the Web page as a document When these three aspects are combined, you get the ability to program changes in Web pages in reaction to user or browser generated events, and therefore to make HTML pages more dynamic.
  • The Implementation of Large Video File Upload System Based on the HTML5 API and Ajax Yungeng Xu , Sanxing

    The Implementation of Large Video File Upload System Based on the HTML5 API and Ajax Yungeng Xu , Sanxing

    Joint International Mechanical, Electronic and Information Technology Conference (JIMET 2015) The Implementation of Large Video File Upload System Based on the HTML5 API and Ajax Yungeng Xu1, a, Sanxing Cao2, b 1 Department of Science and Engineering, Communication University of China, Beijing 2 New Media Institute, Communication University of China, Beijing a b [email protected], [email protected] Keywords: HTML5; File upload; Shell; XMLHttpRequest Abstract. The function of upload file is an important web page designs. Traditional file upload function for file upload function by HTML form and $_FILES system function, has the advantages of convenience, can cope with a relatively small file upload. The traditional HTML way has been difficult to meet the upload of the oversized file. Service not only to open a link waiting for this file is uploaded, but also to allocate the same size of memory to save this file. In the case of large concurrency may cause a great pressure on the server. This article is the use of HTML5 File API to upload video files in the original form on the basis of form, use the function of slice inside the HTML5 file API for the split file upload, to achieve the result of no refresh upload files. Have a valid practical significance. Introduction With the development of web technology, watch videos on the website has become an important forms of entertainment in the people's daily life. Internet video give people a great deal of freedom to choose the way of entertainment, not limited to the live TV mode. People can watch the video on the webpage.
  • Framework for Developing Offline HTML5 Applications

    Framework for Developing Offline HTML5 Applications

    MASARYK UNIVERSITY FACULTY}w¡¢£¤¥¦§¨ OF I !"#$%&'()+,-./012345<yA|NFORMATICS Framework for Developing Offline HTML5 Applications DIPLOMA THESIS Petr Kunc Brno, 2013 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Advisor: doc. RNDr. Tomás Pitner, PhD. ii Acknowledgement Above all, I would like to thank my advisor doc. RNDr. Tomáš Pitner, PhD. for leading not only this diploma thesis but also for leading me during my studies. I would also like to thank my colleagues in Laboratory of Software Architectures and Information Systems, especially Mgr. Filip Nguyen and Mgr. Daniel Tovarˇnákfor priceless advice on implementation and for providing their knowledge. Nevertheless, I would like to thank my colleagues in Celebrio Software company. iii Abstract The aim of this thesis is to provide detailed information about developing offline web ap- plications. The thesis presents important technologies in the development and mostly deals with Application cache technology. It summarizes advantages and also disadvantages and problems of the technology. Then, it offers solutions to some of the problems and introduces framework for build- ing offline web applications more sophisticatedly. At last, demonstration application is pre- sented which shows the benefits of proposed technology. iv Keywords HTML5, offline, web applications, application
  • Webgl: the Standard, the Practice and the Opportunity Web3d Conference August 2012

    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.
  • Cascading Style Sheet Web Tool

    Cascading Style Sheet Web Tool

    CASCADING STYLE SHEET WEB TOOL _______________ A Thesis Presented to the Faculty of San Diego State University _______________ In Partial Fulfillment of the Requirements for the Degree Master of Science in Computer Science _______________ by Kalthoum Y. Adam Summer 2011 iii Copyright © 2011 by Kalthoum Y. Adam All Rights Reserved iv DEDICATION I dedicate this work to my parents who taught me not to give up on fulfilling my dreams. To my faithful husband for his continued support and motivation. To my sons who were my great inspiration. To all my family and friends for being there for me when I needed them most. v ABSTRACT OF THE THESIS Cascading Style Sheet Web Tool by Kalthoum Y. Adam Master of Science in Computer Science San Diego State University, 2011 Cascading Style Sheet (CSS) is a style language that separates the style of a web document from its content. It is used to customize the layout and control the appearance of web pages written by markup languages. CSS saves time while developing the web page by applying the same layout and style to all pages in the website. Furthermore, it makes the website easy to maintain by just editing one file. In this thesis, we developed a CSS web tool that is intended to web developers who will hand-code their HTML and CSS to have a complete control over the web page layout and style. The tool is a form wizard that helps developers through a user-friendly interface to create a website template with a valid CSS and XHTML code.