May 4th, 2009 by Aaron N.
I had a nice email exchange with one of the guys on the Firebug team recently. Basically, I miss Firebug 1.2 w/ Firefox 2.0, but Firefox 3 has some features I really don’t want to live without. In our email conversation, I shared a laundry list of issues that I’ve observed Firebug 1.3 doing that make my life less awesome.
Anyway, one of the suggestions I got was to upgrade to the alpha version of Firebug 1.4 and, I gotta say, it’s worth it. It’s not quite as solid as things were back on Firefox 2, but it’s way better than Firebug 1.3.
You can grab the latest builds here: http://getfirebug.com/releases/firebug/1.4/?C=M;O=A (My Firebug friend recommends the most-recent, currently 1.4a22).
Posted in Browser Plugins | 8 Comments »
January 13th, 2009 by Aaron N.
This is actually kind of old news, but it’s something that never really got released. Valerio and I spent a few weeks a while back putting together a bookmarklet that would give you a Firebug-style JavaScript console for browsers without Firebug (IE, Safari, etc).
It supports console.log statements in the various formats that Firebug supports (“console.log(‘foo: %s, bar: %o’, foo, bar);”) and is really useful for debugging your code in non-Firebug browsers. I like to use it in conjunction with X-RAY to solve layout issues, too.
To use it, all you need to do is drag the link on the bookmarklet page into your bookmarks and then click it on any page to bring up the console (I.E. you have to right click and choose “Add to Favorites”).
You can see it in action on the test page.
Note: If you have Firebug installed and enabled, it doesn’t do anything.
Posted in Browser Plugins, MooTools | 16 Comments »
December 3rd, 2008 by Aaron N.
Over on the MooTools Google group, David Nolen (of ShiftSpace) writes:
For those of you who are GreaseMonkey hackers I’ve created a fork of MooTools Core on GitHub that can be loaded into a GreaseMonkey script via @require. We’ve been using this fork for our open source meta/hack/web project ShiftSpace. You’ll need need to have ruby and the json ruby gem installed on your machine in order to build the mootools-core.js file.
Of course there may be issues, if you run into trouble let us know.
Get it here:
http://github.com/swannodette/mootools-core/tree/master
Posted in 'Industry' News, Browser Plugins, MooTools | Comments Off
June 23rd, 2008 by Aaron N.
Ajaxian has a post up this morning on Jiffy, a Firebug plugin “that adds a new tab showing fine grained performance data. You want to know the time between the onunload of the previous page, the first rendering, time until onload, time after, and more.”

The Ajaxian article has a nice overview, and the post by Bill Scott (Rico, ex-Yahoo, now @ Netflix) is really detailed and worth reading. Good stuff.
Posted in Browser Plugins | Comments Off
June 19th, 2008 by Aaron N.
I’ve been putting off upgrading to FF3 only because I know it’ll mean that at least some of my stuff won’t work. Whether it’s a web site I use often or a plugin (like Firebug), my official policy is to wait a month or two until I start using a new browser.
Given that it’s rather difficult to run multiple versions of browsers side by side (why do they do this? certainly the developers of these things have to be able to switch around from one version to another, right?), this often means using a virtual machine for my testing.
Well, not anymore (for OSX users at least): MultiFirefox
Posted in Browser Plugins | 7 Comments »
March 6th, 2008 by Aaron N.
via Ajaxian:
Jan Odvárko “missed two movie nights” to create cookie support in Firebug. His Firebug plugin, Firecookie, gives you access to view, search, create, remove, and manage the permissions of a cookie, all from within a Firebug tab.
Firecookie creates a log entry every time when a cookie is created, changed, deleted or rejected (an option you can change).

Jan is looking for comments.
He has also written a nice tutorial on extending Firebug. It is great to see sub-plugins for Firebug such as YSlow, Firecookie, etc. Do you know of any other good ones?
NOTE: There are, of course, separate Firefox plugins for cookie management.
Posted in Browser Plugins | Comments Off
October 25th, 2007 by Aaron N.
I use Eclipse at home (I run Ubuntu), but I can’t say that this plugin excites me terribly. I use the debugging in firebug for a lot of different things (with our own debugging wrapper: dbug.js) and I don’t know that I want all that stuff diverted into my editor… Still, it’s cool and I’ll probably install it just to see if it’s more useful than firebug on its own. I don’t really get all the mileage out of Eclipse that I could, so maybe this is just another instance of me not getting it entirely. To you Eclipse users out there, what do you think?
Note: the comments on ajaxian imply that this plugin isn’t quite ready for prime time as of this posting.
via ajaxian, via Dean Edwards…
John J. Barton has released a new open source framework named Fireclipse that enables nice coupling of Firefox and Eclipse for debugging purposes, working on top of Firebug.
- Fireclipse routes error messages from Firefox’s
Javascript Console to Eclipse’s console.
- Fireclipse positions an Eclipse editor on the source line reported by Firefox.
- Calls to
dump() end up on the Eclipse console
- Fireclipse adds an Eclipse panel to Firebug
- Extensions to Firebug include:
- debug
eval() code.
- debug event handlers
- route error messages to eclipse
- executable line numbers marked
Take a peak at the page of screenshots to see it setup in Firefox and Eclipse.
( via Dean Edwards )
Posted in Browser Plugins | Comments Off
October 4th, 2007 by Aaron N.
Something that’s long been on my list is to do a write up on firebug. It’s such an indispensable tool that I can’t imagine my day without it. It’s like trying to understand how people did anything before the internet. Anyway, over at Ajaxian there’s a post about one that Phil Rees wrote up. If you don’t use Firebug (and if you’re reading this blog, you probably do), or if you feel like you’re not getting everything out of it, you should dig through this.
Phil Rees has written up a nice introduction to Firebug, showing us how you can use Firebug to:
- Inspect custom stylesheets included by Google Mashup Editor
- Modify in-memory stylesheets to see the changes reflected immediately
- Place watches and breakpoints into running JavaScript
- Execute arbitrary JavaScript in the context of your running application
- Monitor Ajax calls, showing response times, posted content, and results
- Profile JavaScript functions to help you identify bottlenecks and optimize your application.
The article walks through all of these points using Phil’s DanceMaps mashup using the Google Mashup Editor.

Posted in Browser Plugins | 1 Comment »
August 22nd, 2007 by Aaron N.
Today on Ajaxian:
We had a great response for XRAY, the “free cross browser tool that lets you see the box model in action for any element, letting you see beneath the skin of any web page.”
The number one question was “but what about IE???” and now we have the answer. The latest release supports IE6 and above, and “displays information about an element’s borders, and allows you to move around the document with arrow keys. Use the up, down, left and right key to XRAY the currently selected element’s parent, first child, and previous and next siblings.”

Posted in Browser Plugins | Comments Off
August 8th, 2007 by Aaron N.
Here’s a nice little bookmarklet that Mark Bult (of Webshots here at CNET) sent my way: Xray. Here’s what Ajaxian had to say about it when they posted on it last week:
John Allsopp has developed XRAY, a bookmarklet that launches a tool to visualize the web page that you are on (a little like features in Firebug and Firefox). The look and feel is great, and the margin popups look like the new Safari/Webkit search functionality (mmm orange).
What is XRAY
XRAY is the first in hopefully a suite of free cross browser tools for helping web designers and developers better visualize what their code is doing in a browser. XRAY is designed to help you get beneath the skin of your web page.
XRAY let’s you see the box model for any element on a page in action – where is the top and left of an element, how big is each margin, how big is the padding, how wide and high is the content box?
What platforms and browsers is XRAY available on?
XRAY currently has been tested on Safari 2 and 3 on Mac OS X, Webkit nightly builds, and Mozilla based browsers (Firefox, Camino and so on) on Mac OS X and Windows. At present it won’t work on Internet Explorer (XRAY uses the canvas element, but plans are afoot to adapt it for Internet Explorer), and has not been adapted for Opera. We hope to have versions for Opera shortly, and Internet Explorer on Windows in the not too distant future. XRAY works in Safari 3 on Windows, but clicking a bookmark does not fire any Javascript it contains. To use XRAY on Safari 3 for windows at present, you’ll need to paste the XRAY link into the address field and hit return.

Posted in Browser Plugins | Comments Off