Downloaded 19 times
Uploaded byDave Bouwman
HTML5: Not Just for Breakfast
The document discusses the evolution of web technologies, highlighting key components such as semantic markup, CSS3, JavaScript, and browser extensions. It explores various device differences and the importance of creating custom view engines for different platforms, emphasizing the role of responsive design. Additionally, it includes resources and demos to illustrate the concepts presented.
More Related Content
Similar to HTML5: Not Just for Breakfast
HTML5: Not Just for Breakfast
- 1. NOT JUST FORBREAKFAST ANYMORE.Dave Bouwman, Head GeekMike Juniper, Javascript Ninja
- 2. I’ve seen theFUTUREandit’s myBROWSER
- 4. WeBob Muglia, VP,Microsoft
- 8.
- 9. Bret Taylor, CTO,FaceBook
- 11.
- 12.
- 13.
- 14. <div id=“header”><div id=“nav”><divclass=“article”><div id=“sidebar”><div class=“section”><div id=“footer”>
- 15.
- 16.
- 17.
- 18. Where is MAIKitteh!
- 19.
- 20.
- 21.
- 22. GeolocationLocal storageWebGL, Canvas*,WebWorkers, SVG*, Drag & Drop Geolocationhttp://www.flickr.com/photos/hendry/3642114424
- 23. key : valueLocalStorage
- 24.
- 25.
- 26.
- 28.
- 31.
- 32.
- 33.
- 35.
- 36.
- 37.
- 38. I think incode…
- 39.
- 40.
- 41.
- 44.
- 45.
- 46. ControllerCustomViewEngineRequestViewMobileViewiPadViewDesktopViewHTML + JavascriptjQueryMobileHTML+ JavascriptOrientation AwareHTML + JavascriptUserAgent?Views
- 47.
- 48.
- 49.
- 50. ControllerCustomViewEngineRequestViewSmall ScreenViewLarge ScreenViewHTML+ JavascriptHTML + JavascriptUserAgent +WURFLViews
- 51. Browser Capabilities addedin CustomViews
- 52.
- 53. Aw man… Ihate server side code
- 54. Modernizr + Jquery+ partials
- 57. I’ve seen theFUTUREandit’s myBROWSER
- 58.
Editor's Notes
- #4 And we all know Google Loves HTML – Google Apps is a web based version of an office suite, but if that’s not enough, they also wrote a love story about HTML5And recently, on Google has been re-mixing their logo using adding HTML5 – this one is an interactive tribute to 20,000 leagues under the sea
- #7 Silverlight FirestarterGu, Tim Heuer, John Papa, Jesse Liberty and other cogniscenti all to try and convince everyone that MS loved Silverlight and that seemed to have worked for a while, until last week’s MVP summit where the ASP.NET team were spotted rollin like this. Anyhow Microsoft clearly loves HTML5 AND Silverlight
- #9 Native is for “high touch” things. Web is for low touch.
- #10 FaceBook supports 18 native applications – too much! Moving to HTML5… even farmville!
- #11 So we have 4 of the largest technology companies agreeing (to some degree) that HTML5 is the future… but
- #12 What IS HTML5
- #13 For the purposes of this talk I’t really 3
- #15 So if we look at a typical page layout… divs and pretty common ID’s and Classes – which mean things to you and I, but not to the machine…
- #16 With HTML5, we get new DOM elements, which have semantic meaning.
- #17 Allows computers to “understand” the content better
- #19 Gradients and rounded corners – help avoid using images on pages. We also have much wider support for web fonts, which now allows
- #24 Also WebDB – relational database in the browser.
- #25 As well as some other less widely implemented stuff
- #26 Google Body Browser in Chrome to see what this is all about.
- #27 So – HTML5 brings unicorsand rainbows to the world. Great… just
- #28 There are two things to contend with
- #29 The second problem is IE
- #32 It’s not just that IE does not support HTML5 in any meaningful way, even more important is javascript performanceSo – the latest version of IE is >5 times slower than other more modern browsers. And IE 6 and 7 are more than double that!So the simple answer has been to use Flex of Silverlight
- #33 Desktopvs tablets vs phones – very different screen sizes, and user xpectations
- #34 This alone means that you need a separate “view” for touch devices – also note that Flex on Android != same app for desktop and mobile!
- #35 So – what do we do? Multiple devices, form factors, javascript environments
- #36 Since we have different needs for different client devices, lets drop the idea that we can create ONE thing and run it everywhere – use some infrastructure to create optimized views for each device.
- #49 Ags2.dtsagile.com/arcstache
- #52 WURFL
- #53 Ags2.dtsagile.com/arcstache