Tools

You can use the Subversion version control system to access the KDE source repository.

There is a list of tools available, that can be used for developing KDE applications. These include low-level debuggers, as well as the KDevelop *Integrated Development Environment (IDE), and various design programs.

Libraries and Interfaces

DCOP and D-Bus

DCOP is the message bus built into KDE 3, that is used for inter-process communication (IPC) between different KDE applications. DCOP can be used in order to remotely control KDE applications from your own application or to provide scriptable interfaces for your own application.

KDE Automation writeupDocument by Olaf Zanger showing an overview of the scripting capabilities in KDE 2.x. Includes usage of "dcop", "kdcop", scripting languages, xmlrpc, and a FAQ.

Connect KDE applications using DCOPIBM DeveloperWorks tutorial, shows how to use kdcop and dcop with several examples such as instantly messaging a contact in kopete when he comes online, and also how to create a simple DCOP-aware application.

KIO-Slaves

KDE is network transparent. This means that each application can access files via many network protocols just as if they were stored locally. There exist access modules (KIO-Slaves) for Samba (Windows Shares), HTTP, FTP and many other protocols.

Using IOSlavesIOSlaves are the subprocesses KDE uses to fetch remote files without blocking the user interface. This document discusses how they work and how to use them. (Somewhat dated, but might still be useful).