I’d love to dive right in and show you how it all works in cujo.js, but you’ve got to have a firm understanding of OOCSS for any of it to make sense. Let’s get started…
Here is the slideshow from my presentation at the Bocoup Loft on August 15th. For some reason, slideshare barfed on it even after I removed all of the video and audio. Srsly, I tried five different variations.
dojo is bizarro jQuery (bocoup)
This presentation is in the QuickTime Presentation format. You must use the space bar or arrow keys to navigate. (I seem to have to click and hit the arrow keys about a dozen times before the presentation starts.)
I finally got slideshare to accept the slides! Here’s the sideshow.
It’s no secret that one of the keys to a decent user experience is a responsive (fast) user interface. And the most critical component to a fast web app is minimizing the HTTP requests. So it’s no mystery that people are working on ways to solve this problem.
Firefox, of course, is one of the leaders in this area. Their proposal started out fine. Here’s a sample of what it would look like (if you didn’t read the article):
But for some reason, this concise, nearly-valid implementation was trashed in favor of a terse, unfamiliar, and nearly unusable alternative. Here’s what the spec looks like now:
<html packages='[pkg1.zip img1.png script.js styles/style.css]
In this bastardization, the packages are specified as an attribute on the document element (
<html> tag). Package definitions in the
packages attribute are delimited by square brackets, and the resources within them are delimited by spaces.
WTF? Not only is this ugly and non-standard, but it also has some serious drawbacks. Here’s why:
CSS, cujo.js, dojo, HTML / DHTML, In-browser MVC