[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Gnumed config editor
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Gnumed config editor |
Date: |
Sun, 2 Mar 2003 23:18:46 +0100 |
User-agent: |
Mutt/1.3.22.1i |
> See gmclient_config.sql in CVS. These tables store metadata (config
> type, name, description) which can be used to form config widgets on the
> fly. It nees more work (and integrating which Karsten's config tables
> of course)
I did not do that integration myself since
a) I could not conceive of a way to handle the
gmclient_config.sql tables generically
b) the way gmclient_config handles tables might lead to an
arbitrary explosion of config item types
c) all of the data can be handled by the 'generic' tables in
gmconfiguration.sql
However, I do ack that one looses some possibilities when
storing, say, font information in a generic string rather than
in a cfg_font_info table.
If anyone can think of a sensible, tasteful way of how to marry
the get()/set() genericity of gmCfg.py with the data type
specifity of gmclient_config.sql I'd be most happy.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- [Gnumed-devel] Gnumed config editor, Hilmar Berger, 2003/03/02
- Re: [Gnumed-devel] Gnumed config editor, Karsten Hilbert, 2003/03/03
- Re: [Gnumed-devel] Gnumed config editor, Karsten Hilbert, 2003/03/03
- Re: [Gnumed-devel] Gnumed config editor, Karsten Hilbert, 2003/03/22
- Re: [Gnumed-devel] Gnumed config editor, Karsten Hilbert, 2003/03/22