Chapter 1: an Introduction to HTML, Css, and XML Preliminaries

Total Page:16

File Type:pdf, Size:1020Kb

Chapter 1: an Introduction to HTML, Css, and XML Preliminaries Chapter 1: An Introduction to HTML, css, and XML Preliminaries: download the oXygen XML Editor (you do not need Author, but it may come with it—that’s ok, too) From http://www.oxygenxml.com. We will be learning here the basics of HTML and css, and then how to transForm XML documents into HTML-and-css encoded web pages. The “languages” or really encoding procedures—“code,” for short—that we will discuss in this chapter (and a later chapter, in the case oF RDF), have been created and designed by the World Wide Web Consortium (W3C) organization.1 Consequently, you can find online tutorials From W3Schools that teach each oF these encoding procedures as well as the documentation For each language: Code Documentation Tutorial (section) HTML2 http://www.w3.org/TR/html4 http://www.w3schools.com/html/ (1.1) / http://www.w3.org/TR/xhtml http://www.w3schools.com/html/ht 1/ ml_xhtml.asp XML http://www.w3.org/XML/ http://www.w3schools.com/xml/ (1.3) CSS http://www.w3.org/Style/CSS http://www.w3schools.com/css/ (1.2) /Overview.en.html RDF http://www.w3.org/RDF/ http://www.w3schools.com/webserv (18.1) http://www.w3.org/TR/REC- ices/ws_rdf_intro.asp rdf-syntax/ Each of these languages are explained below. 1.1 HTML The Most Basic Introduction to Web-Page Coding (please read only 1.1.3, concerning our class setup, if you already know what HTML is and how it works.) 1.1.1 From the Outside When you go to a web site on your computer, iPad, or phone, you go to it via a browser oF some sort: SaFari, Internet Explorer, Google Chrome, FireFox: Figure 1.1.1, the Google Chrome browser A Web Page is anything that displays on that browser. 1.1.2 From the Inside Figure 1.1.2.a, a Web Page When you navigate to a webpage such as Figure 1.1.2.a that has not been made by a content management system – WordPress, Drupal, Media Commons, etc. – you can reveal the code that runs behind it. You simply navigate in your browser to “View Source,” as here in Chrome (Figure 1.1.2.b): Figure 1.1.2.b, View Source in Chrome Clicking on View Source reveals the HTML code that the browser has interpreted in order to display the web page you saw before revealing the source (Figure 1.1.2.c): Figure 1.1.2.c, HTML Code that causes the display seen in Figure 1.1.2.b The HTML code lives on a server at the web address where the browser visits (Figure 1.1.2.d): Client (User) Side Server (Maker) Side Figure 1.1.2.e, The Two Sides 1.1.3 Accessing Inside and Out For inFormation concerning how to get to your server space—whether space that has been set up by your IT Services Department, or space that you have purchased, see Appendix A. For the rest of this book, all the web pages that we will make can be put on your computer, locally, and we will view them using the browser(s). I will now have you set up your computer so that we can see both the inside and the outside, saving things as iF they were going on the server, and then looking at them using a browser, as iF you were coming to them via the Internet. a. First, make file extensions visible. Right now, on your computer, you might see only File names. We want you to be able to see the File name plus the “extension,” which is to say, the letters indicating what kind oF document it is: “letter.docx” = a File called “letter” that is a Word Document. You may google how to show/hide File extensions on your computer For your soFtware, but I offer two sets of instructions here (Figure 1.1.3.a.1 and Figure 1.1.3.a.2): Figure 1.1.3.a.1, Making File Extensions Visible on a PC with Windows 7: The instructions above are for Windows 7. You can go to the site itself to see the instructions for previous versions as well as Windows 10: http://windows.microsoFt.com/en-us/windows/show-hide-file-name- extensions#show-hide-file-name-extensions=windows-7 Figure 1.1.3.a.2, making file extensions visible on a Mac with OS X Yosemite. b. Second, set up a file structure that we will use as you work through the exercises in this book (Figure 1.1.3.b): Figure 1.1.3.b File Structure Your Digital Edition folder does not need to be on your desktop—it can be anywhere—but make the Four subFolders shown above: css, HTML, XML, and xslt. c. When you create your HTML pages, as you will for the exercises in this first chapter, you will use TextWrangler or Notepad++, then save the document with an .html extension, just as you would when creating web Files to send to your server (Figure 1.1.3.c): Figure 1.1.3.c, Saving an HTML document in TextWrangler. d. You will then pretend you are a user, looking at the file by opening it in your web browser (Figure 1.1.3.d): Figure 1.1.3.d, View local files in the same way as would a user coming to your server 1.1.4 Basic HTML Code HTML, or the Hypertext Markup Language, is “the publishing language of the World Wide Web”3 and is part oF the XML and SGML Families oF languages.4 Here follows the most basic code For a web page (Figure 1.1.4.a): Figure 1.1.4.a, Minimal Web Code When viewed in a browser, either locally on your computer or on the Internet, this code makes a page that looks like the Following (Figure 1.1.4.b): Figure 1.1.4.b, Minimal code viewed in a browser. Here in Figure 1.1.4.c, you can see the two together, the viewable results of the code: Figure 1.1.4.c, HTML Code and its effect in the browser window. Notice that, in talking about this code, I have called “<html>” a “tag”: it can be called, tag, element, or node, and in Fact to be most precise, <html> is a root node. Tags | Elements | Nodes appear in angle brackets in all the coding languages that we will learn, with the sole exception of CSS, as well as in the scripting language that is the main topic oF this book, XSLT. Notice also that nodes are nested inside each other. The <html> root element is the highest in the hierarchy: every other node occurs inside it. The next two elements in the hierarchy, elements that each minimal HTML document must contain, are <head> and <body> tags. Inside the body tag, we have two other kinds oF elements: <h#> and <p>. “H” in the first stands For “header,” and you can use numbers 1 through 6 along with it, 1 being the largest header, and 6 the smallest. The <p> tag is a paragraph tag, and it contains normal-sized fonts. The size, color, and font can all be adjusted by adding inFormation, and we will see how to make those adjustments in web-page style by using cascading stylesheets (section 1.2 below). Our minimal HTML code is lacking in one way. We should precede the root <html> element with a document declaration <!DOCTYPE html>, as in the first coding example oF HTML at the W3C Tutorial: <!DOCTYPE html> <html> <head> <title>Page Title</title> </head> <body> <h1>This is a Heading</h1> <p>This is a paragraph.</p> </body> </html> Figure 1.1.4.d: W3C’s minimal web encoding. The exclamation point inside the First open bracket indicates to web browsers interpreting this code for proper viewing that the content of the angle brackets is inFormation rather than something to be displayed, so the output of that code, the web view oF it, given on the W3C tutorial site is the following (Figure 1.1.4.e): Figure 1.1.4.e, W3C’s minimum web page, viewed in a browser. Usually, more inFormation is included in the document declaration: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> Here we are presented with the inFormation that the deFinition oF the HTML language is public, and it is given by the W3C in a “DTD” or Document Type Declaration with the name “HTML 4.01,” in “EN” (English), and that you can find this Document Type Declaration, the list oF rules that our code follows, at the URL given: http://www.w3.org/TR/html4/strict.dtd. When you are using WordPress or other content- or course-management systems, you can oFten switch to the HTML view oF whatever document you are composing or editing: in that view, HTML tags can be added using angle brackets, by coding directly. Those views do not need to have the document declaration, html, head, or body tags in them. For more about HTML codes, keep reading. HTML attributes (1.2.1) and links (1.2.3.d) will be discussed in the process of explaining Cascading Stylesheets. 1.2 Cascading Stylesheets Figure 1.2.a, a definition of CSS from W3C Tutorials The best way to see how using cascading stylesheets can affect the way that your HTML code looks when it is seen in a browser is to go to Zen Garden: http://www.csszengarden.com.
Recommended publications
  • 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).
    [Show full text]
  • XML a New Web Site Architecture
    XML A New Web Site Architecture Jim Costello Derek Werthmuller Darshana Apte Center for Technology in Government University at Albany, SUNY 1535 Western Avenue Albany, NY 12203 Phone: (518) 442-3892 Fax: (518) 442-3886 E-mail: [email protected] http://www.ctg.albany.edu September 2002 © 2002 Center for Technology in Government The Center grants permission to reprint this document provided this cover page is included. Table of Contents XML: A New Web Site Architecture .......................................................................................................................... 1 A Better Way? ......................................................................................................................................................... 1 Defining the Problem.............................................................................................................................................. 1 Partial Solutions ...................................................................................................................................................... 2 Addressing the Root Problems .............................................................................................................................. 2 Figure 1. Sample XML file (all code simplified for example) ...................................................................... 4 Figure 2. Sample XSL File (all code simplified for example) ....................................................................... 6 Figure 3. Formatted Page Produced
    [Show full text]
  • Document Object Model
    Document Object Model DOM DOM is a programming interface that provides a way for the values and structure of an XML document to be accessed and manipulated. Tasks that can be performed with DOM . Navigate an XML document's structure, which is a tree stored in memory. Report the information found at the nodes of the XML tree. Add, delete, or modify elements in the XML document. DOM represents each node of the XML tree as an object with properties and behavior for processing the XML. The root of the tree is a Document object. Its children represent the entire XML document except the xml declaration. On the next page we consider a small XML document with comments, a processing instruction, a CDATA section, entity references, and a DOCTYPE declaration, in addition to its element tree. It is valid with respect to a DTD, named root.dtd. <!ELEMENT root (child*)> <!ELEMENT child (name)> <!ELEMENT name (#PCDATA)> <!ATTLIST child position NMTOKEN #REQUIRED> <!ENTITY last1 "Dover"> <!ENTITY last2 "Reckonwith"> Document Object Model Copyright 2005 by Ken Slonneger 1 Example: root.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE root SYSTEM "root.dtd"> <!-- root.xml --> <?DomParse usage="java DomParse root.xml"?> <root> <child position="first"> <name>Eileen &last1;</name> </child> <child position="second"> <name><![CDATA[<<<Amanda>>>]]> &last2;</name> </child> <!-- Could be more children later. --> </root> DOM imagines that this XML information has a document root with four children: 1. A DOCTYPE declaration. 2. A comment. 3. A processing instruction, whose target is DomParse. 4. The root element of the document. The second comment is a child of the root element.
    [Show full text]
  • Extensible Markup Language (XML) and Its Role in Supporting the Global Justice XML Data Model
    Extensible Markup Language (XML) and Its Role in Supporting the Global Justice XML Data Model Extensible Markup Language, or "XML," is a computer programming language designed to transmit both data and the meaning of the data. XML accomplishes this by being a markup language, a mechanism that identifies different structures within a document. Structured information contains both content (such as words, pictures, or video) and an indication of what role content plays, or its meaning. XML identifies different structures by assigning data "tags" to define both the name of a data element and the format of the data within that element. Elements are combined to form objects. An XML specification defines a standard way to add markup language to documents, identifying the embedded structures in a consistent way. By applying a consistent identification structure, data can be shared between different systems, up and down the levels of agencies, across the nation, and around the world, with the ease of using the Internet. In other words, XML lays the technological foundation that supports interoperability. XML also allows structured relationships to be defined. The ability to represent objects and their relationships is key to creating a fully beneficial justice information sharing tool. A simple example can be used to illustrate this point: A "person" object may contain elements like physical descriptors (e.g., eye and hair color, height, weight), biometric data (e.g., DNA, fingerprints), and social descriptors (e.g., marital status, occupation). A "vehicle" object would also contain many elements (such as description, registration, and/or lien-holder). The relationship between these two objects—person and vehicle— presents an interesting challenge that XML can address.
    [Show full text]
  • HTML5 Favorite Twitter Searches App Browser-Based Mobile Apps with HTML5, CSS3, Javascript and Web Storage
    Androidfp_19.fm Page 1 Friday, May 18, 2012 10:32 AM 19 HTML5 Favorite Twitter Searches App Browser-Based Mobile Apps with HTML5, CSS3, JavaScript and Web Storage Objectives In this chapter you’ll: ■ Implement a web-based version of the Favorite Twitter Searches app from Chapter 5. ■ Use HTML5 and CSS3 to implement the interface of a web app. ■ Use JavaScript to implement the logic of a web app. ■ Use HTML5’s Web Storage APIs to store key-value pairs of data that persist between executions of a web app. ■ Use a CSS reset to remove all browser specific HTML- element formatting before styling an HTML document’s elements. ■ Save a shortcut for a web app to your device’s home screen so you can easily launch a web app. = DRAFT: © Copyright 1992–2012 by Deitel & Associates, Inc. All Rights Reserved. Androidfp_19.fm Page 2 Friday, May 18, 2012 10:32 AM 2 Chapter 19 HTML5 Favorite Twitter Searches App 19.1 Introduction 19.5 Building the App 19.2 Test-Driving the Favorite Twitter 19.5.1 HTML5 Document Searches App 19.5.2 CSS 19.5.3 JavaScript 19.3 Technologies Overview Outline 19.6 Wrap-Up 19.1 Introduction The Favorite Twitter Searches app from Chapter 5 allowed users to save their favorite Twit- ter search strings with easy-to-remember, user-chosen, short tag names. Users could then conveniently follow tweets on their favorite topics. In this chapter, we reimplement the Fa- vorite Twitter Searches app as a web app, using HTML5, CSS3 and JavaScript.
    [Show full text]
  • An XML Model of CSS3 As an XƎL ATEX-TEXML-HTML5 Stylesheet
    An XML model of CSS3 as an XƎLATEX-TEXML-HTML5 stylesheet language S. Sankar, S. Mahalakshmi and L. Ganesh TNQ Books and Journals Chennai Abstract HTML5[1] and CSS3[2] are popular languages of choice for Web development. However, HTML and CSS are prone to errors and difficult to port, so we propose an XML version of CSS that can be used as a standard for creating stylesheets and tem- plates across different platforms and pagination systems. XƎLATEX[3] and TEXML[4] are some examples of XML that are close in spirit to TEX that can benefit from such an approach. Modern TEX systems like XƎTEX and LuaTEX[5] use simplified fontspec macros to create stylesheets and templates. We use XSLT to create mappings from this XML-stylesheet language to fontspec-based TEX templates and also to CSS3. We also provide user-friendly interfaces for the creation of such an XML stylesheet. Style pattern comparison with Open Office and CSS Now a days, most of the modern applications have implemented an XML package format that includes an XML implementation of stylesheet: InDesign has its own IDML[6] (InDesign Markup Language) XML package format and MS Word has its own OOXML[7] format, which is another ISO standard format. As they say ironically, the nice thing about standards is that there are plenty of them to choose from. However, instead of creating one more non-standard format, we will be looking to see how we can operate closely with current standards. Below is a sample code derived from OpenOffice document format: <style:style style:name=”Heading_20_1” style:display-name=”Heading
    [Show full text]
  • Copyrighted Material
    05_096970 ch01.qxp 4/20/07 11:27 PM Page 3 1 Introducing Cascading Style Sheets Cascading style sheets is a language intended to simplify website design and development. Put simply, CSS handles the look and feel of a web page. With CSS, you can control the color of text, the style of fonts, the spacing between paragraphs, how columns are sized and laid out, what back- ground images or colors are used, as well as a variety of other visual effects. CSS was created in language that is easy to learn and understand, but it provides powerful control over the presentation of a document. Most commonly, CSS is combined with the markup languages HTML or XHTML. These markup languages contain the actual text you see in a web page — the hyperlinks, paragraphs, headings, lists, and tables — and are the glue of a web docu- ment. They contain the web page’s data, as well as the CSS document that contains information about what the web page should look like, and JavaScript, which is another language that pro- vides dynamic and interactive functionality. HTML and XHTML are very similar languages. In fact, for the majority of documents today, they are pretty much identical, although XHTML has some strict requirements about the type of syntax used. I discuss the differences between these two languages in detail in Chapter 2, and I also pro- vide a few simple examples of what each language looks like and how CSS comes together with the language to create a web page. In this chapter, however, I discuss the following: ❑ The W3C, an organization that plans and makes recommendations for how the web should functionCOPYRIGHTED and evolve MATERIAL ❑ How Internet documents work, where they come from, and how the browser displays them ❑ An abridged history of the Internet ❑ Why CSS was a desperately needed solution ❑ The advantages of using CSS 05_096970 ch01.qxp 4/20/07 11:27 PM Page 4 Part I: The Basics The next section takes a look at the independent organization that makes recommendations about how CSS, as well as a variety of other web-specific languages, should be used and implemented.
    [Show full text]
  • Markup Languages SGML, HTML, XML, XHTML
    Markup Languages SGML, HTML, XML, XHTML CS 431 – February 13, 2006 Carl Lagoze – Cornell University Problem • Richness of text – Elements: letters, numbers, symbols, case – Structure: words, sentences, paragraphs, headings, tables – Appearance: fonts, design, layout – Multimedia integration: graphics, audio, math – Internationalization: characters, direction (up, down, right, left), diacritics • Its not all text Text vs. Data • Something for humans to read • Something for machines to process • There are different types of humans • Goal in information infrastructure should be as much automation as possible • Works vs. manifestations • Parts vs. wholes • Preservation: information or appearance? Who controls the appearance of text? • The author/creator of the document • Rendering software (e.g. browser) – Mapping from markup to appearance •The user –Window size –Fonts and size Important special cases • User has special requirements – Physical abilities –Age/education level – Preference/mood • Client has special capabilities – Form factor (mobile device) – Network connectivity Page Description Language • Postscript, PDF • Author/creator imprints rendering instructions in document – Where and how elements appear on the page in pixels Markup languages •SGML, XML • Represent structure of text • Must be combined with style instructions for rendering on screen, page, device Markup and style sheets document content Marked-up document & structure style sheet rendering rendering software instructions formatted document Multiple renderings from same
    [Show full text]
  • 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.
    [Show full text]
  • How-To Guide: Copy and Adjust Skins (SAP CRM 7.0).Pdf
    How-to Guide: Copy and Adjust Skins ® SAP CRM 7.0 Target Audience System administrators Technology consultants Document version: 1.1 – December 2008 SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com © Copyright 2007 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their Some software products marketed by SAP AG and its distributors respective logos are trademarks or registered trademarks of SAP AG contain proprietary software components of other software vendors. in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their Microsoft, Windows, Outlook, and PowerPoint are registered respective companies. Data contained in this document serves trademarks of Microsoft Corporation. informational purposes only. National product specifications may vary. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, These materials are subject to change without notice. These materials xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, are provided by SAP AG and its affiliated companies ("SAP Group") Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and for informational purposes only, without representation or warranty of PowerPC are trademarks or registered trademarks of IBM Corporation.
    [Show full text]
  • Head First HTML with CSS & XHTML
    Head First HTML with CSS & XHTML Wouldn’t it be dreamy if there was an HTML book that didn’t assume you knew what elements, attributes, validation, selectors, and pseudo-classes were, all by page three? It’s probably just a fantasy... Elisabeth Freeman Eric Freeman Beijing • Cambridge • Köln • Sebastopol • Taipei • Tokyo Head First HTML with CSS and XHTML by Elisabeth Freeman and Eric Freeman Copyright © 2006 O’Reilly Media, Inc. 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 Media books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Associate Publisher: Mike Hendrickson Series Creators: Kathy Sierra, Bert Bates Series Advisors: Elisabeth Freeman, Eric Freeman Editor: Brett McLaughlin Cover Designers: Ellie Volckhausen, Karen Montgomery HTML Wranglers: Elisabeth Freeman, Eric Freeman Structure: Elisabeth Freeman Style: Eric Freeman Page Viewer: Oliver Printing History: December 2005: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. The Head First series designations, Head First HTML with CSS and XHTML, 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.
    [Show full text]
  • 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
    [Show full text]