[Gnumed-devel] notes re ConfigRegistry

[Karsten Hilbert]

Hilmar,

I suggest the following layout:

 ------------------------------------------------------
| config file: <path>                                  |
|------------------------------------------------------|
| option | __input_field__ | description        | tab  |
| option | __input_field__ | description        |------|
| option | __input_field__ | description        |tab | |
| option | __input_field__ | description        |------|
| option | __input_field__ | description        |tab | |
|------------------------------------------------------|
|                                           |  ______  |
| group description                         | | save | |
|                                           |  ------  |
|                                           |  ______  |
|                                           | | load | |
|                                           |  ------  |
 ------------------------------------------------------

The tabs are the groups/sections in the config file/database.
Preloaded is gmCfg.gmDefCfgFile. <load> allows to load another
file. The top line shows the name of the config file or the
connected database. When displaying a tab with a section from the
database your (sub)tree structure instead of the "option,
field, description" triple would be used.

Or something similar. The end user shouldn't notice much of a
difference in handling either the file or the database but the
option source should be shown very clearly.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346