Difference between revisions of "Control Center Modules (KDE3 Architecture)"
Jump to navigation
Jump to search
(Updated article (class ref link, class names)) |
(-Applicable to TDE (redundant)) |
||
| Line 1: | Line 1: | ||
| − | {{Applicable to TDE}} |
||
| − | |||
| − | |||
The '''Trinity Control Center''' is a modular application. It acts |
The '''Trinity Control Center''' is a modular application. It acts |
||
as a container for "Control Center modules". Modules are implemented |
as a container for "Control Center modules". Modules are implemented |
||
Latest revision as of 15:30, 21 April 2022
The Trinity Control Center is a modular application. It acts as a container for "Control Center modules". Modules are implemented as dynamically loadable libraries.
In order to write a control center module, inherit the class TDECModule from the libtdeui library. This class in turn inherits TQWidget. Basically, you only have to reimplement some methods to load and save the configuration of the items that are configured in your module. In order to notify the control center about a new module, it has to install a .desktop file in the directory applnk/Settings in the TDE directory hierarchy.
Further information is available in the TDECModule class reference.
Initial Author: Bernd Gehrmann