[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, 23 Mar 2003 04:25:14 +0100
User-agent: Mutt/

> gnumed-archive. It is designed as notebook of panels where each page
> represents the options belonging to one particular problem (import/export,
> scan options, backend config etc.).

> It does basic validity checks on the data entered.

> IMHO this concept (single pages for related options,validity checks)
> represents the highest level of convenience to the end user. Eventually we
> should have a config module that has that functionality.

> However, coding every single config item by hand imposes a relatively
> hight cost.
Sebastian is still learning how to program.

> I therefore suggest that we generalize the implementation a little bit,
Yes !

> My suggestions are:
> 1. order all config parameters in some type of hierarchy. This could
> either be implemented by naming conventions (e.g.
> or by passing a group name in addition to the parameter name (this could
> be implemented using the 'cookie' entry in gmCfg)
No. IMHO (or naming conventions).

> 3. handle config parameter definitions and actual config data stored in
> the backend by a higher level (business-object like) config data object.
> This will talk to the backend via gmCfg and provide functions for entry
> validation and parameter grouping.
Good idea.

> 4. as a temporary solution, implement a config-GUI resembling the
> 'regedit' Windows registration editor on top of the config object .
> Reason: quick solution, sufficient for development, allmost the complete
> structure of the gui can be derived from the config parameter definitions.
That is what I hoped for. User level hints on parameters can
be provided in file comments and SQL comment statements.

> 5. as a final step, implement a notebook like config option widget as
> suggested by Sebastians first implementation. This should use the same
> underlying configuration object. All we will have to add is the
> information on how to align the parameters on a notebook page.
This should flow rather naturally from 4 and 3.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]