KDE IPC module(last modified: 30 April, '07)
KDE inter-process communication abstraction
kdeipc abstracts away the details of what back-end is being used to communicate to a KDE application, be it the dcop process, PyKDE, PyDCOP, or (in the future) DBUS. It lets you just get on and communicate. Use as follows:
| 1 | import kdeipc |
| 2 | kicker = kdeipc.applications.Kicker |
| 3 | print kicker.Panel.panelSize() |
Changelog
- 30/04/07: You can now use kdeipc.launch("myapp") which will start the application 'myapp' and then return the DCOP interface for it, much like dcopstart
- 31/01/07: Added SuperKarambaEngine and ExistingPyKde3ApplicationEngine. They are backends that use existing DCOPClient instances to connect to DCOP instead of creating new ones and hence sparking a new KApplication.
You can therefore now use kdeipc from SuperKaramba by adding the line 'kdeipc.engine = kdeipc.SuperKarambaEngine' once you have imported kdeipc. I may make detection of SuperKaramba automatic, such that you won't need to add line. I'll see how many people end up using this.
Download
(or view the source online)