Archive for the ‘HTML5’ Category

File Under: HTML5, Web Standards
Sep
20
2012

W3C Unveils Plan to Finish HTML5 in 2014

By

Image: Screenshot/Webmonkey.

Like the Cylons, HTML5 was created by man. It rebelled. It evolved. It looks and feels like HTML. And now, it has a plan.

Namely, to be done in 2014.

The W3C has formalized its plan to move the HTML5 spec to the official “Candidate Recommendation” status by the end of 2014. That might seem like a long time from now, especially if, like most of us, you’ve been using the bulk of HTML5 for some time, but 2014 is quite a bit better than the 2022 date that used to be tossed around.

But there’s a catch. In order to get HTML5 to the Candidate Recommendation stage on time the W3C is going to move some less stable parts of the spec to the newly designated HTML 5.1.

HTML5 has already been “modularized” over the years, spinning off sections like Web Workers, WebSockets, Microdata and half a dozen others, which are all now separate specifications at the W3C.

Now the W3C plans to split the remaining chunk of HTML 5.0 into HTML 5.0 and HTML 5.1. Each spec will then move through the process of becoming an official web standard. Here’s the W3C HTML Working Group’s plan for HTML5:

  • we determine which features are likely to meet the “Public Permissive” CR exit criteria,
  • we create a “stable HTML5.0″ draft which includes just those “stable” features, and which omits the remaining “unstable” features
  • we create an HTML 5.1 editor’s draft which is a superset of the stable HTML5.0 but with the “unstable” features included instead of omitted, and also with any new proposed features included

The HTML WG would then rinse and repeat with HTML5.1 in 2016. And then HTML5.2 and so on. The result will hopefully be a faster evolving series of specs, which in turn means more features reach the Recommendation stage in less time.

For web developers in the trenches finalizing HTML5 might seem irrelevant — after all, browsers already support most of it so who really cares? There are two reasons reaching the Candidate Recommendation stage matters: It usually means improved cross-browser support and it always means that the spec is covered by the all important W3C patent policy, which ensures that HTML5 remains a royalty-free standard.

For a complete list of everything that’s “unstable” in the current draft of HTML5, as well as the plan for how to handle it, be sure to read through the W3C’s plan.

Tags: ,
File Under: HTML5, Multimedia
Aug
30
2012

Microsoft, Atari Bring Arcade Classics to the Web

By

Centipede in HTML on the iPad. Image:Screenshot/Webmonkey

Microsoft’s Internet Explorer team has partnered with Atari to re-imagine classic Atari games for the modern web. That’s right, Centipede, Asteroids, Missile Command and half a dozen more all re-written using HTML5 and JavaScript.

If you’d like to play, point your browser to the new Atari Arcade and enjoy the glory of Pong, Super Breakout and the rest of the Atari back catalog.

While the games look a bit different — the graphics aren’t exactly what you might remember from the arcades of your youth, hence the “re-imagining” — the game play is faithful to the originals, especially on a touch screen where the controls are more like the classic arcade button layouts.

For those curious to know how it all works, the answer is largely CreateJS, though for full details be sure to read through the developer documentation. You can even create your own HTML5 Game on top of the new Atari Arcade SDK.

For more details on how it all works check out the video below featuring developer Grant Skinner and the rest of the team behind Atari Arcade.

Tags:
File Under: HTML5, Web Basics
Aug
29
2012

Popular ‘HTML5 Boilerplate’ Hits 4.0

By

HTML5 Boilerplate, easy to bolt on. Image: Les Chatfield/Flickr

The developers behind HTML5 Boilerplate have released version 4 of their boilerplate HTML, CSS and JavaScript templates for quickly prototyping HTML5 designs.

You can grab a copy of HTML5 Boilerplate v4.0 from the HTML5 Boilerplate website.

This release is notable for a number of changes including a snazzy new website, cleaned up and reorganized code and the beginnings of a high-resolution-screen @media query. This release is also notable for what it lacks, namely the trademark pink text highlight color which has been ditched in favor of a more neutral blue.

Version 4 of Boilerplate also updates the various code libraries that Boilerplate relies on, including jQuery, Modernizer and the very awesome Normalize.css.

You can see the complete changelog for this version over on Github and get any help you might need with HTML5 Boilerplate at Stack Overflow.

Tags:
File Under: HTML, HTML5, Web Standards
Jul
30
2012

W3C Names Four New HTML Editors

By

The World Wide Web Consortium (W3C) has named four new editors of the HTML5 spec to replace departing editor Ian Hickson.

The W3C’s HTML Working Group co-chair Paul Cotton announced the four-way editorship in a e-mail to the W3C’s public HTML mailing list.

The four new editors include two Microsoft employees, Travis Leithead and Erika Doyle Navara, Apple’s Ted O’Conner and Silvia Pfeiffer of Ginger Technologies, a company specializing in HTML video.

“The Chairs received a large number of applications for the position of HTML5 editor,” writes Cotton. “After evaluating all the applications, we chose the above HTML5 editorial team based on the individual qualifications of the new editors as well as the combination of the individual appointee’s qualifications.”

The heavy representation of Microsoft is interesting given that Microsoft is not currently a member of the Web Hypertext Application Technology Working Group (WHATWG), the other standards body that oversees HTML. It would seem that Microsoft is doubling down on the W3C version of HTML.

The editor change is part of the recent split that sees the two standards bodies jointly responsible for developing the HTML specification, moving in different directions.

The W3C and the WHATWG have long acted as separate bodies, but previously shared an editor, Ian Hickson, who helped ensure that the two specs remained in sync. Then last year the WHATWG announced it was dropping the “5″ version number and would work on HTML as a “living standard” sans version numbers. The W3C continued to focus on HTML “snapshots” like HTML5.

“The WHATWG effort is focused on developing the canonical description of HTML,” wrote when he stepped down as W3C editor last week. “The W3C effort, meanwhile, is now focused on creating a snapshot developed according to the venerable W3C process.”

Tags: , , ,
File Under: APIs, HTML5
Jul
23
2012

Chrome 21 Adds New Drag-and-Drop Tricks

By

HTML5 offers developers a File API with drag-and-drop support to make web apps behave a bit more like desktop apps. Provided you’ve got a modern web browser and are using a web app that supports it (Gmail and Flickr are among the hundreds that do), uploading files works just like moving files on the desktop — drag and drop them where you want them.

The key word there is files, though. Drag and drop a folder of files and you’re out of luck. Currently browsers just ignore folders dropped into them. Chrome, however, recently added folder support to its bag of drag-and-drop tricks. You’ll need to be using Chrome 21 or better (currently in the dev channel).

If you’d like to see how the new folder parsing works, HTML5Rocks has a quick little tutorial on how you can add support for folders to your web app.

The JavaScript required to support folders consists of an extra loop to tunnel through folders and get to “Entry” objects. That’s a slightly different syntax than what you might have seen if you’ve read tutorials on the File API in the past — using “Entry” instead of “File”. There are two new properties as well — .isFile and .isDirectory.

As always with cutting edge tools, we don’t suggest using this one in the wild just yet. You’ll need Chrome 21 or better for it to work and it’s not yet an official standard, but you can learn more over at the WHATWG wiki.

« OLDER POSTS