Use TweetMeme API instead of JavaScript

sure, I'll look into that when I find some spare time (prolly not gonna be any time soon q.q)

also, in the example I posted I used the serialized php API, which turns out to be pretty much the most unsecure way of doing it

fortunately, they also provide a JSON API, which is pretty secure :D

ok, I finally found a minute to work some on this
attached patch adds a select to the settings, labeled "API" with the options "iFrame" and "JSON"
if JSON is chosen, the theming function calls tweetmeme_get_json and constructs the elements using the data returned, if this call fails, it'll fall back to the iFrame
I'm not sure if tweetmeme_get_json is a good name for the function, as it doesn't rly return JSON, but a php object
I'm also not too sure if this is the best way to go about it, it always feels nasty to go grab data from within a theming function, perhaps we should split it up and go sorta like this:

if API == iFrame -> call theme('tweetmeme_iframe', url, style), done
if API == JSON -> call tweetmeme_get_data(url, json), if that fails, call theme('tweetmeme_iframe', url, style), if it succeeds, call theme('tweetmeme_button', data, url, style), done

also, u'll notice that I did some weird stuff to grab the ID separately coz for some reason they don't return it as a separate value in the object. This is mainly for the next step I was thinking about, which is sort of a mechanism to have up-to-date numbers while having cached pages.
I was thinking of making a behavior that updates the number once everything else on the page is done loading and perhaps optionally have an interval to keep updating it without a pageload
but that's not for right now, I'd rather polish the more static-y method first

I tried to keep the CSS to a minimum while retaining the distinct TweetMeme look (actually used less CSS than they do in their lil iframe, which makes no sense, but w/e)
both normal style and compact only tested in garland
(I linked the background-image to the one on their server as it's prolly not GPL and I don't think I can just recreate it without violating something)

oh, and patch is against HEAD, which seems to be missing some features in comparison to the latest stable...

hehe upsy, forgot to remove my test-url :x

yea, I'm probably not going to be able to do this any time soon, but I'll get on it when I find some spare time