The KDevelop C++ KDE templates: others

KControl module

Screenshot

Automake based. Generates a framework for a module which can be embedded into the KDE Control Center. When you make install, it installs the file in $KDEDIR/lib/kde3 and you must (re)start KControl to find the application there, in KDE Components per default. You can set a new location in the .desktop file. Nothing appears on execute.

Tutorial: http://developer.kde.org/documentation/other/kcm_howto.html

Kate Plugin

Screenshot.

Automake based. Generates a plugin for Kate the text editor.

After make install, you'll find it in Kate -> Settings -> Configure Kate... -> Application -> Plugins in the plugins manager tab (it's called My first Kate plugin) Nothing appears on execute. The name My First Kate Plugin is set in the .desktop file as well as the author name.

Kate plugins tutorial: http://kate.kde.org/doc/pluginhowto.php

Kate plugin with config page

Screenshot

Automake based. Generates a plugin with config page for Kate the text editor.

After make install, you'll find it in Kate -> Settings -> Configure Kate... -> Application -> Plugins in the plugins manager tab (it's called My first Kate plugin). Nothing appears on execute. The name My First Kate Plugin is set in the .desktop file as well as the author name. The config page will appear in Kate -> Settings -> Configure Kate -> under Application > Plugins where you check the plugin and then the config page is located under Plugins.
See screenshot.

Kate plugins tutorial: http://kate.kde.org/doc/pluginhowto.php

Simple DCOP Server

Screenshot

Automake based. Generates a basic KDE DCOP server. This is an ideal starting point for a DCOP server that does not require a complete GUI interface. It's just a DCOP server within a KMainWindow without any menus.

Tutorial: http://docs.kde.org/en/3.4/kdevelop/kdearch/components.html

KDE DCOP Service

Screenshot

Automake based. It generates a framework for a KDE dcop service and client access library: it is a program controlled by DCOP and it has no GUI. When you execute it, you enable the service.

In a terminal, you can call for example:

annma@localhost:~$ dcop kdcopser serviceInterface add "mystuff"
kdcopser: Adding mystuff to the list

To see all the DCOP calls available, you will do:

annma@localhost:~$ dcop kdcopser serviceInterface
QCStringList interfaces()
QCStringList functions()
QString string(int)
QStringList list()
void add(QString)
bool remove(QString)
bool exit()

More informations on DCOP services: http://docs.kde.org/en/3.4/kdevelop/kdearch/components.html

KDE Screen Saver

Screenshot

Automake based. Generates a framework for a KDE screensaver. As you can see on the screenshot, it installs in KControl in Appearance & Themes -> Screen Saver.

KFile plugin

Automake based. Generates a KFile plugin for konqueror to display meta information.
I could not find where you can see the template effect though.

Tutorial: http://developer.kde.org/documentation/tutorials/kfile-plugin/t1.html
KFile API doc: http://api.kde.org/3.5-api/kdelibs-apidocs/kio/kfile/html/index.html

KHTML Part plugin

Generates a plugin for the KHTML part.

API reference: http://api.kde.org/3.5-api/kdelibs-apidocs/khtml/html/index.html
Does not compile at the moment.

Kicker Applet

Screenshot

Automake based. Generates a framework for an applet that embeds into the KDE panel. After make install, the template installs an applet that displays 42. You can see it by right clicking kicker ->Panel Menu -> Add to Panel -> Applet ->your_applet_name. On right click on the applet handle you have all the usual context menu.

Tip: Use the Panel Applet Proxy to run the applet from a console to view debugging output
e.g. $ appletproxy $KDEDIR/share/apps/kicker/applets/applet.desktop

.

Tutorial: http://techbase.kde.org/Development/Tutorials/KDE3/Extending_the_KDE_Panel

KIO slave

Screenshot

Automake based. Generates a framework for an IO slave. After make install you can see the template in action by typing your_project_name:/ in konqueror as seen on the screenshot.

Tutorial: http://www.heise.de/ct/english/01/05/242/

KOffice Part

You need KOffice headers to get it running.
Automake based. Generates a framework for a full KOffice Application.

koDocument API doc: http://koffice.org/developer/apidocs/lib/html/classKoDocument.html

Konqueror Navigation Panel plugin

Screenshot

Automake based. Generates a framework for a plugin that embeds into Konqueror's navigation panel. After make install, start a new Konqueror instance and in the Window menu, click on Show Navigation Panel. You will then see your plugin (see screenshot).

Noatun UI plugin

Screenshot

You need Noatun headers to get it running.
Automake based. Generates a simple user interface plugin for Noatun. Noatun is the KDE player in kdemultimedia. After you build the project and install it, you can start Noatun, go in the Settings menu, Configure Noatun... -> Plugins and in the Interfaces tab you will find your plugin (see screenshot below). Click on your plugin to enable it.
When accepted to be include in the main KDE distribution, Noatun plugins are located in the kdeaddons module.

Noatun Settings dialog with your plugin.

Tutorial: http://noatun.kde.org/doc/noatun-docs/

Noatun visualization plugin

Screenshot

You need Noatun headers and SDL to get it running (for example, I have libSDL1.2 and libSDL1.2-devel from my distribution).
Automake based. Generates a visualization plugin for noatun using SDL. Noatun is the KDE player in kdemultimedia. After you build the project and install it, you can start Noatun, go in the Settings menu, Configure Noatun... -> Plugins and in the Visualizations tab you will find your plugin (see screenshot below). Click on your plugin to enable it.
When accepted to be include in the main KDE distribution, Noatun plugins are located in the kdeaddons module.

Noatun Settings dialog with your plugin.

Tutorial: http://noatun.kde.org/doc/noatun-docs/

 

---

Last update: 2007-04-15

[ Edit ]