Kevin Ottens
177be5f6af
I really wonder what I had in mind when I put QStrings everywhere...
Of course SODEP says nothing about encoding so it's really byte arrays that we send/receive. MetaService being higher level I'll assume UTF8 encoding though (it's apparently what it's using. svn path=/branches/work/~ervin/qtjolie/; revision=975435
libplasma Commit Rules: * If your patch is not an obvious or trivial bug fix, have it peer reviewed by another Plasma developer * 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 Unit tests are next to godliness. (Though as you can see, right now libplasma is hellbound.) This directory contains the classes making up libplasma, which provides the core framework used by Plasma applictions, 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, PackageStructure, etc plugins. 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.
Description
Languages
C++
63.9%
QML
29.4%
CMake
3.3%
Shell
1.3%
Python
1%
Other
1%