Known problems

Todo:

* 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).

Todo:

* 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.

Todo:

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

Todo:

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

Todo:

* 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?

Todo:

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

Bug:

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

Bug:

* Drop all GtkCTree code

Bug:

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

Todo:

* 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.