From 95e28f5bcadbf0ac052c4f29d77b4ab5e6648d1b Mon Sep 17 00:00:00 2001
From: Timothy Pearson <kb9vqf@pearsoncomputing.net>
Date: Sun, 20 Jan 2013 00:24:38 -0600
Subject: Rename KApplication to TDEApplication to avoid conflicts with KDE4

---
 doc/kdearch/index.docbook | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

(limited to 'doc/kdearch')

diff --git a/doc/kdearch/index.docbook b/doc/kdearch/index.docbook
index 000cf9c3..65963503 100644
--- a/doc/kdearch/index.docbook
+++ b/doc/kdearch/index.docbook
@@ -109,7 +109,7 @@ Core application skeleton - classes needed by almost every application.
 <itemizedlist>
 
 <listitem><formalpara>
-<title><ulink url="kdeapi:tdecore/KApplication">KApplication</ulink></title>
+<title><ulink url="kdeapi:tdecore/TDEApplication">TDEApplication</ulink></title>
 <para>
 Initializes and controls a KDE application.
 </para>
@@ -1809,7 +1809,7 @@ action->setWhatsThis(i18n("Deletes the marked file"))
 
 <para>
 The invocation of <application>KHelpCenter</application> is encapsulated in the
-<ulink url="kdeapi:tdecore/KApplication">KApplication</ulink>
+<ulink url="kdeapi:tdecore/TDEApplication">TDEApplication</ulink>
 class. In order to show the manual of your application, just use 
 </para>
 
@@ -2091,8 +2091,8 @@ name. As additional properties, it contains two lines:
 <literal>X-DCOP-ServiceType</literal> specifies the way the service is
 started. The value <literal>Unique</literal> says that the service must not be
 started more than once. This means, if you try to start this service (e.g. via 
-<ulink url="kdeapi:tdecore/KApplication.html#startServiceByName">
-KApplication::startServiceByName()</ulink>, KDE looks whether it is already 
+<ulink url="kdeapi:tdecore/TDEApplication.html#startServiceByName">
+TDEApplication::startServiceByName()</ulink>, KDE looks whether it is already 
 registered with DCOP and uses the running service. If it is not registered yet, 
 KDE will start it up and wait until is registered. Thus, you can immediately 
 send DCOP calls to the service. In such a case, the service should be implemented
@@ -2134,7 +2134,7 @@ X-TDE-StartupNotify=false
 <title>Using DCOP services</title>
 
 <para>
-A DCOP service is started with one of several methods in the KApplication
+A DCOP service is started with one of several methods in the TDEApplication
 class:
 </para>
 
@@ -2143,7 +2143,7 @@ DCOPClient *client = kapp->dcopClient();
 client->attach();
 if (!client->isApplicationRegistered("kio_uiserver")) {
     QString error;
-    if (KApplication::startServiceByName("kio_uiserver", QStringList(), &amp;error))
+    if (TDEApplication::startServiceByName("kio_uiserver", QStringList(), &amp;error))
         cout &lt;&lt; "Starting kioserver failed with message " &lt;&lt; error &lt;&lt; endl;
 }
 ...
@@ -2165,10 +2165,10 @@ instead, because it is much simpler and less error prone.
 
 <para>
 In the example given here, the service was started "by name", i.e. the
-first argument to <function>KApplication::startServiceByName()</function> is
+first argument to <function>TDEApplication::startServiceByName()</function> is
 the name is appearing in the <literal>Name</literal> line of the desktop
 file. An alternative is to use
-<function>KApplication::startServiceByDesktopName()</function>, which takes
+<function>TDEApplication::startServiceByDesktopName()</function>, which takes
 the file name of its desktop file as argument, i.e. in this case
 <literal>"kio_uiserver.desktop"</literal>.
 </para>
-- 
cgit v1.2.1