plasma-framework

Go to file

David Faure c533ee9e32 Another unit test breakage CCMAIL: r.scheepmaker@student.utwente.nl svn path=/trunk/KDE/kdelibs/; revision=1023883		2009-09-15 13:08:07 +00:00
data
extenders
private
remote
scripting
tests
widgets
.krazy
abstractrunner.cpp
abstractrunner.h
animationdriver.cpp
animationdriver.h
animator.cpp
animator.h
applet.cpp
applet.h
CMakeLists.txt
config-plasma.h.cmake
configloader.cpp
configloader.h
containment.cpp
containment.h
containmentactions.cpp
containmentactions.h
context.cpp
context.h
corona.cpp
corona.h
datacontainer.cpp
datacontainer.h
dataengine.cpp
dataengine.h
dataenginemanager.cpp
dataenginemanager.h
delegate.cpp
delegate.h
dialog.cpp
dialog.h
framesvg.cpp
framesvg.h
glapplet.cpp
glapplet.h
kcm_remotewidgets.actions
Mainpage.dox
Messages.sh
package.cpp
package.h
packagemetadata.cpp
packagemetadata.h
packagestructure.cpp
packagestructure.h
paintutils.cpp
paintutils.h
plasma_export.h
plasma.cpp
plasma.h
plasma.kdev4
popupapplet.cpp
popupapplet.h
querymatch.cpp
querymatch.h
README
runnercontext.cpp
runnercontext.h
runnermanager.cpp
runnermanager.h
runnersyntax.cpp
runnersyntax.h
service.cpp
service.h
servicejob.cpp
servicejob.h
svg.cpp
svg.h
theme.cpp
theme.h
tooltipcontent.cpp
tooltipcontent.h
tooltipmanager.cpp
tooltipmanager.h
version.cpp
version.h
view.cpp
view.h
wallpaper.cpp
wallpaper.h
windoweffects.cpp
windoweffects.h

README

libplasma

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.

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.