Wednesday, January 28, 2009

Transits and the homepage (20090128)

Making the decision on how to handle transits - it seems the best option is to fetch transits on a daily basis, using a cronjob, using the retrieveTransits2 API, which returns the most important transits for the current 3 days (centered around today.) The only issue with this is that it currently uses the local time (and zone) to determine when days start and end. Kinda implies that we should be storing the user's timezone when they log in/register. For starters we can use
GMT.

Created the Transit mini-ORM class.

Extracting the transits from retrieveData2 is done. This isn't the nice clean and localised (from a time point of view) set of transits as above - but it'll do for the moment whilst we get the transit
display up and running.

Basic display of overlapping transits (starting before now, and ending after now) done. Doesn't look very pretty.

I've got a homepage up and running, display 3 tabs (Welcome, Images, Transits), with a little Ajax and other javascript to display the relevant content.

No comments: