transmission 2. pat lauke (opera): future of web technologies
DESCRIPTION
Pat Lauke's presentation from Transmission #2 - 'Innovation Online: Where next for the web?'. Part of the Digital Sparks programme presented by Northwest Vision and Media, delivered by The White RoomTRANSCRIPT
The future of web technologies
Patrick H. Lauke / Transmission2 #tx2 / Manchester / 25 November 2009
WEB STANDARDS, CROSS-DEVICE DEVELOPMENT AND THE WEB AS UBIQUITOUS PLATFORM
Web Evangelist at Opera
1. new web standards2. adaptive content3. browser as platform
1. new web standards2. adaptive content3. browser as platform
new technologies you can start using today
HTML5<!DOCTYPE html>
HTML5 does not replace HTML 4.01
HTML5 has more bling!
“...extending the language to better support Web applications, since that is one of the directions the Web is going in and is one of the areas least well served by HTML so far. This puts HTML in direct competition with other technologies intended for applications deployed over the Web, in particular Flash and Silverlight.”
Ian Hickson, Editor of HTML5http://lists.w3.org/Archives/Public/public-html/2009Jan/0215.html
HTML5 is umbrella term:markup elements and JavaScript APIs
new elements for more accurate semantics
HTML5 elements for a typical blog
HTML5 – unambiguous and machine readable
current and old browsers “support” these new elements
(although some need a little extra help)
webforms – more powerful form elements
standardise commonly-usedrich form elements – without JavaScript
built-in validation(of course you should still validate on the server)
Demonstration of webforms
<canvas>
canvas = “scriptable images”
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);
canvas mixing things up with external graphics
ctx = canvas.drawImage(…)
Demonstration of canvas
<video>
<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&fs=1&" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed></object>
<video src="video.ogv" controls autoplay poster="poster.jpg" width="320" height="240"> <a href="video.ogv">Download movie</a></video>
video as native object...why is it important?
● “play nice” with rest of the page● keyboard accessibility built-in● API for controls
Demonstration of video in Presto 2.4
video format debates – MP4 vs OGG Theora
<video controls autoplay poster="…" width="…" height="…"><source src="movie.ogv" type="video/ogg" /><source src="movie.mp4" type="video/mp4" /><!-- fallback content -->
</video>
still include fallback for old browsershttp://camendesign.com/code/video_for_everybody
video and canvas on any devicewithout plugins
(Java / Flash / Silverlight not ubiquitous)
IANAL, but … EOLAS?
and many more...(geolocation, drag and drop, web workers, offline support, storage)
1. new web standards2. adaptive content3. browser as platform
Opera Mini: +150% users, +224% traffic15 Billion pages served / month
September 2008 - 2009
"Our goal is to take the one true Web and make it available to people on their terms."
Jon S. von Tetzchner, Opera Co-founder & CEO
“One Web” is an uneven landscape:
● constrained browsers (WAP, …)● mobile “Full Web” (Android, Opera Mobile, …)● proxy-based (Opera Mini, …)● laptop, Netbook, Tablet PC, Desktop● games consoles, set-top boxes, TVs
Device capabilities also vary:
● screen size and resolution● input mechanism – touch, keypad, other?● memory and processing power● colour palettes● connection speed / quality
Approaches to cross-device development:
● do nothing – use standards, defensive design● separate site (m.mysite.com, mysite.mobi)● single site, but optimised for cross-device
CSS 2.1 Media Types:
● print, screen, handheld, projection, tv, …● partially supported● lump all devices into single categories
http://www.w3.org/TR/CSS21/media.html
CSS 2.1 Media Types:
<link rel="stylesheet" ... media="print" href="...">@import url("...") print;@media print { // insert CSS rules here}
CSS 3 Media Queries:
● build and extend CSS 2.1 Media Types● more granular control of capabilities● width, height, orientation, color, resolution, …
http://www.w3.org/TR/css3-mediaqueries/
CSS 3 Media Queries:
@media screen and (max-device-width: 480px) { // insert CSS rules here
}Demonstration of Media Queries
CSS 3 Media Queries and SVG:
● SVG already resolution independent● ideal for device interfaces, maps, graphs, …● combination with CSS 3 Media Queries
Demonstration of Media Queries + SVG
1. new web standards2. adaptive content3. browser as platform
Full Web is not always practical or desirable
Widgets are nothing newYahoo! Widgets (aka Konfabulator), OS X Dashboard, Windows Sidebar,
Adobe Air, iPhone Apps, Android Apps, …
“…the browser run-time is perfect…you’re out of writing for Windows Mobile, Android, S60, each of which require testing...we want to abstract that.
All the cool innovation is happening inside the browser – you don’t need to write to the native operating system anymore.”
Mobile Entertainment Market , June, 2009
W3C Widgets – application development filled with web standards goodness,
using browser engine as platform
Widgets on desktop, mobile, TV … fridge?
Opera had widget capability for a long time … latest 10.20 alpha widgets as standalone apps
dev.opera.com/articles/view/widgets-as-standalone-applications
Standardised JavaScript APIsto access device-specific capabilities
(JIL / BONDI)
1. new web standards2. adaptive content3. browser as platform
www.opera.com/developerpeople.opera.com/patrickl/presentations/Transmission2_25.11.2009/Transmission2_25.11.2009.pdf