Resedit (Was: Proposal for KControl)

[Oswald Buddenhagen]

On Sun, Jun 30, 2002 at 10:19:28AM +0200, Cornelius Schumacher wrote:
> Couldn't we do it the other way around and generate the code that reads 
> and writes the config entries from the XML file?
>
i very much like this one. and it's exactly the same idea i had this
morning for kdm - although i didn't plan to use xml. :)

> Then we have only one place where the config options are specified and
> automatically get a nice C++ class for the configuration which is
> convenient to use in an application.
>
a config container. kdm already has such a thing. :-)
the only situation i can think of where this does not work are
configurations that dynamically create new entries/groups depending on
prior settings (think of lists and even flattened trees). we could put
support for some basic complex (yeah, that's a condradiction :)
structures into the container, but this would never cover all use cases
- but then, this is not tragic: wildcards could be used for groups &
keys and the code to create the structure would be hand written as ever.

> We could even try to automatically generate code for the configuration
> dialogs, at least for some standard types.
>
this is a nice idea for the "konfedit" (oh, well, the current name
is "resedit" :). in the "normal" kcontrol this would lead to a usability 
disaster, unless it is only used create the "contents" of the config
widgets, while their placing, etc. is still done in an ui file.

> This could significantly improve consitency across different apps.
> 
and it would simplify development and prevent bugs. in theory ... :)

greetings

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.