ROADMAP
-------
Planned features:

 o Write a Web/PHP driver, so that web pages can be driven.
 
 o Allow XML specification to be stored in an SQL specification.
   This not only allows clients to share the same app, but it also
   allows the DWI gui design tool to eb written in DWI.

 o Build a syntax checker that will run seperately from the gui,
   and check things like filter names (which usually don't puke 
	till runtime).

 o Build GUI RAD designer tool.  Construction of tool has started.

 o Simplify chaining of forms.  Provide some defaults forms for
   checking for null fields, etc. (since right now, checking for 
	a null field in an entry is excessivly complicated).

 o Create a scheme-based file format that mirrors the XML design.

TODO List, Bug List
-------------------

 * The order in which signals are delivered can be ambiguous,
   resulting in out-of-order traversals, leading to unexpected results.
	Do something to clarify the order in which signals are submitted.
	(This has the greatest effect when e.g. the database connection
	signal is caught before the database paramters have been set,
	resulting in a failure to connect).

 * The <filter> element needs more work.  The idea is to allow
   filters to be cascaced & custom filters to be created.
   In general, filters allow special data type input & handling, 
   such as printing custom date
   values, or parsing and displaying custom currency strings.

 * add filter to check if a date field contains a valid date!

 * provide multiple simultaneous database support. This is needed 
   for the GUI tool.

 * Provide a cascading chain for reporting errors (in particular,
   errors associated with a failed database conect.  The cascade should
	allow a new user-login form to pop up, or have some other action
	be taken, if the connect to the DB fails.)
	Maybe the best way to do this is to have the DB object issue 
	different signals for each of the failure modes?

 * Provide native postgres drivers so that ODBC is not needed.

 * switch to automake so that odbc driver isn't built, if not present.

 * add GtkList supprt.  make it so "column 0" adds tio list, and "column -1"
   selects items in list.

 * add "column =-1" for selection support to CList, CTree code.

 * make menus and radio-buttons work more like lists (???)

 * Move the sql-builder code (builder.c) into the db-provider directory.
   The idea is to abstract the database interface a bit, allowing non-SQL
	data sources to be used.