Barış Metin 248e733a1f Move Runner plugins code out of Interface::loadPlugins and into Runner
as indicated in Tasks.

A simple static function does the job IMHO, but if we want something
like a RunnerLoader/Trader class (which can also load a specified
single runner?) I can work on that.

One more question in mind :). Should we make all runners loadable in
runtime?


svn path=/trunk/KDE/kdebase/workspace/plasma/lib/; revision=638445
2007-03-02 00:06:52 +00:00
2006-01-20 11:09:06 +00:00
2007-03-01 08:22:38 +00:00
2007-02-28 23:35:26 +00:00
2007-03-01 00:00:23 +00:00
2007-02-28 23:45:32 +00:00
2006-01-23 11:37:31 +00:00
2006-01-23 11:37:31 +00:00
2006-09-28 10:13:02 +00:00
2007-01-02 19:05:09 +00:00

libplasma

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) for API
documentation and design documents regarding this library.
Description
No description provided
Readme 40 MiB
Languages
C++ 63.9%
QML 29.4%
CMake 3.3%
Shell 1.3%
Python 1%
Other 1%