Molly Holzschlag - How HTML 5 is Going to Completely Change your Web App
Upcoming SlideShare
Loading in...5
×
 

Molly Holzschlag - How HTML 5 is Going to Completely Change your Web App

on

  • 11,722 views

The HTML 5 spec was originally called "Web Applications 1.0". Most of the attention has been on the new markup elements, but we'll look further at the applications side of the spec, including: 1. ...

The HTML 5 spec was originally called "Web Applications 1.0". Most of the attention has been on the new markup elements, but we'll look further at the applications side of the spec, including: 1. Dynamic images and graphs with canvas 2. Eliminating forms validation with webforms 2.0 3. Local storage for saving your data 4. Geolocation 5. Building toolbars and menus

Statistics

Views

Total Views
11,722
Views on SlideShare
11,692
Embed Views
30

Actions

Likes
5
Downloads
34
Comments
0

3 Embeds 30

http://lanyrd.com 20
http://www.slideshare.net 9
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />

Molly Holzschlag - How HTML 5 is Going to Completely Change your Web App Molly Holzschlag - How HTML 5 is Going to Completely Change your Web App Presentation Transcript

  • HTML5 The Future of Web Applications molly e. holzschlag | web evangelist, developer relations | opera software
  • origin of the species web hypertext applications technology working group (what-wg)
  • <canvas>
  • canvas is . . . controversial WHAT-WG W3C ? accessibility concerns at-risk under W3C
  • <form>
  • before hixie (b.h.) <form action="" method="get"> <p><label>Search: <input name=search type="text" id="search"> </label></p> <script> document.getElementById('search').focus() </script> <!-- the rest of the form --> </form>
  • after hixie (a.h.) <form><p><label>Search: <input name=search autofocus> </label></p> <!-- the rest of the form --> </form>
  • validation <form> <p><label>Name: <input name=name required></label></p> <p><label>E-mail: <input name=”email” type=”email” required></label></p> <p><label>URL: <input name=”url” type=”url”></label></p> <p><label>Comment: <textarea name=”comment” required></ textarea></p> <p><input type=”submit” value=”Submit”></p> </form>
  • storage
  • Offline Web Applications ApplicationCache
  • Client-side data storage: Per-session via sessionStorage Persistently across sessions via localStorage and client-side SQL database storage
  • HTML5 APIs postMessage() - cross document messaging API for native drag and drop without the need for script Native getElementsByClassName accesskey and spellcheck keygen element how to handle SVG in text/html
  • Related APIs Geolocation - allowing script access to geolocation data Native JSON support XMLHttpRequest (level 1 and 2)
  • Device APIs JIL - Joint Innovation Lab - for widget and device development BONDI - From Open Mobile Terminal Platform (OMTP) - also for widget and device development Both allow scripting access to data such as remaining battery power, available bandwidth, processor speed and other aspects to device-specific, mobile behavior