At 12:19 AM 9/15/01 -0400, you wrote:
We are all acutely aware of the problems the GUI causes when we manually edit configuration files -- httpd.conf, aliases, virtusertable, and the like. It seems to me not very difficult to rewrite the GUI to use the configuration files as base input when editing data, rather than the PostgreSQL database. All the config files are parseable, so deciphering them into HTML forms and later recording the changes as the admin originally laid them out seems feasible.Comments/thoughts?
It is feasible, raq2 did it just like that. There was no database. But I suspect, Cobalt evolved into the database method, as it provided an easier user interface.
-------------------------------------------------------------------------- Ted Behling, Web Application Developer - Monarch Information Systems, Inc. 43 Folly Field Road, Unit 4, Hilton Head Island, SC 29928-5434 E-mail: mailto:TBehling@xxxxxxxxxxxxx Phone/Fax: 1-800-842-7894 Local or Outside the USA: 1-843-842-7894 Cell Phone (urgent issues): 843-816-7895 Cell Phone E-mail: mailto:TedPhone@xxxxxxxxxxxxx (116 letter limit) Web site: http://www.MonarchIS.net -------------------------------------------------------------------------- _______________________________________________ cobalt-developers mailing list cobalt-developers@xxxxxxxxxxxxxxx http://list.cobalt.com/mailman/listinfo/cobalt-developers
Román Sainz Gerente de Tecnología rsainz@xxxxxxxxxxxxxxxxxx http://www.emtechnologies.net