Schöne neue Welt von HTML5 - MultimediaTreff 28 - Köln 03.12.2011
•
5 likes•2,047 views
The document discusses the current state and capabilities of HTML5. It provides an overview of new HTML5 elements that add semantics, improved form controls, multimedia elements like video and audio, and the canvas element. While browser support for HTML5 is still evolving, many features can be used today through progressive enhancement. Feature detection and polyfills can help support older browsers. The document advocates an approach of giving developers choice between HTML5 and other technologies like Flash.
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to Schöne neue Welt von HTML5 - MultimediaTreff 28 - Köln 03.12.2011
Similar to Schöne neue Welt von HTML5 - MultimediaTreff 28 - Köln 03.12.2011 (20)
More from Patrick Lauke
More from Patrick Lauke (20)
Recently uploaded
Recently uploaded (20)
Schöne neue Welt von HTML5 - MultimediaTreff 28 - Köln 03.12.2011
- 1. Schöne neue Welt von HTML5 NEUE TECHNOLOGIEN IM KONTEXT Patrick H. Lauke / MultimediaTreff 28 / Köln / 3 Dezember 2011
- 2. Web Evangelist bei Opera
- 3. ...ist HTML5 heute schon nutzbar?
- 5. "there is already a lot of excitement for HTML5, but it’s a little too early to deploy it because we’re running into interoperability issues." Philippe Le Hegaret, W3C interaction domain leader blogs.techrepublic.com.com/hiner/?p=6369
- 8. Geschichte von HTML5 1999 HTML 4.01 2000 XHTML 1.0
- 9. 2004 W3C Fokus auf XHTML 2.0 …die Zukunft ist XML! http://www.flickr.com/photos/craiga/17071467/
- 10. WHATWG Web Hypertext Application Technology Working Group
- 11. 2007 W3C HTML5 WG
- 13. “...extending the language to better support Web applications [...] This puts HTML in direct competition with other technologies[...] , in particular Flash and Silverlight.” Ian Hickson, Editor of HTML5 http://lists.w3.org/Archives/Public/public-html/2009Jan/0215.html
- 14. HTML5 ersetzt nicht HTML 4.01
- 15. HTML5 hat mehr Bling!
- 16. HTML5 Spezifikation für Browserhersteller (wie interpretieren Browser Markup/Code – kein “reverse engineering”) für Autoren: HTML5 differences from HTML4 http://www.w3.org/TR/html5-diff/
- 17. 1. Syntax/Semantik 2. Formulare 3. Multimedia
- 18. 1. Syntax/Semantik 2. Formulare 3. Multimedia
- 19. HTML5 standardisiert derzeitiges Browserverhalten (e.g. “relaxed” coding rules)
- 22. das schmutzige Geheimniss der Doctype
- 24. <meta charset=”utf-8” /> <meta charset=utf-8> <MeTa CHarSet=utf-8>
- 28. neue Elemente für bessere Semantik
- 30. Top 20 class names 1. footer 11. button 2. menu 12. main 3. style1 13. style3 4. msonormal 14. small 5. text 15. nav 6. content 16. clear 7. title 17. search 8. style2 18. style4 9. header 19. logo 10. copyright 20. body http://devfiles.myopera.com/articles/572/classlist-url.htm
- 31. Top 20 id names 1. footer 11. search 2. content 12. nav 3. header 13. wrapper 4. logo 14. top 5. container 15. table2 6. main 16. layer2 7. table1 17. sidebar 8. menu 18. image1 9. layer1 19. banner 10. autonumber1 20. navigation http://devfiles.myopera.com/articles/572/idlist-url.htm
- 34. explizit und maschinenlesbar ...z.B. Screenreaders?
- 35. neue und alte Browser “unterstützen” die Elemente (obwohl einige etwas Hilfe brauchen) header, footer, … { display: block; }
- 36. Internet Explorer <9 braucht Stützräder document.createElement('header'); document.createElement('footer'); … http://html5doctor.com/how-to-get-html5-working-in-ie-and-firefox-2
- 37. 1. Syntax/Semantik 2. Formulare 3. Multimedia
- 38. bessere Formelemente weil das Web interaktiver ist
- 39. jqueryui.com
- 40. rich form elements – ganz ohne JavaScript <input type=”date”> <input type=”time”> <input type=”month”> <input type=”week”> <input type=”datetime” … > <input type=”range”> <input type=”number”> <input type=”file” multiple> <input … autofocus> <input … autocomplete>
- 41. Typen und Attribute mit eingebauter Validierung <input … required> <input type=”tel”> <input type=”email”> <input type=”url”> <input … pattern="[a-z]{3}[0-9]{3}">
- 45. 1. Syntax/Semantik 2. Formulare 3. Multimedia
- 46. making your site Fonzie compliant...
- 47. <video>
- 48. Adobe Flash derzeit meistbenutztes Art, Videos zu übermitteln
- 49. <object width="425" height="344"> <param name="movie" value="http://www.youtube.com/v/9sEI1AUFJKw&hl=en &fs=1&"></param> <param name="allowFullScreen" value="true"></param> <param name="allowscriptaccess" value="always"></param> <embed src="http://www.youtube.com/v/9sEI1AUFJKw&hl=en&f s=1&" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed> </object>
- 50. <video src="video.webm" controls autoplay loop preload poster="poster.jpg" width="320" height="240"> <a href="video.webm">Download movie</a> </video>
- 51. Video als natives object ● verhält sich wie jedes andere HTML Element ● keyboard accessibility von Haus aus
- 55. <video> per JavaScript ansteuern var v = document.getElementById('player'); v.play(); v.pause(); v.volume = … ; v.currentTime = … ; …
- 56. events vom <video> abfangen var v = document.getElementById('player'); v.addEventListener('loadeddata', function() { … }, true) v.addEventListener('play', function() { … }, true) v.addEventListener('pause', function() { … }, true) v.addEventListener('timeupdate', function() { … }, true) v.addEventListener('ended', function() { … }, true) …
- 60. Video Formate die grosse Debatte
- 61. MP4 / H.264 weitverbreitet, Lizenzen/Royalties
- 62. Ogg Theora “free and open”, keine Lizengebühren wenige Tools, nicht für's Web optimiert
- 63. WebM von Google, aber “open and royalty-free” Web-optimiert Support von Software- und Hardware-Herstellern
- 64. Video mit multiple sources <video controls autoplay poster="…" width="…" height="…"> <source src="movie.webm" type="video/webm" /> <source src="movie.mp4" type="video/mp4" /> <!-- fallback content --> </video>
- 65. Flash fallback für ältere browsers http://camendesign.com/code/video_for_everybody
- 66. <video controls autoplay poster="…" width="…" height="…"> <source src="movie.webm" type="video/webm" /> <source src="movie.mp4" type="video/mp4" /> <object width="…" height="…" type="application/x- shockwave-flash" data="player.swf"> <param name="movie" value="player.swf" /> <param name="flashvars" value=" … file=movie.mp4" /> <!-- fallback content --> </object> </video>
- 67. <audio>
- 68. Audio...genau das gleiche <audio src=”music.mp3” controls autoplay … ></audio> <audio controls autoplay> <source src="music.mp3" type="audio/mpeg" /> <source src="music.oga" type="audio/ogg" /> <!-- fallback content --> </audio> Formate: MP3 vs Ogg Vorbis (vs WAV)
- 69. <canvas>
- 70. canvas = “scriptable images” <canvas width="…" height="…"></canvas>
- 71. canvas has standard API methods for drawing ctx = canvas.getContext("2d"); ctx.fillRect(x, y, width, height); ctx.beginPath(); ctx.moveTo(x, y); ctx.lineTo(x, y); ctx.bezierCurveTo(x1, y1, x2, y2, c1, c2); ctx.drawImage(…);
- 74. canvas und externe Bildformate ctx = canvas.getContext("2d"); var logo = new Image(); logo.src = 'logo.png'; ctx.drawImage(logo,x1,y1,w1,h1,x2,y2,w2,h2);
- 76. canvas zugriff auf Bilddaten ctx = canvas.getContext("2d"); canvasData = ctx.getImageData(x,y,w,h); [R,G,B,A,R,G,B,A,R,G,B,A,R,G,B,A, … ]
- 79. canvas und video ctx = canvas.getContext("2d"); v = document.getElementById('player'); ctx.drawImage(v,x1,y1,w1,h2,x2,y2,w2,h2);
- 83. video, audio und canvas auch auf Devices ohne “Steck-eins” (plugins) (nicht jeder hat Java / Flash / Silverlight)
- 86. HTML5 (und Freunde) hat viele APIs für Developer (für mächtige client-side Apps)
- 87. is it all safe to use, right now?
- 89. vorsicht: browser sniffing http://www.flickr.com/photos/timdorr/2096272747/
- 91. caniuse.com
- 92. feature-detection progressive enhancement, graceful degradation – or use shims http://diveintohtml5.org/everything.html
- 93. modernizr.com
- 94. yepnopejs.com
- 97. nicht die Frage ob HTML5 als Ersatz für Flash gut ist...
- 98. giving developers a choice!
- 99. ...ist HTML5 heute schon nutzbar?
- 100. “The future is already here – it's just not very evenly distributed” William Gibson
- 101. www.opera.com/developer patrick.lauke@opera.com