summaryrefslogtreecommitdiffstats
path: root/kutils/kcmoduleproxyIface.h
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2013-01-25 00:35:07 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2013-01-25 00:35:07 -0600
commit703fb0c89c2eee56a1e613e67a446db9d4287929 (patch)
treedd8c5ca66075cd89c2638a2b48cf78386a9870a7 /kutils/kcmoduleproxyIface.h
parent818e7abec3d5d3809b6b77293558678371c16b71 (diff)
downloadtdelibs-703fb0c89c2eee56a1e613e67a446db9d4287929.tar.gz
tdelibs-703fb0c89c2eee56a1e613e67a446db9d4287929.zip
Rename KCModule, KConfig, KIO, KServer, and KSocket to avoid conflicts with KDE4
Diffstat (limited to 'kutils/kcmoduleproxyIface.h')
-rw-r--r--kutils/kcmoduleproxyIface.h20
1 files changed, 10 insertions, 10 deletions
diff --git a/kutils/kcmoduleproxyIface.h b/kutils/kcmoduleproxyIface.h
index ff597b5c6..5bf24ac91 100644
--- a/kutils/kcmoduleproxyIface.h
+++ b/kutils/kcmoduleproxyIface.h
@@ -24,16 +24,16 @@
/**
* @ingroup kcmodule
- * @brief DCOP Interface for KCModule.
+ * @brief DCOP Interface for TDECModule.
*
- * A module (which is loaded via KCModuleProxy) does always have
+ * A module (which is loaded via TDECModuleProxy) does always have
* this DCOP interface, whether it's in root mode or not.
*
* @since 3.4
* @internal
* @author Frans Englich <frans.englich@telia.com>
*/
-class KCModuleProxyIface : virtual public DCOPObject
+class TDECModuleProxyIface : virtual public DCOPObject
{
K_DCOP
@@ -81,7 +81,7 @@ k_dcop_signals:
*
* @param c true if the module is modified, false if its not.
* @param module a string identifying the module which was changed. This
- * is typically "KCModuleProx-X" where X is the module's name.
+ * is typically "TDECModuleProx-X" where X is the module's name.
*/
virtual void changed( bool c );
@@ -93,25 +93,25 @@ k_dcop_signals:
* @ingroup kcmodule
* @brief DCOP interface for communicating with the real module running in root mode.
*
- * When a KCModuleProxy tells kcmshell to load "itself" and embed into the
- * KCModuleProxy, this DCOP interface is used to communicate to the real KCModuleProxy, since
- * the KCModuleProxy which told kcmshell to load itself, is nothing but a shell.
+ * When a TDECModuleProxy tells kcmshell to load "itself" and embed into the
+ * TDECModuleProxy, this DCOP interface is used to communicate to the real TDECModuleProxy, since
+ * the TDECModuleProxy which told kcmshell to load itself, is nothing but a shell.
*
* Currently is only the changed signal routed, but it's possible to proxy
- * the rest of the KCModuleProxy API, if it turns out necessary.
+ * the rest of the TDECModuleProxy API, if it turns out necessary.
*
* @since 3.4
* @internal
* @author Frans Englich <frans.englich@telia.com>
*/
-class KCModuleProxyRootDispatcher : virtual public DCOPObject
+class TDECModuleProxyRootDispatcher : virtual public DCOPObject
{
K_DCOP
k_dcop:
/**
- * KCModuleProxyIface::changed() gets connected to this.
+ * TDECModuleProxyIface::changed() gets connected to this.
*/
virtual void changed( bool c ) = 0;