atom thoughts

I just ran across this great visual diagram of the prototype javascript library:

http://www.snook.ca/archives/prototype.png

It was put together by Jonathan Snook and is a great cheat sheet if you are working with the prototype library.

There are a ton of great plugins for Firefox that make Web development a whole lot better. I really don’t know how I managed without them.

My most recent addition is called FireBug, which provides a number of great features including:

• Javascript and CSS error notification.
• Inspection tools for HTML, the DOM, CSS and events.
• A Javascript command line.
• XmlHttpRequest spying (which is great for AJAX debugging).

Some of my other favorite Firefox web development extensions include:

• Web Developer – This should be in every web developer’s tool box. It provides a ton of different utilities for doing things such as disabling cookies and javascript, informational tools such as highlighting elements within your page, tools for validating your HTML and CSS, and way too much more to list.

• DevBoi – A one stop shop for all of your reference documentation needs. It includes the docs for HTML, CSS, DOM, Javascript and also has add on packs for Ruby On Rails, PHP and XUL. Be sure to install the offline version if you want to be able to access these without internet access.

• IETab – This is a great tool for viewing your page in IE from within Firefox. It will open the page in a new tab that is rendered using the IE engine. Pretty slick.

If you have any that you think I missed, I would love to hear about them.

I just recently ran across another nice thing you can do with Ruby on Rails that I thought others may find useful. I have developed a few different Rails apps and in several cases, I have found that I really needed a way to perform some process in the background outside of the web server. This could serve a variety of purposes, such as for slicing and dicing your data into reports or performing some resource intensive tasks.

Ruby On Rails provides a simple way to take advantage of your existing Rails code from the command line. For this example, let’s say we want to create a script called do_something_magical. So, we can just create a file in the scripts directory of our Rails app and call it do_something_magical.rb. Then, at the top of this script, just add this one line to make your script run within the Ruby On Rails environment:

require File.join(File.dirname(__FILE__), '../config/environment')

Now this script will be able to access all of your other Rails code. For instance, to include your secret_ingredients model, you can just require it like so:

require 'secret_ingredients'

Likewise, if you have a magic_maker dependency in your lib directory you can include it as follows:

require_dependency 'magic_maker'

I found this to be a great time saver when I need to do some heavy lifting with my existing Ruby On Rails code.

So, I noticed I was receiving a random error from the Gift Hat by one of my ajax auto complete forms.

An ajax submit was occurring without any data, which is impossible from within a browser since a user has to enter data for the ajax form to submit.

Here is the Ajax code in question:

new Ajax.Autocompleter('find_hat', 'find_hat_auto_complete', '/hat/auto_complete_for_find_hat', {indicator:'indicator'})

Thanks to my Exception Notifier setup, I was receiving very detailed emails when the error occurred including this interesting tidbit:

HTTP_FROM : googlebot(at)googlebot.com

It turns out, the googlebot traverses your Ajax code, so beware of the Googlebot or any other random non-human agents. They may be doing things that would otherwise be impossible so plan for these cases as well when building your web apps.

After publishing the Gift Hat Tour, some of the initial feedback I received was that the tour was a bit too long. Looking through the stats for the tour, I could see that a majority of the people never made it to the end. So, I searched for a more elegant solution for presenting the tour content.

My first tour implementation consisted of 8 pages, and that not all of the features of the Gift Hat that I intend to put into the tour. Each page linked to one another through a series of Next and Previous links. So, there was a very linear path through the tour.

After searching around for some alternative inspiration, I ended up completely rewriting the tour navigation to include links to the individual tour pages like so:

I think the end result is a major improvement to the tour with just a simple navigation change. Now, instead of a linear path through the tour, people can choose their own path and exit whenever they like. It also gives me plenty of room to add some of those additional features into the tour as the Gift Hat grows.