Title: Google Enhanced Todo List 

Authors: John Russell. The original idea was that of Paul Russell who
is also in this class. He will not be participating in the
implementation but will happily use the module once completed.

Abstract: 
The personalized google homepage allows for the creation of custom
modules which utilize its web services api for a variety of purposes.
There are many TODO lists with similar limitations.  I intend to
overcome some of these limitations using a combination of XML as a
storage medium a javascript xml parser, and the google web services
API.


What:
The main limitation of all of the existing task list modules for
google is the issue of storage.  The trade off that must be made is to
either find another place to store your task data external to the
google module itself or to manage to deal with the limitations put
forth by the google module environment.  See, the How section.  The
goal is to implement a feature rich task list with a wide array of
common features such as % complete, due dates, labels and task
notes. All within the confines of a single google module with the use
of the google web services api. 

Why:
I want this.  So does my brother Paul.  Isn't that enough?  There are
many half way modules for this existing today, but they are all
extremely simple and limited.  The ones that aren't require external
resources of questionable availability and durability.  

How: 
What the google api allows is the storage of an seemingly
unlimited number of discrete named parameters of limited size ( ~1500
characters ).  While this limit may not come in to play on some tasks,
when directions, notes, dates, meta-data such as due-date, % complete,
which are considered necessary for a truly useful task list
implementation 1500 characters, even if it wasn't XML, would get
chewed up very quickly.  I intend to write javascript which will
serialize and de-serialize the storage xml into these parameters
handling any concatenation across parameters that may be necessary to
store as much data as required by a given task. I will be using a
javascript xml parser to handle the XML and to interface with the
google web services api.

Questions:
No questions yet.  Probably will have some later.