| 1 |
HOWTO Make KDED Modules |
| 2 |
======================= |
| 3 |
|
| 4 |
A KDED module is loaded when a call is made to it. |
| 5 |
KDED modules should not be added if it is avoidable because (especially |
| 6 |
when new) they endanger the stability of KDED and its other modules which |
| 7 |
provide important services. There are other ways to achieve what a KDED |
| 8 |
module can do in many cases. |
| 9 |
KDED modules should be useful during the whole session and manage |
| 10 |
information that, for some reason, cannot be kept in any other process. |
| 11 |
|
| 12 |
Here are examples of KDED modules: |
| 13 |
frameworks/baloo/src/kioslaves/kded/baloosearchmodule.cpp Baloo search module |
| 14 |
kde/workspace/khotkeys/app/kded.cpp KHotKeys |
| 15 |
|
| 16 |
A KDED module should install a .desktop file with |
| 17 |
ServicesTypes=KDEDModule |
| 18 |
|
| 19 |
A KDED module will be loaded on KDE startup if it has a line |
| 20 |
X-KDE-Kded-autoload=true |
| 21 |
|
| 22 |
Note that this flag doesn't cause the module to be loaded if the KDE desktop |
| 23 |
is not running (i.e. when running a KDE application in another environment). |
| 24 |
|
| 25 |
Normally KDED modules are loaded whenever they are accessed, so you don't |
| 26 |
need autoloading enabled. On demand loading can be disabled by putting |
| 27 |
the following line in the .desktop file: |
| 28 |
X-KDE-Kded-load-on-demand=false |
| 29 |
|
| 30 |
Further it should contain: |
| 31 |
X-KDE-Library=foo |
| 32 |
|
| 33 |
Which means that kded_foo.so is the name of the library that contains |
| 34 |
the module. Note that the name of the library always starts with kded_. |
| 35 |
|
| 36 |
The .desktop file should be installed to ${SERVICES_INSTALL_DIR}/kded |