The code itself is Javascript that uses a jQuery template for results. It’s heavily ripped off from the existing Google search command (with the site:lifehacker.com operator thrown in). If you haven’t tried out Ubiquity, here’s my introductory tutorial.

The new release is only a minor point upgrade but feature-wise it’s major: now you can configure whatever meta-lookups your heart desires in the menu all by yourself. (This will also head off all that email I get from folks requesting that I add their new webapp to the menu.)

Current About This Site users can upgrade just using the auto-update feature; go to your Add-ons in Firefox, right click on About This Site and hit “Find Update.”

What’s more, the fine folks at Lifehacker are funding some of my whimsical open source development efforts, so the extension and some more little utilities I’ve got in the works will be hosted there, under the new Lifehacker Code tag.

A girl cannot subsist on blogging alone. Meep.

After many hours of cursing myself for not having a better debugging system, I discovered it was a PHP 4 versus PHP 5 code incompatibility. Turns out that PHP passes arrays into foreach loops by value, which means that any changes you make to that array inside the foreach don’t appear after the foreach, because it’s acting on a copy of the arrray instead of the original data.

So code like this:

Doesn’t print “nothingnothing”, which is what I’d expect; it prints “rainbowspuppies.” In PHP4, apparently, there’s no way to get around this. In PHP5, you can pass the array into the foreach by reference using this notation: foreach ($gina->interests as & $interest)

For now, I to make my code both PHP4 and PHP5 compatible, I went with a:

while ($i=0; $i < sizeof($gina->interests); $i++)

Which just isn’t as readable as the foreach. Here’s the PHP doc on foreach (which clearly states the PHP 5 caveat.)

So, inspired by PB’s graphing post and a curiosity about Amazon’s API, I set out to write a little something that would help me visualize what’s happening with the book’s sales over time. I didn’t get into the hardcore tools Paul did - just the names RRDTool or SNMP scare me - so I instead opted for the very no-frills, Flash-based PHP/SWF graphs. After registering for a free key, I was delighted to find that the Amazon API is dead simple. In less than 30 minutes of a little PHP/MySQL hacking, I had a sales rank capture-and-graph set of PHP scripts. It’s turned out to be a really nice way to keep an eye out without reloading the book’s Amazon page 4 times a day like a total egotistical loser.

Here’s the finished Lifehacker book Amazon sales rank charter. Screengrab below:

Two years and one point one version later, I’ve revisited Mozilla’s extension development docs, processes and community. What an improvement! You can actually make changes to your extension and see them without repackaging, uninstalling, restarting, reinstalling and restarting again! There’s a fabulous Extension Maker wizard that produces an extension skeleton starter file set, and batch scripts to do the packaging for you. It’s all very exciting. Here are some tools and reference links I used to update my extensions:

• The aformentioned Extension Wizard
• Setting up the extension development environment [Mozillazine]
• Getting started with extension development [Mozillazine]

When I was done updating all my extensions, I got all uppity and submitted one to the Mozilla Add-ons directory. To my surprise and dismay/happiness, an editor tested it and rejected the submission because the extension threw a Javascript error! (An error that didn’t keep it from working, mind you, just cluttered up the Error Console.) I was pretty impressed with their vigilance (and sheepish about my shitty code), so I fixed it and re-submitted. It just got accepted.

Here’s a final list of my completed (and very simple) extensions, now compatible with Firefox 2.0:

• About This Site (here it is on Mozilla Update)
• Show Screen Captures
• Text Area Word Counter

I’ve got a few more extension ideas in the works, especially for web writers.

Notes on Mozilla Update: The great thing about hosting your extension there is that they take care of the auto-update on new versions, count your downloads for you, have per-extension comments enabled and are generally considered a trusted source for extensions (because they, you know, actually test them, as I found out). The bad part is that to host on Mozilla Update, you have to remove your custom auto-update URL from the install.rdf file. So, if you want to host your own extension (like say, to run ads on the page or include them in your custom portfolio) in addition to making it available on Mozilla Update, you have to build TWO separate versions - one, without an updateUrl set for Mozilla Update and one WITH an updateUrl for your own hosted version. That part kinda sucks.