Watching code being written isn’t for everyone, especially beginners who might not be able to easily follow what’s happening, but it’s well suited to those that already understand the basics and just want to see how some particular function was written. It also provides an interesting look at how other developers work, which in turn might teach you a new trick or two.
The Code Player offers a variety of playback speeds depending on how fast you want to run through the tutorial, and there’s a timeline scrubber for pausing and rewinding any bits you miss. Our only complaint is that Code Player forces focus in the browser; when you try to click another tab or do something in the background Code Player steals focus back immediately.
If learning something new by watching someone else type sounds intriguing, head on over to the Code Player site. And don’t worry if the stopwatch demo has no appeal for you, there are plenty of other tutorials to choose from.
Given the amount of industry noise about native video and scripted animations, you’d be forgiven if you had never heard of the new microdata specification included in HTML5.
Similar to outside efforts like Microformats, HTML5′s microdata offers a way of extend HTML by adding custom vocabularies to your pages.
The easiest way to understand it is to consider a common use case. Let’s say you want list details about a business on your page — the name, address, telephone number and so on. To do that you’ll need to use some vocabulary in addition to HTML, since there is no <business> tag.
Using microdata, you can create your own custom name/value pairs to define a vocabulary that describes a business listing.
When a search engine spider comes along, it will know that not only is your data a business listing, but it can discover the address, the phone number, or even the precise geo-coordinates if you want to include them.
Given that HTML5 is still a draft at this point, why bother?
Actually, despite its lack of publicity and HTML5′s still-incomplete status, microdata is already being used by Google, which has started adding information gleaned from microdata markup to its search result snippets.
Not only has a very public (and contentious) debate unfolded on the web about the efficacy of presenting videos using HTML5 instead of Flash, but momentum is gathering behind the nascent web standard.
From giant video sites like YouTube to Wikipedia, everyone it seems wants to get their video out of Flash and into native web formats. With Microsoft recently announcing it will support the HTML5 video tag in the coming Internet Explorer 9, expect even more sites to abandon Flash for native video.
So, you want in on the fun? Do you want to use some HTML5 video tags on your site right now? No problem. Fasten your seat belts, as we’re about to take a tour of the wonderful world of HTML5 video.
If you’re anything like us, you’re always jumping on your cross-platform soapbox at the office. On mailing lists, over lunch, at parties, and on the bus home from the party (just in case the bus driver has been duped into supporting proprietary tags in his home page) you insist that everyone should follow W3C standards for HTML, CSS, and HTTP.
“Standards, standards, standards!”, you insist, as you pound on your podium. But do you actually test your own Web site for rigid W3C compliance? Be honest: Of course you don’t. You look at it with a couple of browsers, maybe a second computer, and just fix anything that looks wrong to your naked eye.
But if you really want to create cross-platform HTML and remove proprietary browser tricks from your site, you should be validating your HTML with the W3C’s HTML validator at validator.w3.org. The W3C validator is free to use and always up to date. And a more official source for standards specifications doesn’t exist.
Even better, you can augment the W3C specifications to include your own rules, such as forbidding nested tables. A “house rules” validator is an easy way to keep a team of developers from messing up each others’ work.