Sebastian Kügler c76b5137e2 Fix empty group operations
There appears to be a subtle change in KConfig*, which means that if a
config group is empty, it won't be listed in groupsMap. Since operations
files can have empty groups, which are simply calls without arguments,
these would not be listed, and thus not be callable at all.

Fix: Add a dummy item per group, not beautiful, but effectively makes it
work.
2013-08-14 03:29:46 +02:00
..
2013-02-14 17:17:12 +01:00
2013-03-13 12:05:06 +01:00
2013-07-30 08:05:09 +02:00
2013-07-30 08:05:09 +02:00
2013-08-09 05:22:20 +02:00
2013-02-14 17:17:12 +01:00
2013-02-14 17:17:12 +01:00
2013-08-14 03:29:46 +02:00
2013-06-27 18:36:20 +02:00
2013-07-30 08:05:09 +02:00
2013-07-30 08:05:09 +02:00
2013-07-30 08:05:09 +02:00
2013-05-14 20:27:32 +02:00
2013-08-06 15:06:07 +02:00
2013-02-14 17:17:12 +01:00
2013-07-30 08:05:09 +02:00
2013-05-14 20:37:16 +02:00
2013-02-14 17:17:12 +01:00
2013-07-30 08:05:09 +02:00
2013-02-14 17:17:12 +01:00
2013-07-30 08:05:09 +02:00
2013-07-10 00:12:26 +02:00
2013-07-30 08:05:09 +02:00
2013-02-14 17:17:12 +01:00
2013-07-30 08:05:09 +02:00
2013-02-14 17:17:12 +01:00
2013-07-30 08:05:09 +02:00
2013-02-14 17:17:12 +01:00
2013-02-14 17:17:12 +01:00
2013-07-30 08:05:09 +02:00
2013-07-30 08:05:09 +02:00
2013-07-30 08:05:09 +02:00
2013-02-14 17:17:12 +01:00
2013-07-30 08:05:09 +02:00
2013-03-13 11:32:00 +01:00
2013-02-14 17:17:12 +01:00

libplasma

This directory contains the classes making up libplasma, which provides the
core framework used by Plasma applications, such as the Plasma desktop shell
and its components. This includes applet and extension definitions and loading,
common GUI elements, data and service interaction, search system, etc.

Domain specific sets of functionality, e.g. for network awareness or sensors,
are not found here but as DataEngine, Service, Applet, Package, Wallpaper,
ContainmentActions, Containment and other plugins.

Commit Guidelines:
* If your patch is not an obvious or trivial bug fix, have it peer reviewed
  by another Plasma developer; http://reviewboard.kde.org is your friend :)

* All code MUST follow the kdelibs coding style, as found at:
        http://techbase.kde.org/Policies/Kdelibs_Coding_Style

* All new public API MUST have apidox written before committing and must go
  through an API review with another Plasma developer. We have to maintain
  binary compatibility, remember!

Unit tests are next to godliness. (Though as you can see, right now libplasma
is hellbound.)

Please refer to the Plasma website (http://plasma.kde.org) and Plasma wiki
(http://techbase.kde.org/Projects/Plasma) for API documentation and design
documents regarding this library.