You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
David Faure 6bb0a14db4 Revert "Store app config file in ~/.config/<domain>/<app>rc" 12 years ago
autotests Adapt to changes in KDEInstallDirs 12 years ago
docs Rewrite kiosk documentation 12 years ago
src Revert "Store app config file in ~/.config/<domain>/<app>rc" 12 years ago
.reviewboardrc Add myself to the target people to receive all review requests. 12 years ago
CMakeLists.txt Compile translations (in tags and tarballs) 12 years ago
COPYING.LIB Move kconfig code to the root directory. 12 years ago
DESIGN Move kconfig code to the root directory. 12 years ago
KF5ConfigConfig.cmake.in Remove references to ${_KDE4_KCONFIG_COMPILER_DEP} 12 years ago
KF5ConfigMacros.cmake Rename the kconfig_compiler_kf5 target to kconfig_compiler 12 years ago
README.md Rewrite kiosk documentation 12 years ago
TODO Move kconfig code to the root directory. 12 years ago
metainfo.yaml Add framework information in metainfo.yaml files 12 years ago

README.md

KConfig

Backend for storing application configuration

Introduction

KConfig provides an advanced configuration system. It is made of two parts: KConfigCore and KConfigGui.

KConfigCore provides access to the configuration files themselves. It features:

  • Code generation: describe your configuration in an XML file, and use `kconfig_compiler to generate classes that read and write configuration entries.
  • Cascading configuration files (global settings overridden by local settings).
  • Optional shell expansion support (see [docs/options.md](@ref options)).
  • The ability to lock down configuration options (see [docs/options.md](@ref options)).

KConfigGui provides a way to hook widgets to the configuration so that they are automatically initialized from the configuration and automatically propagate their changes to their respective configuration files.