TODO / Design Document - For dicussion

[mike_phillips urscorp com]

After reading the design document in the source fully, there are a lot of 
good idea in the document. 

For future development perhaps we should compile a list of features to be 
added. 

I thought of the following:

Main Functionality - 
        Extending the current code with a gui. 
        Producing kneeboard format output
        Adding support for DAFIF files. 
        Other stuff covering in general todo section. 

New Functionality - 
        In flight capabilities (on linux based pda's and/or otherwise)
        Airport directory, facilities information
        Weather downloads
        E6B functions
        DUATS (maybe ;)

It would be nice to set the code up to be modular in nature, allowing new 
modules to be added without a major rewrite of the underlying code. This 
will also allow us to keep a cli if desired. 

I would even go so far as to suggest a modular database system as well 
allowing people to use whichever database they want. Default would be the 
existing setup with modules for other db's (Berkeley DB, MySQL, 
PostgresSQL, etc.) I've already hacked together some routines to convert 
the DAFIF airport files into a Postgressql table. 

This is John's project, so ultimately his decision as well, but if we can 
agree on a framework for modularizing the code each of us can work on a 
different part without stepping on each other's toes. 

Personaly, my area of expertise is in low level coding, network stuff and 
databases.

Mike