Some changes to my approach:
- I think I’m going to use the twitter gem, rather than twitter4r. The only reason; it just seems a bit simpler. I may change my mind again. Or you may change your mind.
- Alternatively, I may just use Net::HTTP — the twitter api seems straight forward, and this would eliminate a dependency.
- I don’t think this will be a mass consumption tool at any time in the near future. It simply won’t be a 1 or 2 click install, like an AIR application. And really, that’s ok; maybe a Shoes application is supposed to require you to roll up your sleeves and muck about a little bit. Get your hands dirty. Open a command line. Edit a file or two.
So, basically, then, all the shoe has to do is get or post messages to twitter. It will also need to parse XML or JSON, so I suppose I’ll be looking for a gem to make that easier, as well. I’m a big fan of Not Reinventing The Wheel. Stay tuned, padwan.
