CiaN:MinDMaP the experience of reading those pages altered my anatomy

#Winnipeg GPS Bus Shedule Update

I have now completed learning all of the Android functionality that is required to make the GPS Bus Schedule "Go". These include:

• Interacting with the OS, learning what an Activity, and Service are
• Interacting with the GPS/Network location provider, learning how to 'smooth' the data feed from it
• Interacting with the Google API, used to identify Locality, and Long / Lat
• Interacting with the outside world directly, eg. Winnipeg Transit's API

In order to make this project able to work with many other Transit API's, I'm designing it to be modular, selecting the appropriate module based on the currently detected city. What this means is that I need to build a model that will standardize the flow of information between the presentation layer (UI) and the data access layer (API).

It will work something like this

Currently I'm working on the Model portion, I'm looking at various Transit API's and finding the most common data objects and attributes. Out of those I'm selecting the ones that I believe will be relevant to this project. Once I am complete, I can use this model as a common 'intermediary' to ensure that changes to the transit API's don't require User Interface changes, which should make this project much easier to maintain.

In case you're interested, I'm currently working in Eclipse 3.5, with Visual Paradigm as my modeling tool. The nice thing about this combination is the model-code-model loop is all integrated between the two, meaning changes in either my code or model are synced without data loss. Once I'm further along, I will post more, thanks for listening!

A snapshot of my development environment