I've finally taken the Ruby plunge. It's taken a while. My buddyChris Grindstaff recommended I look at it years ago. I had heard of it, and it sounded interesting, but coming from Chris, I took a closer look. Started following it from afar. Eventually boughtthe book. Still didn't really do anything.
Finally, as I have been posting flickr pix in my blog entries,and copy/pasting the html into new entries, it was time to automate, and thus getf4b was born. Simple command line program,and thus easy to integrate intoTextMate and Eclipse.
(Quick aside: I edit all my blog posts in .html files usingTextMate, then paste into roller when I'm all done.)
So, Ruby. I'm an old smalltalker, so I don't need muchconvincing on the gorgeousness of the language. I am a little suprised there's not much interest from theold OTI crowd in Ruby. They'll come around.
The little program I wrote uses a Ruby gem named 'flickr' to do all the flickrAPI work, but there are some issues. Check the code and you'llsee how I had to hack the photo URLs a bit. I needed to figureout how to get program arguments, the name and location ofthe program being invoked, some basic string parsing, and howto do 'here doc'. Everything else was pretty natural.
Actually, the hardest thing was figuring out to 'require' a gem. Ithelps to require 'rubygems' first, and then use require_geminstead of require for a gem. The doc didn't really make thatclear.
More later, I'm sure.