Perhaps it might makes things more complicated than what it's worth but having the _option_ of 3 variations could be neat. 1) a static system much as it is now with perhaps a little thought to make it as simple as possible, 2) a super flexible dynamic system as outlined above by Mike or, 3) a default SQLite db/table with all of the normal config parameters as records. If in config mode 3 then the first thing the TG app does when starting up is a single query that pulls in all config info that would normally have been supplied by the current static config system. Catwalk basically enables the ability for the user to provide application config changes via the web so this 3rd option of not even having ANY config files at all would be super-slick.
The catch 22 of a config option to determine which config mode to use could be simply solved by auto detecting whether or not certain files exist... something like, if config.ini exists then use static config mode 1, if config.py exists then use dynamic config mode 2, if config.sqlite exists then kick into config mode 3. A 4th option to write out a config.ini AFTER starting up in mode 3 and making changes could also be considered, so that there is no database hit involved and we end up back at in mode 1 via mode 3, with a database enhanced static config system. --markc
