I started (as many CFers do) by discovering Twitter4J but immediately discovered two important things:
- I'm a CF developer and not a Java developer
- I have this fetish wherein I like things to work...or at least be properly documented in case they don't.
In either event, this meant that Twitter4J just wasn't for me. From having to have access to the web server for the site to drop in a .jar file to realizing most of the way through my project that the sparse documentation I was in possession of was stale by a factor of two full point releases and that object methods the examples used no longer existed...I was pretty much launched on a quest to find some other way to navigate the maddening complexity that is Twitter's OAuth powered API.
Monday, I discovered the alternative for ColdFusion devs who want to integrate Twitter into their projects. It's called monkehTweets and is merely a collection of .cfc files that is easily dropped into most sites and works pretty damned easily thereafter. Much easier to use than Twitter4J, monkehTweets is one of those things you actually have a chance of fixing on your own should it not work according to plan. It even comes with one of the easiest video tutorials I've ever seen as well as a nice .zip file of CF code so if you're as lazy and/or discouraged as I got from trying to understand why Satan wrote OAuth in the first place (the only plausible explanation to my mind), you can simply look at what Matt Gifford (monkehTweet's author) has done and blatantly use that as a template to forge your own sweet, sweet success with Twitter's API.
As the discerning reader might pick up on, I'm somewhat delirious with relief that I can finally move past most of my site's Twitter integration issues and move on to other pressing items...like Facebook integration. Anyway, my current mood means I feel like sharing the good (and unfortunately hard-to-find) news with the rest of the CF community.

New Topic/Question
Reply




MultiQuote




|