Twitter API, Jquery, AJAX, javascript, html, css, YUI grids and 1 widget

For the last week or so I have been busy working on an individual project to create a twitter widget that displays a twitter list in the classic twitter scrolling style. This project was given to me as more of a self development project rather than having any end game, which is really good and I have learnt a lot. The title of this blog kind of outlines basically what the project has required, and in typical development fashion the scope creep has been pretty lengthy.  Along the way I've had a couple of other small flash pieces to work on but this has been the main focus of my time.  The project has gone through many various stages over the past week and a half and now consists of both a working scrolling interactive twitter widget, and a generator webpage to provide the twitter widget to other users open source, probably eventually under a creative commons license.  The twitter API probably saved me on this one, making it really easy to get twitter data which I could then manipulate.  Im glad there was no OAuth issues either as this would have been particularly tricky to deal with.  It was really good to properly get to grips with some of the main jquery functions as it is a very powerful javascript addon, and the more comfortable I am with it the better.  Most of the javascript I worte was standard javascript though which is great as it means I have gathered more understanding about something that I can use to improve my personal work in the future.  In doing this project I have also been able to develop some design skills as I have produced all of the assets for the twitter widget creation pages.  This was only small but it has shown to me that my understanding of how web design works has already improved from the work I have been doing on my placement. I have now uploaded the twitter page to my webspace so that it can be used but am having a few compatibility issues between browsers (no surprise). From doing this I have learnt that I should probably work more in stages rather than one go.  If I had tested my application on all browsers throughout the project any main problems that occurred I could fix as I went along rather than having to try and work it out afterwards when there is a lot of code to look through.