[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC: KConfig changes for 3.0
From:       Marc Mutz <mutz () kde ! org>
Date:       2001-07-25 14:03:47
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 25 July 2001 14:10, Simon Hausmann wrote:
<snip>
> IMHO the right fix is not to enrich the kconfig file but to add a
> proper GUI.
<snip>

Off the topic of this thread, but related:

Often, certain GUI elements in the config dialog correspond directly to 
a certain config key (e.g. QCheckBox <-> bool entry; QLineEdit <-> 
String entry).

How about ready-made ConfigWidgets that can be given KConfig*, group 
and key, and then plugged into the config dialog, getting their label 
from the database of explanations Simon mentioned. On Apply, Cancel, 
Default, the dialog makes sure these widget's states are being 
reflected into the config file.

You won't replace all config dialog GUI elements with this approach, 
but you abstract away all the boring ones, esp. if "group" and "key" 
are designable QProperties, so you can use the QtDesigner :-)

Marc

- -- 
Marc Mutz <Marc@Mutz.com>
http://marc.mutz.com/
http://www.mathematik.uni-bielefeld.de/~mmutz/
http://EncryptionHOWTO.sourceforge.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7XtHD3oWD+L2/6DgRAjecAKDtnndTO/a2Tqisk+V0AdGl1RqbHQCgiYbF
huMEn/Gn3fCyuGoXwm2rzhA=
=UVyW
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]