Rename a number of libraries and executables to avoid conflicts with KDE4

3 files changed, 33 insertions, 33 deletions

diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook
index a73c681a..374e0e37 100644
--- a/doc/kde_app_devel/index.docbook
+++ b/doc/kde_app_devel/index.docbook
@@ -531,7 +531,7 @@ the tdecore library, containing all classes that are non-visible elements to pro
 the tdeui library, containing user interface elements like menubars, toolbars, etc.
 </para></listitem>
 <listitem><para>
-the kfile library, containing the file selection dialogs
+the tdefile library, containing the file selection dialogs
 </para></listitem>
 </itemizedlist>
 </para>
diff --git a/doc/kdearch/index.docbook b/doc/kdearch/index.docbook
index 7bccb9fa..6e4cc884 100644
--- a/doc/kdearch/index.docbook
+++ b/doc/kdearch/index.docbook
@@ -71,7 +71,7 @@ respecting user preferences.
 </varlistentry>
 
 <varlistentry>
-<term><ulink url="kdeapi:kio/index.html">kio</ulink></term>
+<term><ulink url="kdeapi:tdeio/index.html">kio</ulink></term>
 <listitem><para>
 The <literal>kio</literal> library contains facilities for asynchronous,
 network transparent I/O and access to mimetype handling. It also provides the
@@ -381,13 +381,13 @@ Generic auto-completion of strings.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kio/KURLCompletion">KURLCompletion</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdeio/KURLCompletion">KURLCompletion</ulink></title>
 <para>
 Auto-completion of URLs.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kio/KShellCompletion">KShellCompletion</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdeio/KShellCompletion">KShellCompletion</ulink></title>
 <para>
 Auto-completion of executables.
 </para>
@@ -455,7 +455,7 @@ A combo box for selecting file names and URLs.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kfile/KURLRequester">KURLRequester</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdefile/KURLRequester">KURLRequester</ulink></title>
 <para>
 A line edit for selecting file names and URLs.
 </para>
@@ -494,7 +494,7 @@ Dialogs - full-featured dialogs for file, color and font selection.
 
 <itemizedlist>
 
-<listitem><formalpara><title><ulink url="kdeapi:kfile/KFileDialog">KFileDialog</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdefile/KFileDialog">KFileDialog</ulink></title>
 <para>
 A file selection dialog.
 </para>
@@ -512,7 +512,7 @@ A font selection dialog.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kfile/KIconDialog">KIconDialog</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdefile/KIconDialog">KIconDialog</ulink></title>
 <para>
 An icon selection dialog.
 </para>
@@ -548,7 +548,7 @@ A simple dialog for entering text.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kfile/KURLRequesterDlg">KURLRequesterDlg</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdefile/KURLRequesterDlg">KURLRequesterDlg</ulink></title>
 <para>
 A simple dialog for entering URLs.
 </para>
@@ -624,31 +624,31 @@ Object factory in plugins.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kio/KServiceType">KServiceType</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdeio/KServiceType">KServiceType</ulink></title>
 <para>
 Represents a service type.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kio/KService">KService</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdeio/KService">KService</ulink></title>
 <para>
 Represents a service.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kio/KMimeType">KMimeType</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdeio/KMimeType">KMimeType</ulink></title>
 <para>
 Represents a MIME type.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kio/KServiceTypeProfile">KServiceTypeProfile</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdeio/KServiceTypeProfile">KServiceTypeProfile</ulink></title>
 <para>
 User preferences for MIME type mappings.
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kio/KServiceTypeProfile">KTrader</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdeio/KServiceTypeProfile">KTrader</ulink></title>
 <para>
 Querying for services.
 </para>
@@ -2019,7 +2019,7 @@ objects or in most cases the generic
 
 <para>
 In order to use a shared library service in an application, you need to obtain a
-<ulink url="kdeapi:kio/KService.html">KService</ulink> object
+<ulink url="kdeapi:tdeio/KService.html">KService</ulink> object
 representing it. This is discussed in the 
 <ulink url="mime.html">section about MIME types</ulink> (and in a section about the
 trader to be written :-)
@@ -2073,7 +2073,7 @@ A DCOP service is usually implemented as a program that is started up when it is
 needed. It then goes into a loop and listens for DCOP connections. The program 
 may be an interactive one, but it may also run completely or for a part of its
 lifetime as a daemon in the background without the user noticing it. An example 
-for such a daemon is <literal>kio_uiserver</literal>, which implements user interaction 
+for such a daemon is <literal>tdeio_uiserver</literal>, which implements user interaction 
 such as progress dialog for the KIO library. The advantage of such a centralized 
 daemon in this context is that e.g. the download progress for several different 
 files can be shown in one window, even if those downloads were initiated from 
@@ -2115,14 +2115,14 @@ on the user's settings, the cursor will be changed.
 </para>
 
 <para>
-Here is the definition of <literal>kio_uiserver</literal>:
+Here is the definition of <literal>tdeio_uiserver</literal>:
 </para>
 
 <programlisting>
 [Desktop Entry]
 Type=Service
-Name=kio_uiserver
-Exec=kio_uiserver
+Name=tdeio_uiserver
+Exec=tdeio_uiserver
 X-DCOP-ServiceType=Unique
 X-TDE-StartupNotify=false
 </programlisting>
@@ -2141,9 +2141,9 @@ class:
 <programlisting>
 DCOPClient *client = kapp->dcopClient();
 client->attach();
-if (!client->isApplicationRegistered("kio_uiserver")) {
+if (!client->isApplicationRegistered("tdeio_uiserver")) {
     QString error;
-    if (TDEApplication::startServiceByName("kio_uiserver", QStringList(), &amp;error))
+    if (TDEApplication::startServiceByName("tdeio_uiserver", QStringList(), &amp;error))
         cout &lt;&lt; "Starting kioserver failed with message " &lt;&lt; error &lt;&lt; endl;
 }
 ...
@@ -2151,9 +2151,9 @@ QByteArray data, replyData;
 QCString replyType;
 QDataStream arg(data, IO_WriteOnly);
 arg &lt;&lt; true;
-if (!client->call("kio_uiserver", "UIServer", "setListMode(bool)", 
+if (!client->call("tdeio_uiserver", "UIServer", "setListMode(bool)", 
                   data, replyType, replyData))
-    cout &lt;&lt; "Call to kio_uiserver failed" &lt;&lt; endl;
+    cout &lt;&lt; "Call to tdeio_uiserver failed" &lt;&lt; endl;
 ...
 </programlisting>
 
@@ -2170,7 +2170,7 @@ the name is appearing in the <literal>Name</literal> line of the desktop
 file. An alternative is to use
 <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>.
+<literal>"tdeio_uiserver.desktop"</literal>.
 </para>
 
 <para>
@@ -2297,7 +2297,7 @@ an icon <filename>fooicon.png</filename>, which represents the file e.g. in
 
 <para>
 In the KDE libraries, such a type definition is mapped to an instance of the 
-class <ulink url="kdeapi:kio/KMimeType.html">KMimeType</ulink>.
+class <ulink url="kdeapi:tdeio/KMimeType.html">KMimeType</ulink>.
 Use this like in the following example:
 </para>
 
@@ -2350,7 +2350,7 @@ forget about them.)
 You may want to find out a MIME from the contents of file instead of
 the file name. This is more reliable, but also slower, as it requires
 reading a part of the file. This is done with the 
-<ulink url="kdeapi:kio/KMimeMagic.html">KMimeMagic</ulink> 
+<ulink url="kdeapi:tdeio/KMimeMagic.html">KMimeMagic</ulink> 
 class, which has different error handling:
 </para>
 
@@ -2481,12 +2481,12 @@ else
 
 <para>
 For even more complex queries, there is a full-blown CORBA-like
-<ulink url="kdeapi:kio/KTrader.html">trader</ulink>.
+<ulink url="kdeapi:tdeio/KTrader.html">trader</ulink>.
 </para>
 
 <para>
 In order to run an application service with some URLs, use 
-<ulink url="kdeapi:kio/KRun.html">KRun</ulink>:
+<ulink url="kdeapi:tdeio/KRun.html">KRun</ulink>:
 </para>
 
 <programlisting>
@@ -2602,7 +2602,7 @@ deletes itself. Thus, a typical use case will look like this:
 <programlisting>
 void FooClass::makeDirectory()
 {
-    SimpleJob *job = TDEIO::mkdir(KURL("file:/home/bernd/kiodir"));
+    SimpleJob *job = TDEIO::mkdir(KURL("file:/home/bernd/tdeiodir"));
     connect( job, SIGNAL(result(TDEIO::Job*)), 
              this, SLOT(mkdirResult(TDEIO::Job*)) );
 }
diff --git a/doc/tdevelop/tdevelop-install.docbook b/doc/tdevelop/tdevelop-install.docbook
index 5e07b0b6..14f7236b 100644
--- a/doc/tdevelop/tdevelop-install.docbook
+++ b/doc/tdevelop/tdevelop-install.docbook
@@ -608,7 +608,7 @@ That's all. If you installed &tdevelop; in the default &kde; directory you may n
 <indexterm zone="compile-and-install-options-dir">
   <primary>TDEDIRS</primary></indexterm>
 <indexterm zone="compile-and-install-options-dir">
-  <primary>kbuildsycoca</primary></indexterm>
+  <primary>tdebuildsycoca</primary></indexterm>
 
 <para>
 By default <command>configure</command> prepares the IDE to be installed in the default &kde; directory. This is necessary because &tdevelop; assumes direct access to some tools and parts which reside there. If want to use your own installation directory, you must tell <command>configure</command> this by the <option>--prefix</option> option:
@@ -635,7 +635,7 @@ Call up a shell and have the following commands executed before you start &tdeve
   </member>
   <member>
     <prompt>~&gt; </prompt>
-    <userinput>kbuildsycoca</userinput>
+    <userinput>tdebuildsycoca</userinput>
   </member>
   <member>
   (Now start &tdevelop;:)
@@ -661,14 +661,14 @@ In a tcsh shell you must set the environment variables using:
     <userinput>setenv TDEDIRS /usr/local/kde:/opt/trinity</userinput>
 </member></simplelist></informalexample>
 <para>
-The <command>kbuildsycoca</command> command (<quote>build system control cache</quote>) looks around for libraries and caches their location and version, so that &tdevelop; can find them. The caveat is that it takes noticeable time&mdash;and it has to be run any time you call up the shell to start &tdevelop; from a non-default directory. You may want to put the above commands into a shell script to reduce the typing effort.
+The <command>tdebuildsycoca</command> command (<quote>build system control cache</quote>) looks around for libraries and caches their location and version, so that &tdevelop; can find them. The caveat is that it takes noticeable time&mdash;and it has to be run any time you call up the shell to start &tdevelop; from a non-default directory. You may want to put the above commands into a shell script to reduce the typing effort.
 </para>
 <para>
-(You could as well put the lines in your <filename>.bashrc</filename> or <filename>.cshrc</filename> file, but this is not advisable as <command>kbuildsycoca</command> will then be run any time you call up the shell.)
+(You could as well put the lines in your <filename>.bashrc</filename> or <filename>.cshrc</filename> file, but this is not advisable as <command>tdebuildsycoca</command> will then be run any time you call up the shell.)
 </para>
 
 <note><para>
-The <command>kbuildsycoca</command> command does not run from within the root. You must call it from a non-root user. (But is <emphasis>not a very good idea</emphasis> after all to do software development from within the root!)
+The <command>tdebuildsycoca</command> command does not run from within the root. You must call it from a non-root user. (But is <emphasis>not a very good idea</emphasis> after all to do software development from within the root!)
 </para></note>
 </sect3> <!-- compile-and-install-options-dir -->