Difference between revisions of "Panel Applets (KDE3 Architecture)"
m (→Panel Applets: Minor updates and improvements, updated apidoc link) |
m (Minor changes) |
||
| Line 1: | Line 1: | ||
| ⚫ | |||
| ⚫ | |||
| + | '''applets''', to be embedded into it. The clock and the pager are both examples of |
||
| ⚫ | |||
| + | Kicker applets. |
||
| ⚫ | |||
| − | {{Applicable to TDE}} |
||
| − | |||
| − | == Panel Applets == |
||
| − | |||
| ⚫ | |||
| − | ''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 |
Applets can run either in the internally (i.e. in the panel's process |
||
| Line 31: | Line 24: | ||
''Initial Author:'' [mailto:bernd@kdevelop.org Bernd Gehrmann] |
''Initial Author:'' [mailto:bernd@kdevelop.org Bernd Gehrmann] |
||
| + | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
Latest revision as of 16:26, 21 April 2022
Kicker (the Trinity panel)allows small programs, called applets, to be embedded into it. The clock and the pager are both examples of Kicker 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 libtdeui 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 TDE directory hierarchy.
Further information is available in the KPanelApplet documentation.
Initial Author: Bernd Gehrmann