KDE 4: systemsettings and general configuration

kde-logo-official
Besides other things the current KDE 4 development snapshots are lacking a working configuration utility. Now a branch was created to port the old systemsettings over to KDE 4.

The new branch was announced in the newest commit-digest, issue 58. It is about time because this is one of the fields where KDE 4 has nothing to offer yet – others are the kicker, menu and kdesktop replacements, btw.
However, besides the initial creation of the branch nothing else has happened there yet – but that might be due to local work not submitted to the SVN yet.

Speaking about system settings and configuration, I wonder what happened to the initial thoughts about new configuration backends for KDE 4. The idea was to have a new kconfig system which could use different backends. One proposal was to have a ldb backend to

get a centralizable, replicatable, scalable, fast and safe config storage system that can move us beyond ini-style configs without much work on our part

Another proposal was for a new type of XML based configuration files, kconfig XT. I never heard anything about that again in the last months.

Looks like we will go with the pure text files – again.

7 thoughts on “KDE 4: systemsettings and general configuration”

  1. In your post it sounds (at least for me) like graphical configuration isn’t posslible in KDE4 at the moment. However, this is possible by using “kcmshell /module/”. A list of possible modules can be seen by “kcmshell –list”.

  2. ah well. I built kde from SVN last night just to give it a try. It looked quite nice and dolphin as well as oxygen are great new features. But I really missed the configuration frontend (of course this didn’t come surprising since it’s only post-alpha1 now).

    Well, thank you for the information🙂

  3. Nice link, thank you.
    Btw, I tried out `kcmshell –list` and it only brought some error about not finding the module ‘-list’ or somewhat. Launching some of the modules I knew worked, though.

  4. “Looks like we will go with the pure text files – again.”

    Yes, and let’s hope it stays that way.

    It’s human-readable by anyone, and no harder to parse for config tools than (for instance) XML. Better for the user.

  5. XML files are also human readable – and when the XML file is structured in a sane way it can even improve the readability.

    Besides, I never met users who want to read config files. I met power users and technique interested people who wanted to do (like me), but never average computer users.
    And for the group of people who want to read and do stuff with the config files XML seems the much better choice!

Comments are closed.