4 * If your patch is not an obvious or trivial bug fix, have it peer reviewed
5 by another Plasma developer
6 * All code MUST follow the kdelibs coding style, as found at:
7 http://techbase.kde.org/Policies/Kdelibs_Coding_Style
8 * All new public API MUST have apidox written before committing
10 Unit tests are next to godliness. (Though as you can see, right now libplasma
13 This directory contains the classes making up libplasma, which provides the
14 core framework used by Plasma applictions, such as the Plasma desktop shell
15 and its components. This includes applet and extension definitions and loading,
16 common GUI elements, data and service interaction, search system, etc.
18 Domain specific sets of functionality, e.g. for network awareness or sensors,
19 are not found here but as DataEngine, Service, Applet, PackageStructure, etc
22 Please refer to the Plasma website (http://plasma.kde.org) and Plasma wiki
23 (http://techbase.kde.org/Projects/Plasma) for API documentation and design
24 documents regarding this library.