Difference between revisions of "Development/Architecture/KDE3/Panel Applets"

Jump to: navigation, search
 
Line 25: Line 25:
 
Further information is available in the
 
Further information is available in the
 
[http://api.kde.org/3.5-api/kdelibs-apidocs/kdeui/html/classKPanelApplet.html KPanelApplet]
 
[http://api.kde.org/3.5-api/kdelibs-apidocs/kdeui/html/classKPanelApplet.html KPanelApplet]
documentation. A
+
documentation.
[[Development/Tutorials/KDE3/Extending the KDE Panel|tutorial]]
+
is also available.
+
  
  

Latest revision as of 21:15, 11 July 2007

KDE Architecture - Applets

[edit] Panel Applets

KDE's panel (also known as kicker) allows small programs, called "applets", to be embedded. Currently, for example the clock and the pager are implemented as applets.

Applets can run either in the internally (i.e. in the panel's process space) or externally (i.e. as separate processes). The advantage of the first method is that the memory overhead is not higher than really necessary. On the other hand, an unstable applet can crash the whole panel. This can not happen with an external applet which communicates with the panel via a DCOP connection.

From the programmer's point of view, the difference between internal and external applets is transparent. He implements an applet as a dynamically loadable library and inherits from the KPanelApplet class in the libkdeui library. In order to notify the panel about a new applet, it has to install a .desktop file in the directory share/apps/kicker/applet in the KDE directory hierarchy.

Further information is available in the KPanelApplet documentation.


Initial Author: Bernd Gehrmann


This page was last modified on 11 July 2007, at 21:15. This page has been accessed 4,025 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal