[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: |
Mon, 3 Mar 2003 11:50:27 +0100 |
User-agent: |
Mutt/1.3.22.1i |
> I agree, it is cleaner to store everything as a string on one table.
We already have 3 types available: string, numeric, string
array (list). But those can be deduced automatically via
Python's introspection features.
> All we need is a description and a type (only 4 types: number, string,
> colour and font) on the table.
One might use the group field of cfg_template to indicate
color/font on some rows.
> These parameters could be on the gmCfg.set () function (optional
> parameters, the default type is string, so it doesn't break existing
> code).
Quite a nice idea. I'll put it in the TODO.
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