Don’t get too excited, it doesn’t do most of the good stuff such as actionscript, filters, sound, strokes … the list of “unsupported” goes on and on.
It is, however, nice to see Adobe embracing HTML5 as a standard, and moving beyond the Flash / HTML5 games.
I’m going to start publishing, every Friday, a list of some useful / interesting links I’ve visited throughout the course of the week.
Usually this will involve whatever I am working on at the moment. If you like these links, you can follow me on Twitter to get them as I find them (as opposed to waiting for Friday).
This week I’ve been working a lot with jQuery (nothing new), Flowplayer, and CSS. An average week for a web developer.
Way back when, in the times of HTML 4, and CSS was just getting started we worked with IE6. IE6 required us to do everything differently, because of the ways things were implemented. They just had to be different.
Fast forward to 2011. The world is rapidly expanding use of an incomplete spec, HTML5, and things seem OK. Browsers support it, the implementations seem pretty consistent.
Starting in a few months, Google will be dropping H.264 support in Chromew.
This is done to push support for the new WebM (VP8) codec.
Just announced, and it means for those of us who implemented the HTML5 video tag, time to go back and make sure the video is available in WebM or Theora.
Part of the trials and tribulations of working with a partial spec. This is just going to make our work as web developers more difficult.
I’m reading through the Interoperable HTML Parsing in IE9 blog post on MSDN and there are some nice, and some not so nice things.
The following are some subjects talked about, and what it means for us web developers.
I grew up with webmonkey as the single best destination for web developers and any tutorial you could want, but just saw that Google has a Google Code University featuring Tutorials, Contributed course content and Video lectures on:
- Web Programming
- Web Security (yes, web developers should be well versed in Web Security)
Just looking through the site it is so much more than basic web development. Material covers topics ranging from the Android platform, to basic algorithms. Please check out the material that isn’t just web development. There’s a reason Google is providing content for Distributed Systems, Tools and working with APIs.
We’re never beyond refreshing our own skills, as I’m sure Google has some great advice on their site.
I wish I could send this link to some other web developer’s I’ve had to rescue projects from.
In the very near future, I will be posting a series of posts on what you should/shouldn’t be doing to develop a website where the iPhone and iPad are a target demographic. jQuery will figure prominently in the series, as I’ve seen almost all websites now require work with jQuery (or anther AJAX platform).
Let me know if you have any specific questions / concerns, and I’ll be glad to answer them.
Some interesting things to think about:
- How are mouse clicks triggered? (It’s not as straightforward as you’d think)
- How are hover states triggered? (Hint: the iPad has a hover state, but it’s not what you think — remember you only have a single touch, no arrow following your finger)
- What types of gestures can we use?
- What special considerations must we make for CSS?
- What are the ideal screen dimensions? (this is easy, but remember we have multiple devices, and multiple orientations)
- What types of video can we play? (iPad, iPhone 3GS, iPhone 3G, iPhone 2G and the original iPhone all have different specifications, it’s not that easy)
Everywhere I look on the web (the web developer web that is) is CSS3 this, jQuery that, shadows, HTML5.
Such a tease, what about our minimum browser requirements spec? Damn IE6 is yet again 10% of the target demographic.
Not only is IE6 the problem, but so is the most recent IE8, as well as IE7. They just don’t support CSS3 and HTML5.
Now we have some solutions…
Apple released their HTML5 Showcase a month or so ago. It was cool, but the showcase required Safari to view it (not sure if this is a technical limitation, or just marketing making the decision).
Some of the featured experiments:
- Sketchpad – We’ve seen this before, showing off the ability to create vector graphics in HTML5 (we’ve linked to this before)
- Canopy – Impressive fractal zoomer implemented with HTML5
- Browser Ball – Some interesting animation of an element between windows.
- Wavy Scrollbars – physics simulation using browser scrollbars.
- Pong – Pong implemented through browser windows (annoying sound warning)
- Google Gravity – Physics applied to the Google homepage (demos very nicely physics as well as CSS rotations)
- Harmony – Sketching app
- Destructive Video – This is cool, blow apart a playing video (I’ve linked to this before) — notice how the video keeps playing
- Ball Pool – Another physics demo … rotations, animations, large numbers of objects.
In conversations with designers and developers we have been discussing the pro and cons of using HTML5 video instead of Flash. Sites that support iPad / iPhone need HTML5 as an option, and recently has been driving project’s to require non Flash video.
YouTube’s API Blog published an article yesterday, Flash and the HTML5 <video> tag, which goes over the major points of the argument from one of the most influential players in the Flash vs. HTML5 market. It’s important to keep in mind while reading, that YouTube is owned by Google, and is positioned opposite Apple on many issues (this is far from impartial, but the points are applicable anyway).