London Web Standards – slides and further info

Sorry for the delay, but I finally got around to sticking my presentation from last month’s London Web Standards meet-up on slideshare. Slideshare is a bit naff to be honest, but it’ll do for now. If you click through to the talk on slideshare, you’ll be able to get my notes which should hopefully make the pictures more useful. Jake‘s busy syncing up both of our presentations to the videos so that we can show them on the BBC developer blog, so as soon as they’re available I’ll link those up too and you can view me in full hand-flapping, ranting form.

I think I speak for both of us when I say that we really enjoyed the evening – everyone was lovely and friendly and asked really excellent questions. Highly recommendable meet-up, and we’re both intending to try and make it to some of the future sessions.

Some useful links from my stuff:

London Web Standards Talks

Jake and I will be guests at March’s London Web Standards meetup. We’re giving a pair of JavaScript themed talks that should give plenty of fodder for the latter half of the evening’s discussion. I’m doing “Pro bun-fighting“, covering how we manage working on a large scale JavaScript project with a small team, our process, the performance and quality testing we do, and how to integrate group hugs, and Jake will be doing “The events left behind“, talking about the horrors of keyboard events, how to work around them and what’s their future.

Although it’s not a Glow specific talk, we will be using Glow in our examples, so feel free to come along and talk to us about the library too, if you’re interested.

Tickets are available now for the event on Wednesday 31st March at The Square Pig in London.

Github and QUnit

This year, Glow switched over to using Github as it’s code repository when it went open source to make collaboration easier. To be honest, getting used to git and github in general has been somewhat of an uphill battle for the team, but we’ve really found it’s come into it’s own recently now that we’ve adopted using submodules.

Glow 2 now includes Sizzle, Woosh and QUnit all as submodule projects of Glow, and doing so has instantly made Glow feel like a more team-playing product.

The whole many hands make light work approach is really quite good fun. For example, Jake started working up a design for Woosh, his new speed test framework for JS that he’s also open-sourced, which was making default QUnit look a bit… uh… under-loved, so I forked QUnit and started to reflect the designs, and over the last couple of weeks worked it up to something that the QUnit team have decided to accept back into the main project. Github made that extremely easy and now Glow, jQuery and the wider JS community benefits from a little bit of time spent making something that was essentially made to please just 3 pairs of eyes.

QUnit Theme, Screenshot by John Resig

Picture credits: QUnit Screenshot from John Resig’s Flickr Stream, designed by myself.