I thought I would share the part of my twitterbrite scripts that uploads videos to Youtube. Its about 30 lines long, and took me an hour or so to write. Most of my time was spent figuring out form fields to fill out rather than writing code though....

I've broken the script down to three parts: logging in, setting the video attributes, and uploading the video file.

Step 1: Logging In

The first step is pretty simple. Just instantiate a new mechanize object, fetch youtube.com, set your login credentials, and submit!

Step 2: Setting video attributes

This is probably the most difficult step. Now that the agent is logged in, we have to fetch the upload page and fill out the video attributes form. You have to set the title, description, category, and keywords for your video. The you have to tell the agent to click a special button.

The number "28" is just the value from the category drop down list. You can iterate over the select options using mechanize, but I leave that as an exercise to the reader.

Step 3: Upload the video file

My script expects that the video file name will be supplied on the command line, so ARGV[0] should point to the file you want to upload. In this step, you simply set the video file name, then submit the form.

The last two lines grab the html needed to display the video and prints it.

There you go. Upload lots of videos now! Yay!

If this doesn't win me the super nerd of the year award, I don't know what will. In fact, this is so nerdy that I'm kind of ashamed to write about it!

Remeber my Twitterbrite post? Well I registered twitterbrite.com, and now if my client catches a twit from you, it records the message on the LED sign and uploads it to my youtube account. Go ahead, check out twitterbrite.com now!

Update: My scripts are too chatty, so now it will only post videos if the text of the twit contains 'betabrite'.

I've just started getting the runtime working with RKelly. Its working well enough at this point that I was able to execute my earlier Fibonacci example. I've added a method to the runtime that allows you to define ruby functions that may be called from inside javascript. For example, the alert function in the following example is defined in ruby and delegates to puts.

Here is the execution time with ruby 1.8.6 on my machine:

Same code, same machine, but with ruby 1.9.0:

I need to get loops working next!

I've been refactoring Mechanize for an 0.7.0 release. Basically I'm trying to clean the code up and there are a few features that I think are unnecessary, but I would like to ask people first.

1. REXML as a parser.

I want to remove support for REXML. I don't use it. Hpricot seems to do everything I need.

2. 1.8.2 thru 1.8.4 support

I've got a bunch of monkey patches for 1.8.2 thru 1.8.4. I'd like to remove these because I think most people are on 1.8.5 or up.

3. WWW::Mechanize::Page#watch_for_set

I am going to remove this method. It made sense when REXML was the main parser, since REXML was so slow. I think that Hpricot is fast enough that this method is not so useful.

I'm going to make 0.7.0 lazily build up form and link objects, which should give everyone a slight speed increase but makes watchforset obsolete (sort of).

I'm changing around the class names to be better organized, but they should all have the same methods. Also, if there are any feature requests, let me know!

The Mechanize library is used for automating interaction with websites.
Mechanize automatically stores and sends cookies, follows redirects,
can follow links, and submit forms. Form fields can be populated and
submitted. Mechanize also keeps track of the sites that you have visited as
a history.

Changes:

Mechanize CHANGELOG

0.6.5

• Copying headers to a hash to prevent memory leaks
• Speeding up page parsing
• Aliased fields to elements
• Adding If-Modified-Since header
• Added delete_field! to form. Thanks to Sava Chankov
• Updated uri escaping to support high order characters. Thanks to Henrik Nyh.
• Better handling relative URIs. Thanks to Henrik Nyh
• Now handles pipes in URLs
  http://rubyforge.org/tracker/?func=detail&aid=7140&group_id=1453&atid=5709
• Now escaping html entities in form fields.
  http://rubyforge.org/tracker/?func=detail&aid=7563&group_id=1453&atid=5709
• Added MSIE 7.0 user agent string

mechanize version 0.6.5 has been released!

http://mechanize.rubyforge.org/

The Mechanize library is used for automating interaction with websites.
Mechanize automatically stores and sends cookies, follows redirects,
can follow links, and submit forms. Form fields can be populated and
submitted. Mechanize also keeps track of the sites that you have visited as
a history.

Changes:

Mechanize CHANGELOG

0.6.5

• Copying headers to a hash to prevent memory leaks
• Speeding up page parsing
• Aliased fields to elements
• Adding If-Modified-Since header
• Added delete_field! to form. Thanks to Sava Chankov
• Updated uri escaping to support high order characters. Thanks to Henrik Nyh.
• Better handling relative URIs. Thanks to Henrik Nyh
• Now handles pipes in URLs
  http://rubyforge.org/tracker/?func=detail&aid=7140&group_id=1453&atid=5709
• Now escaping html entities in form fields.
  http://rubyforge.org/tracker/?func=detail&aid=7563&group_id=1453&atid=5709

• Added MSIE 7.0 user agent string

  http://mechanize.rubyforge.org/

I was debugging Mechanize the other day, and thought it would be handy to have a graph of objects in memory and they're relationship with each other. So I put together a simple script that outputs a Graphviz file illustrating what the object points to. Here's the code:

and the output:

Right now it only supports Arrays, but should be easily extensible to support all other Enumerable types. Here's the code for ObjectGraph:

Update: added Enumerable support, so Hashes are now graphed.

I thought that while I was traveling in Europe I would be able to work on WWW::Mechanize, but then I found out that I can't do anything when I'm travling. Traveling is too much work for me to do anything productive. Luckily I took a day off after my travels, and I was able to complete my work on Mechanize only a couple days late. I think Mechanize is getting more popular, judging from the number of bug submitted. I've fixed more bugs this release than any other. Check out the CHANGELOG for more details on the bug fixes.

As far as new features are concerned, I've added a submit method to forms. Before, you had to call submit on the mechanize object and pass in the form like this:

Now you can just call the submit method on the form like this:

Along the same line, I've added a click method to links. Instead of passing a link to the agent object, you can just call the click method on the link like so:

I wonder when people will figure out where the release names come from. Nobody has said anything about them to me..... So far I have:

• Twan
• Sylvester
• Rufus
• Chuck

I've been working pretty hard on merging Mechanize with Hpricot in to what I call Mechpricot, or Hprichanize. Things are going quite well.

I've totally cleaned up the Cookie code to use more cookie code from WEBrick, and in the process I found a bug in the way that WEBrick parses set-cookie headers. Unfortunately no one has replied to my patch on ruby-talk, so I think I'll try ruby-core next.....

I removed the dependency on mime-types in favor of using code in WEBrick. I'd like to have as few dependencies as possible. I would like to make a few more performance tweaks before I release. I'll see if I can get this completely done before this weekend. Otherwise everyone will have to wait until I'm back from Spain!

I was able to write a pretty quick mechanize script that grabbed the playlist from kexp and put it in a SQLite database. From that, I came up with the top 4 songs played on KEXP for July:

1. Tv On The Radio - Playhouses
2. Midlake - Roscoe
3. Johnny Cash - Gods Gonna Cut You Down
4. Silversun Pickups - Lazy Eye

I also used Gruff Graphs to make a graph: