If you have an iPhone or an iPod Touch, be sure to check out this very nifty jQuery reference app. It doesn’t take long to install and, best of all, it doesn’t involve the app store at all—the whole thing is built with HTML, CSS and JavaScript using HTML5’s offline storage. Now, no matter where you are, you’ll always have access to jQuery documentation …as long as the battery in your phone lasts, anyway.

In short, it was superb. I’ve been to quite a few conferences in my time so I can get pretty jaded but this was a textbook lesson in how to put on a great event.

The content was top-notch. The fact that the whole day was focused on a single technology gave it a very cohesive feel. That said, there was still a wide variety of topics covered: mobile, accessibility, performance, and even server-side JavaScript. The intensity and complexity increased as the day went on, finishing with Simon blowing everyone’s minds.

All the speakers were great but special mention must go to Jake Archibald from the BBC. His talk on JavaScript performance was thoroughly entertaining and informative —a very tricky combination to do successfully. He made the presentation look effortless but there must have been months of preparation involved. That kind of spontaneity takes years of practice.

If you weren’t lucky enough to make it to Full Frontal, you can check out the speakers’ slides on the website but really, you should have been there.

Congratulations and kudos to Remy for putting together such a world-class event. I sincerely hope there’ll be a Full Frontal 2010, but it’ll be hard to match the standard set by this year’s conference.

Fronteers 2009 is a two-day event in Amsterdam on November 5th and 6th. John Resig and Douglas Crockford—that alone makes it worth the price of admission.

Straight after that, JSConf.eu takes place in Berlin on November 7th and 8th. It’s a tight squeeze but it would possible to go to both events with a train ride in-between. I wonder if that’s what John is going to do; he’s speaking at both conferences.

But the highlight of the month still looks like being Full Frontal on November 20th. That’ll be held right here in Brighton which probably explains why I’m kind of biased. But seriously, check out the line-up:

• Peter-Paul Koch,
• Christian Heilmann,
• Simon Willison

…and more.

You can still grab tickets for the early-price of just one hundred squid.

This year’s be-there-or-be-square JavaScript event is the newly-announced Full Frontal conference to be held at the fantastic Duke Of York’s Picturehouse in Brighton on November 20th:

full-fron•tal (JavaScript):

with nothing concealed or held back.

It’s being organised by Remy Sharp. Doesn’t this guy ever sleep? Not content with creating JS Bin and the JQuery API browser, and writing a book on jQuery for Designers, now he’s going to organise a conference too.

It looks like being an absolute bargain. A mere £100 will get you a ticket to a day of serious JavaScript talks from some of the smartest people in the business: Christian Heilmann, Peter-Paul Koch, Stuart Langridge, Simon Willison, and more.

Best of all, I don’t have to travel anywhere for this conference as it’s being held in my adopted hometown of Brighton. But if you do have to travel, I can think of now better place to travel to. Come along and I’ll make sure the geeks of Brighton welcome you.

Tickets are on sale now.

You can read all about how it was made or you can simply go and play around with it …go ahead; click on stuff.

Phil’s co-worker Paul Downey is responsible for such printed masterpieces as The Web Is Agreement and The URI Is The Thing. He has now created a printable version of Unobtrusify. Head on over to archive.org, download and print to your heart’s content.

Now I just need to find some sticky material so I can slap my copy up next to my desk.

This release features some significant changes and improvements. There’s all the usual speed improvements, of course, but what I like in particular is the way that jQuery is ditching browser sniffing in favour of feature detection. That’s the way to do it.

The way the community is developing is as interesting as the code. Sizzle, the CSS selector engine inside jQuery, has been spun off into its own standalone project so that it can be used by other libraries and frameworks. Meanwhile, the jQuery project itself is coming under the banner of the Software Freedom Conservancy to formalise its standing as free and open software.

Congratulations to John and the rest of the team. Congratulations also to fellow Brightonian Remy Sharp for putting together the very handy jQuery API browser. The boy done good.

At Clearleft, we often use pastebin.com though I’ve also used dpaste in the past. I like the way that pastebin allows you to create subdomains on the fly: just type in the URL to create it.

These services are great for collaborative debugging but they have one slight flaw when it comes to client-side work. JavaScript and CSS don’t exist in isolation; they are used to enhance an existing HTML document. So passing around a snippet of JavaScript or CSS might not be much good unless it is accompanied by the corresponding markup.

Enter JS Bin from Brighton’s own Remy Sharp, the man behind the superb microformats bookmarklet. This is a paste bin with a twist. As well as being able to share a snippet of JavaScript, you provide the markup that the JavaScript is acting on as well. If you’ve been sent a JS Bin URL, you can play around with the JavaScript and/or the markup, saving as you go.

There are some other nice touches too, like the ability to include a JavaScript library at the flick of a dropdown. For a proper explanation, be sure to watch the screencast that Remy has recorded.

Just for kicks, John has created a standalone selector engine called Sizzle. It’s not quite ready for prime time yet but it looks very promising. It uses the CSS syntax that has helped make jQuery such a popular library. Right now, the code is coming in at less than 4K!

I really, really like this modular approach to writing JavaScript. Instead of bloating a library with more features, the components of the library are instead being split into separate standalone pieces. I wonder if the same thing will happen with event handling and effects. Those three actions (selector, event, effect) probably make up 80% of jQuery use cases:

jQuery(selector).event(function() {
 effect();
});

For an event of a different kind, there’s a jQuery Camp scheduled for September 28th, the day before The Ajax Experience in Boston. The exact location has yet to be determined but given the number of jQuery fanboys out there, I’m guessing it won’t be ‘round at John’s house. There’s a nominal registration fee of $50 to cover lunch. If you use jQuery and you find yourself anywhere on the eastern seaboard of the United States at the end of September, you should probably register now.

In his spare time, John likes to relax by porting the Processing visualisation language to JavaScript. Freak.

Meanwhile, as the JavaScript libraries continue to evolve and improve, the browser engines are also focusing on speed improvements. Dave Hyatt and the WebKit gang have announced a brand new JavaScript engine called SquirrelFish. This looks like being about 60% faster than the previous WebKit interpreter so you can expect quite a speed boost in the next version of Safari.

If you’re interested in what happens under the hood with Squirrel Engine, Dave shares some of the philosophical underpinnings:

SquirrelFish owes a lot of its design to some of the latest research in the field of efficient virtual machines, including research done by Professor M. Anton Ertl, et al, Professor David Gregg, et al, and the developers of the Lua programming language.

You can find plenty of gory details on the Surfin’ Safari blog.

Take a look at the UK and Ireland TV and radio listings on Yahoo. See that search form in the upper right corner? It’s using the standard design pattern of allowing you to specify exactly where you’re searching. But unlike most implementations, this one is built on a rock-solid foundation of semantic markup.

Steve Marshall has the lowdown. Under the hood the form is using radio buttons for choosing where to search. Then, using a combination of JavaScript and CSS, this default representation is augmented to look and behave as desired. Switch off JavaScript and you can still use the search form perfectly well.

What impresses me about this isn’t so much the code (although I’m sure it’s top-notch), it’s the thinking behind the implementation: start with solid semantic markup with good ol’ fashioned form elements for interaction; then think about how it can be enhanced. Nice one, Steve.