Introducing Professional JavaScript Frameworks, my first multi-author book project and the result of almost 2 years’ writing, editing, revising, and cat herding. The author roster changed a few times in the process, as did the editorial oversight, but finally the thing’s hitting shelves.
This one’s been a long time coming, but it’s finally sitting in my grubby little hands:
My contribution to this book includes all of the material from The Concise Guide to Dojo, plus a second concise guide worth of material on the MooTools JS framework. In addition to my work, you can find the work of Ara Pehlivanian on YUI, Scott Koon on Prototype, and Harley Jones on ExtJS.
Oh hey, look! It’s another blog post—and this one is cross-posted on hacks.mozilla.com. I won’t say this is the start of a renewed blogging habit, but let’s see what happens.
Drag and drop is one of the most fundamental interactions afforded by graphical user interfaces. In one gesture, it allows users to pair the selection of an object with the execution of an action, often including a second object in the operation. It’s a simple yet powerful UI concept used to support copying, list reordering, deletion (ala the Trash / Recycle Bin), and even the creation of link relationships.
Since it’s so fundamental, offering drag and drop in web
applications has been a no-brainer ever since browsers first
offered mouse events in DHTML. But, although
mousedown, mousemove, and
mouseup made it possible, the implementation has been
limited to the bounds of the browser window. Additionally,
since these events refer only to the object being dragged,
there’s a challenge to find the subject of the drop when
the interaction is completed.
Of course, that doesn’t prevent most modern JavaScript frameworks from abstracting away most of the problems and throwing in some flourishes while they’re at it. But, wouldn’t it be nice if browsers offered first-class support for drag and drop, and maybe even extended it beyond the window sandbox?
As it turns out, this very wish is answered by the HTML 5 specification section on new drag-and-drop events, and Firefox 3.5 includes an implementation of those events.
If you want to jump straight to the code, I’ve put together some simple demos of the new events.
I’ve even scratched an itch of my own and built the beginnings of an outline editor, where every draggable element is also a drop target—of which there could be dozens to hundreds in a complex document, something that gave me some minor hair-tearing moments in the past while trying to make do with plain old mouse events.
And, all the above can be downloaded or cloned from a GitHub repository I’ve created especially for this article—which continues after the jump.
Update 4/14: So, I liked rev="canonical", but I like the notion of pages offering sets of alternative URLs better. There are enough cracks in the case for rev="canonical" to stop caring about it and instead focus on the notion behind it. However it’s expressed—is it rel="shortlink" now?—the final remaining things I’d like to see are:
An more generalized scope for alternate URL choices asserted by publishers, not just URL shortening. Other criteria beyond character length include ease of entry on mobile devices (eg. short, but also simple, maybe mostly numeric), ease of verbal mention (eg. billboards, postcards, etc).
HTTP headers are great where available—hooray for HEAD—but it still needs to be in the page for publishers who can’t set custom headers.
Microformats are great, but I’d rather not parse a whole page to the footer to lift out the desired URLs.
Don’t panic. Have fun.
And with that, I’m going to try coming up with other things to write about so this blog doesn’t stay dormant. The rest of this entry remains unedited below…
So, it finally happened—I’ve been tagged by Stephen Donner. I’ve not been one to follow memes in this blog, but this one’s been going around the Mozillasphere for awhile now and has been kind of interesting. I’m half-tempted to bookmark and tag all the entries I’ve caught so far. Anyway, the rules:
Now, for your random facts, after the jump:
For the “too long; didn’t read” crowd:
Of course, I don’t really care what this means for folksonomy and the rest of Web 2.0—tags work for me on Delicious. So, I suspect this means I’m not entirely opposed to the sentiment in Do Tags Work?, because I don’t think tags work everywhere their use is attempted.
The rest of this entry elaborates on the above.
The Mozilla Tree
Behind Firefox is Mozilla, and behind Mozilla is a community. And the Mozilla community acts a lot like an ecosystem, which can be visualized as a kind of living tree—not to confused with the mozilla-central tree. Oh yeah, and Mozilla is the name of both a Foundation and a Corporation.
Confused yet? If not, then we should talk so you can explain it to me, because it all looks pretty tangly and intertwingled to me. Nonetheless, it seems to work, and produces a good chunk of my favorite software and technologies.
There are many efforts to track what’s going on—including planets and newsletters and bugzillas and wikis and repositories and tinderboxen. Some of these resources report on, or are driven by, the activity occurring in the others. Some are automated, and others are carefully stitched together by hand. None offer a full picture of what’s going on in the Mozilla galaxy in a way that’s casually comprehensible by a sane human being.
Of course, that’s not a slight against any of these sites or the people maintaining them—extracting an overview from such an organic phenomenon is neither easy nor straightforward. But, it might be fun to try.
As an infovore and avid practitioner of continuous partial attention, my first impulse is to reach for a firehose and stick my head into the stream. Relax, defocus, and try to let my pattern recognizers do their thing—sometimes those pattern recognizers are in my head, and sometimes they’re written in Python.
Firefox Victory!
But, for Mozilla, I couldn’t find a stream of sufficient volume or completeness to satisfy me or my robots. Happily, though, my feeding urge found itself aligned with a project to discover the patterns of contribution in the Mozilla community and to find a way to thank the contributors responsible.
So, while we’re still working on the thank-you angle, allow me to introduce you to the Lizardfeeder. The LizardFeeder is a feed aggregator, whose source code is built atop Sam Ruby’s Planet Venus. The LizardFeeder pulls together and archives activity streams from a wide variety of Mozilla community sources. Beyond the usual human-readable pages produced by a blog-gathering Planet, the LizardFeeder accumulates statistical and historical data meant for consumption and analysis by robots.
At present, the only robot navigating the LizardFeeder archives is an AJAX-ified user interface that animates the firehose as a near real-time or time-lapsed stream of events scrolling by.
This is just meant as a conversation starter, though. I’m hoping to gather feedback and find more sources, as well as to entice creative community members to come up with more sophisticated visualizations of this data.
So, take a look, check it out, and let me know what you think!
So, after all that, I suppose the thing to do for a new year is to figure out what’s next, maybe compose some disposable resolutions for the coming months. Well, here are some off the top of my head:
Note that most of what’s happened in my life over the past 3 years is missing from that list.
Hi there! My name is Leslie Michael Orchard. I'm a serially enthusiastic, caffeine-dependent {web,mad,computer} scientist and {tech,scifi} writer working for the Mozilla Corporation and living near Ann Arbor / Detroit in Michigan.
