diff options
| author | tpearson <tpearson@283d02a7-25f6-0310-bc7c-ecb5cbfe19da> | 2010-09-18 20:35:25 +0000 |
|---|---|---|
| committer | tpearson <tpearson@283d02a7-25f6-0310-bc7c-ecb5cbfe19da> | 2010-09-18 20:35:25 +0000 |
| commit | a93c19aaac4a8bdd50dcf36b372932e7145097f2 (patch) | |
| tree | d8c179eef20efa70c159d93d6c6135bc20fcb650 /dcop | |
| parent | ffbbad3e9ef672d8b59f2fd628addb705b6d85da (diff) | |
| download | tdelibs-a93c19aaac4a8bdd50dcf36b372932e7145097f2.tar.gz tdelibs-a93c19aaac4a8bdd50dcf36b372932e7145097f2.zip | |
All documentation references to KDE should now be converted to Trinity for the new API website
git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdelibs@1176842 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Diffstat (limited to 'dcop')
| -rw-r--r-- | dcop/Mainpage.dox | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/dcop/Mainpage.dox b/dcop/Mainpage.dox index af4f14ec3..d573b01b5 100644 --- a/dcop/Mainpage.dox +++ b/dcop/Mainpage.dox @@ -11,7 +11,7 @@ Either unix domain sockets or TCP/IP sockets are supported. DCOP is built on top of the Inter Client Exchange (ICE) protocol, which comes standard as a part of X11R6 and later. It also depends on Qt, but beyond that it does not require any other libraries. Because of this, -it is extremely lightweight, enabling it to be linked into all KDE +it is extremely lightweight, enabling it to be linked into all Trinity applications with low overhead. \section model Model: @@ -270,7 +270,7 @@ class MyInterface : virtual public DCOPObject As you can see, you're essentially declaring an abstract base class, which virtually inherits from DCOPObject. -If you're using the standard KDE build scripts, then you can simply +If you're using the standard Trinity build scripts, then you can simply add this file (which you would call MyInterface.h) to your sources directory. Then you edit your Makefile.am, adding 'MyInterface.skel' to your SOURCES list and MyInterface.h to include_HEADERS. @@ -551,7 +551,7 @@ stream << pid; kapp->dcopClient()->emitDCOPSignal("clientDied(pid_t)", params); \endcode -The task manager of the KDE panel connects to this signal. It uses an +The task manager of the Trinity panel connects to this signal. It uses an anonymous connection (it doesn't require that the signal is being emitted by KLauncher) that is non-volatile: @@ -570,7 +570,7 @@ a clientDied(void) DCOP function. \section conclusion Conclusion: Hopefully this document will get you well on your way into the world of -inter-process communication with KDE! Please direct all comments and/or -suggestions to the KDE Core Developers List \<kde-core-devel@kde.org\>. +inter-process communication with Trinity! Please direct all comments and/or +suggestions to the Trinity Core Developers List \<kde-core-devel@kde.org\>. */ |