KDE Logo
Guidelines
KControl Module Guidelines
Introduction
Design Recommendations
Wording & Phrases
Selecting a Category
Technical Recommendations
Conformance Requirements
Links
KCM Coding HOWTO
KDE UI Guidelines
KConfigXT Tutorial
Makefile.am HOWTO
QT Designer HOWTO
Desktop Entry Specification
KDE User InterfaceStandards

Technical Recommendations

  • Use .ui files instead of handcrafted. User interfaces designed with QT Designer is preferred instead of handwritten ones because 1) It allows people without C++ experience to modify GUIs; 2) It is safer since it is not manually written code; 3) It allows more obtrusive changes to be done in code freezes; and 4) Faster development. It makes life easier for everyone.

  • Use the KConfigXT framework instead of handcrafted configuration code. The rationalis is similar, if not even superior to the above. This is covered in the KConfigXT HOWTO.

  • You must name the KCM's desktop file "kcm_[module name].desktop". For example, if your KCM is called "kmix" the desktop file would be named "kcm_kmix.desktop. All characters must be lowercase.

  • In case the KCM uses KConfigXT, the kcfg file must be called "kcm_[module name].kcfg". For example, if your KCM is called "useraccount" the kcfg file would be called "kcm_useraccount.kcfg". All characters must be lowercase.

  • All files related to the KCM should be positioned in a directory called "kcm", which is a sub directory of the application or code part the KCM belongs to. For example, "kdebase/kicker/kcm".

Previous Next