Hello,

Please give some input on the following idea. For KConfig in 3.0 I would
like to see the following changes:

- allow "default" as readable value even for boolean entries etcetera,
- add a "requirement" or good-practice recommendation that applications
  always save all possible entries in the config file, even those that are
  default
- add a description QString to each key and group

That way, users can be assured there are no "hidden" options in the code
ever. Every configurable option will be in the configuration file.

My concerns regarding this come forth from the removal of "Fade out applet
handles" from kcmkicker. Since it has no GUI entry and is not present in the
default saved configuration file, there is no way to know whether the option
exists but to be familiar with the code.

Proposed changes would also make it fairly easy to add "Advanced options.."
buttons to KControl as that could be a small program reading all the
entries, defaults and descriptions. Launching Kate with the appropriate rc
file and a special highlight mode would probably suffice.

Another option would be to switch to XML based configuration files, which
allows us to store possible values in a DTD and have a generic "RC Editor"
(or a Kate plugin) for advanced features. Such a config file editor would
probably be the best option to keep KControl simple yet allow power users to
tweak all advanced features of a program.

Comments? Cheers? Curses?

Rob
-- 
Rob Kaper     | 'Linux was released on August 25th, 1991. Therefore it is a
cap@capsi.com | virgo, not a cancer.'
www.capsi.com |         -- Kevin Lyda