b8343e6cf7
practice, one should NEVER create user interface in ctors/init()s of objects that get created at startup of the app if that UI is not for immediately visibility - fix the build temporarily (but commenting out AppletBrowser bits) until Ivan commits the missing files svn path=/trunk/KDE/kdebase/workspace/libs/plasma/; revision=717926 |
||
|---|---|---|
| appletbrowser | ||
| effects | ||
| includes | ||
| servicetypes | ||
| widgets | ||
| abstractrunner.cpp | ||
| abstractrunner.h | ||
| animator.cpp | ||
| animator.h | ||
| applet.cpp | ||
| applet.h | ||
| CMakeLists.txt | ||
| configxml.cpp | ||
| configxml.h | ||
| containment.cpp | ||
| containment.h | ||
| corona.cpp | ||
| corona.h | ||
| datacontainer_p.h | ||
| datacontainer.cpp | ||
| datacontainer.h | ||
| dataengine.cpp | ||
| dataengine.h | ||
| dataenginemanager.cpp | ||
| dataenginemanager.h | ||
| glapplet.cpp | ||
| glapplet.h | ||
| karambamanager.cpp | ||
| karambamanager.h | ||
| Mainpage.dox | ||
| Messages.sh | ||
| package.cpp | ||
| package.h | ||
| packagemetadata.cpp | ||
| packagemetadata.h | ||
| packages_p.h | ||
| packages.cpp | ||
| packagestructure.cpp | ||
| packagestructure.h | ||
| phase.cpp | ||
| phase.h | ||
| plasma_export.h | ||
| plasma.cpp | ||
| plasma.h | ||
| README | ||
| scriptengine.cpp | ||
| scriptengine.h | ||
| shadowitem_p.h | ||
| shadowitem.cpp | ||
| svg.cpp | ||
| svg.h | ||
| theme.cpp | ||
| theme.h | ||
| uiloader.cpp | ||
| uiloader.h | ||
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 and its components. This includes applet and
extension definitions and loading, common GUI elements, etc.
Domain specific sets of functionality, e.g. for network awareness or sensors,
are not found here but in one of the Plasma Engines.
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.