Update: I am not yet sure why, but TwitterPane (the tool described in this post) seems to have stopped working for the moment. It might help to know that there is another similar tool out there : TwitterGadget that you can also take a look at. I would suggest that you use TwitterGadget since it is much better featured and is much more likely to be maintained. For figuring out out to write a gadget, welcome and read on.
The need for a twitter feed in gmail.
Lately I have started using twitter quite a bit and find myself going back to check the feed every so frequently (You can find my feed here). The other page I also visit quite regulary is gmail. While I found TweetDeck an exceptionally nice client, it starts up in a different window (thus requiring the customary Alt-Tab to switch and then to switchback) and not in my default workspace (Firefox). I started using TwitterFox extension and every so often I used to look down in the bottom right corner to check if there are any new tweets in the feed. What I wished for was getting the tweets straight onto my gmail page.
Add your own gadget to gmail.
Gmail Labs recently added a new capability to add google gadgets onto the the gmail workspace. I first checked out a few of the existing google gadgets which rolled in the twitter feeds, but soon realised that these were not designed for the narrow workspace one gets on the left hand sidebar in gmail (they were actually designed for the typical igoogle page). So I set out to create my own gadget which would be designed for the left hand sidebar of gmail and which could help serve me the twitter feeds. The real bonus about this would be the fact that I check gmail tab quite often, and I could now check the tweets at the same time.
Types of Gadget
Getting Started: gadgets.* API gets you the introductory start needed for the gadget world. Gadgets are of two types - client side and server side (my words). The client side type uses a host to serve the necessary files for the gadget as a static web server. Thus once the files are loaded onto your browser, the gadget runs on the browser and in turn makes API calls anywhere it needs on the cloud - your host is pretty much out of the way by then. The server side gadgets have some functionality that is running on the host (PHP / Python etc.). The gadget invokes these pages which in turn may make API calls from other services on the cloud. Since the twitter feed basically takes a feed from twitter using its REST API, I just needed to build a client side gadget.
Structure of a Gadget (client side)
1. Basic HTML
Lets first get started with the basic html file. We shall have an HTML file where we shall mark off the area using a
Update : Code removed as stated earlier
2. The document on load function and refresh loop
Please note that HTML / CSS is not exactly stuff I do very often. So good designers are likely to find issues in my HTML code here which they can comment on in the comments for this blog post.
Update : code removed as stated earlier
3. Getting the feed from twitter
The populate() function is where much of the work gets done. We first get the HTML segment identified by the id "messages", clear any existing contents since we shall be refreshing it regulary. The data variable contains a list of json structures which are iterated using the each() function, which splits it up into individual items, and calls the anonymous sub function. This function first identifies the css style based on the message index to separate alternate lines. It also has three regular expression matchers which try to identify twitter users (identified by a word starting with the character '@'), hashtags (identified by a word starting with '#'), and hyperlinks (the typical http/ftp/mailto links), and wrap them with the necessary code to generate the anchor tag around them to be able to make each of them into an hyperlink. Finally it composes the entire HTML code and inserts it into the segment identified by "messages" id using the append function (it actually generates a div tag for each message along the way into which it inserts one message). Since we shall be plugging this gadget into a gmail sidebar, the target of the anchor tag is "_blank" so that the hyperlinks shall open themselves into a new window (or a new tab if your browser is so configured). Moreover because the sidebar is very narrow, and many links are very long without word breaks, I had to replace the link display with a fixed "(Link)" text just so that the resultant content wouldn't scroll off far too into the right.
Sorry .. removed out as per update above
Note that because twitter has a limitation on the number of requests per hour, and because I wasn't sure of how many attempts it would take me to get it right, I first use wget to obtain the output of the REST API call, stored the data in a file, and in the development stages used a link to that static file so that I wouldn't be making calls to twitter every time I was making some minor css / html changes.
4. The gadget descriptor
In this case there was relatively little complexity to describe the gadget using the gadget xml. Here's the xml which is largely self explanatory. The content url refers to the html page which contains the essential gadget functionality
You can pretty much get all the files by following the links from the gadget xml. These are :
In addition one basically needs a jQuery distribution to make it work.
Here's the customary screenshot of how it looks in the end
Should you want to tweak the code, feel free to download and modify the files referred to and self host the gadget elsewhere. But in case you want to check it out as is, in gmail, goto "Settings" select the "Labs" tab and Enable the "Add any gadget by URL" option and press Save. You will now see a new tab called "Gadgets" under "Settings". Go to the "Gadgets" tab and add the gadget by providing its url : http://misc.dhananjaynene.com/gadgets/tweetpane/tweetpane.xml. Thats it and thats all it takes. It will ask you for your twitter id and password to get your feed for you (and for the cautious - the gadget host neither intercepts nor stores your userid/password - thats strictly between you and twitter.)
Afterthoughts:There's probably quite a few things I can still choose to do - clean up the HTML / CSS (some of it may not be quite upto the mark), allow configurable refresh frequencies, allow configurable form factors such as for igoogle etc. But this is fairly functional at this stage and I now can get both my frequently accessed feeds from the same page.
Page 1 / 1