Updated some of the TDevelop documentation toc files. This relates to bug 1859.
Also some KDE to TDE renaming.

diff --git a/doc/tde_app_devel/index.docbook b/doc/tde_app_devel/index.docbook
index 60bae16..dfcaec9 100644
--- a/doc/tde_app_devel/index.docbook
+++ b/doc/tde_app_devel/index.docbook
@@ -46,8 +46,8 @@
 </abstract>
 
 <keywordset>
-<keyword>KDE</keyword>
-<keyword>KDevelop</keyword>
+<keyword>TDE</keyword>
+<keyword>TDevelop</keyword>
 <keyword>IDE</keyword>
 <keyword>development</keyword>
 <keyword>programming</keyword>
@@ -60,9 +60,9 @@
 <para>
 As Unix Systems are becoming more and more popular to even beginners working with computer machines 
 due to its advantages in regards of stability and functionality, most are somehow disappointed, because 
-those applications don't have a consistent look and each one behaves different from another. With KDE, 
+those applications don't have a consistent look and each one behaves different from another. With TDE, 
 developers have an almost perfect way to create first-class applications for Unix desktop systems to get 
-a wider user community by the mere quality their applications have to offer. Therefore, KDE becomes more 
+a wider user community by the mere quality their applications have to offer. Therefore, TDE becomes more 
 and more popular as a base for programming design, and developers want to take advantage of the 
 possibilities that the system has to offer.
 </para>
@@ -74,8 +74,8 @@
 C++ programming language; if not, you should make yourself familiar with that first. Information about 
 C++ is available through various sources either in printed form at your local bookstore or by tutorials 
 found on the Internet. Knowledge about the design of Graphical User Interfaces is not required, as this 
-handbook tries to cover the application design for KDE programs, which also includes an introduction into 
-the Qt toolkit as well as the KDE libraries and the design of User Interfaces. Also, you should have made 
+handbook tries to cover the application design for TDE programs, which also includes an introduction into 
+the Qt toolkit as well as the TDE libraries and the design of User Interfaces. Also, you should have made 
 yourself comfortable with &tdevelop; by reading The User Manual to &tdevelop;, which contains a descriptive 
 review of the functionality provided by the IDE. 
 </para>
@@ -84,7 +84,7 @@
 <sect1 id="c1s2">
 <title>About this Handbook</title>
 <para>
-This handbook has been written to give developers an introduction into KDE application development by 
+This handbook has been written to give developers an introduction into TDE application development by 
 using the KDevelop Integrated Development Environment. 
 </para>
 <para>
@@ -104,7 +104,7 @@
 <sect2 id="c1s2s1">
 <title>In the next chapter</title>
 <para>
-We'll take a look at the Qt and KDE libraries, showing basic concepts and why things are the way they are. 
+We'll take a look at the Qt and TDE libraries, showing basic concepts and why things are the way they are. 
 Also, we will discuss how to create the tutorial applications provided with the Qt toolkit by using 
 tdevelop;, so beginners can already see first results with a few steps, and thereby will learn how to make 
 use of some of &tdevelop;'s best features. 
@@ -132,17 +132,17 @@
 <sect1 id="c1s3">
 <title>Additional Information</title>
 <para>
-Additional information about Qt/KDE programming is available by various sources:
+Additional information about Qt/TDE programming is available by various sources:
 <itemizedlist>
 <listitem><para>Programming with Qt by Matthias Kalle Dalheimer</para></listitem>
 <listitem><para><ulink url="www.kdevelop.org">The User Manual to KDevelop, provided with the TDevelop IDE</ulink></para></listitem>
 <listitem><para><ulink url="doc.trolltech.com">The Online Reference to the Qt library</ulink></para></listitem>
-<listitem><para><ulink url="developer.kde.org">The KDE Developer web site</ulink></para></listitem>
+<listitem><para><ulink url="developer.kde.org">The TDE Developer web site</ulink></para></listitem>
 </itemizedlist>
 </para>
 <para>
 Additionally, you should look for help by subscribing to the various mailing lists, whose addresses 
-are available on the mentioned web sites, and on the Usenet newsgroups dedicated to users of KDE and 
+are available on the mentioned web sites, and on the Usenet newsgroups dedicated to users of TDE and 
 Unix Systems as well as about the C and C++ programming language. 
 </para>
 <para>
@@ -159,7 +159,7 @@
 </chapter>
 
 <chapter id="chapter2">
-<title>The KDE and Qt Libraries</title>
+<title>The TDE and Qt Libraries</title>
 <para>
 The Norwegian company TrollTech (<ulink url="http://www.trolltech.com">http://www.trolltech.com</ulink>) 
 provides a so-called GUI toolkit, named Qt. GUI means "Graphical User Interface", and therefore, Qt-based 
@@ -171,25 +171,20 @@
 which allows developers to provide their applications for both platforms. 
 </para>
 <para>
-The KDE Team (<ulink url="http://www.kde.org">http://www.kde.org</ulink>) joined together with the goal 
-to make using Unix Systems more friendly, and decided to use the Qt toolkit for the development of a window
-manager on X-Windows, plus a variety of tools included with the KDE packages. The K Desktop Environment 
-therefore contains the window manager kwm, the file manager kfm and the launch panel kpanel as the main 
-components plus a variety of first-class utilities and applications. After KDE was out, a lot of developers 
-turned their eyes towards the new environment and what it has to offer them. The KDE libraries are providing
-essential methods and classes that make all applications designed with them look similar and consistent, 
-so the user has the great advantage that he only has to get accustomed with an application's specific 
-usage, not with handling dialogs or buttons. Also, KDE programs integrate themselves into the desktop and 
-are able to interact with the file manager via drag'n drop, offer session management and many more, if all 
-features offered by the KDE libraries are used.  Both, the Qt toolkit and the KDE libraries, are implemented
-in the C++ programming language; therefore applications that make use of these libraries are also mostly 
-written in C++. In the following chapter, we'll make a short trip through the libraries to see what already
+The TDE libraries, which rely on the Qt toolkit, provide essential methods and classes that make all TDE
+applications designed with them look similar and consistent, so the user has the great advantage that he
+only has to get accustomed with an application's specific usage, not with handling dialogs or buttons.
+Also, TDE programs integrate themselves into the desktop and are able to interact with the file manager
+via drag'n drop, offer session management and many more, if all features offered by the TDE libraries are used.
+Both, the Qt toolkit and the TDE libraries, are implemented in the C++ programming language; therefore
+applications that make use of these libraries are also mostly written in C++. In the following chapter,
+we'll make a short trip through the libraries to see what already
 is provided and how Qt and TDE applications are created in general. 
 </para>
 <para>
-Both, the Qt toolkit and the KDE libraries, are implemented in the C++ programming language; 
+Both, the Qt toolkit and the TDE libraries, are implemented in the C++ programming language; 
 therefore applications that make use of these libraries are also mostly written in C++. In the following 
-chapter, we'll make a short trip through the libraries to see what already is provided and how Qt and KDE 
+chapter, we'll make a short trip through the libraries to see what already is provided and how Qt and TDE 
 applications are created in general. 
 </para>
 
@@ -206,9 +201,9 @@
 </itemizedlist>
 </para>
 <para>
-Therefore knowing the Qt classes is very essential, even if you only want to program KDE-applications. 
+Therefore knowing the Qt classes is very essential, even if you only want to program TDE-applications. 
 To have an impression on the basic concept how GUI-applications are constructed and compiled, we'll first
-have a look at a sample Qt-only program; then we'll extend it to a KDE program.
+have a look at a sample Qt-only program; then we'll extend it to a TDE program.
 </para>
 
 <sect2 id="c2s1s1">
@@ -273,7 +268,7 @@
 For <classname>QApplication</classname>, you will see the constructor and all other methods that this 
 class provides. If you follow a link, you will get more information about the usage and meaning of the 
 methods, which is very useful when you sometimes can't detect the correct use or want to have an example. 
-This also counts for the KDE library documentation, which uses a similar documentation type; therefore 
+This also counts for the TDE library documentation, which uses a similar documentation type; therefore 
 this is almost all you have to know about using the class-references with the documentation browser. 
 </para>
 <sect3 id="c2s1s2s1">
@@ -332,7 +327,7 @@
 <note><para>
 For already advanced users: The button has no parent declared in the constructor, therefore it
 is a top-level widget alone and runs in a local event loop which doesn't need to wait for the main
-event loop.  See the QWidget class documentation and The KDE Library Reference Guide</para>
+event loop.  See the QWidget class documentation and The TDE Library Reference Guide</para>
 </note> 
 
 </sect3>
@@ -510,7 +505,7 @@
 By using signals and slots, your program's objects can interact with each other easily without explicitly 
 depending on the type of the receiver object. You will learn more about using this mechanism for productive 
 usage later in this handbook. More information about the Signals/Slot mechanism can also be found in 
-<ulink url="developer.kde.org/documentation/library/libraryref.html">The KDE Library Reference Guide</ulink> 
+<ulink url="developer.kde.org/documentation/library/libraryref.html">The TDE Library Reference Guide</ulink> 
 and the <ulink url="doc.trolltech.com">Qt online reference</ulink>.
 </para>
 </sect3>
@@ -518,11 +513,11 @@
 </sect1>
 
 <sect1 id="c2s3">
-<title>What KDE provides</title>
+<title>What TDE provides</title>
 <sect2 id="c2s3s1">
-<title>The KDE 3.x libraries</title>
+<title>The TDE libraries</title>
 <para>
-The main KDE libraries you'll be using for creating your own TDE applications are:
+The main TDE libraries you'll be using for creating your own TDE applications are:
 <itemizedlist>
 <listitem><para>
 the tdecore library, containing all classes that are non-visible elements to provide application functionality
@@ -536,16 +531,16 @@
 </itemizedlist>
 </para>
 <para>
-Additionally, for specific solutions KDE offers the following libraries:
+Additionally, for specific solutions TDE offers the following libraries:
 <itemizedlist>
 <listitem><para>
 the tdefx library, containing pixmaps, image effects the TDEStyle extension to QStyle
 </para></listitem>
 <listitem><para>
-the tdehtml library, containing KDE's html component
+the tdehtml library, containing TDE's html component
 </para></listitem>
 <listitem><para>
-the kjs library, containing KDE's Javascript support
+the kjs library, containing TDE's Javascript support
 </para></listitem>
 <listitem><para>
 the tdeio library, containing low level access to network files
@@ -556,14 +551,14 @@
 </itemizedlist>
 </para>
 <para>
-Next we'll have a look at what is needed to turn out first Qt Application into a KDE one.
+Next we'll have a look at what is needed to turn out first Qt Application into a TDE one.
 </para>
 </sect2>
 <sect2 id="c2s3s2">
-<title>Example KDE Application</title>
+<title>Example TDE Application</title>
 <para>
-In the following, you will see that writing a KDE application is not much more difficult than a 
-Qt application. For the use of KDE's features, you just have to use some other classes, and you're almost 
+In the following, you will see that writing a TDE application is not much more difficult than a 
+Qt application. For the use of TDE's features, you just have to use some other classes, and you're almost 
 done. As an example, we'll discuss the changed version of the Qt example from above: 
 <programlisting>
 #include &lt;tdeapplication.h>
@@ -589,7 +584,7 @@
 You see that first we have changed from <classname>QApplication</classname> to <classname>TDEApplication
 </classname>. Further, we had to change the previously used <methodname>setMainWidget()</methodname> method 
 to <methodname>setTopWidget</methodname>, which <classname>TDEApplication</classname> uses to set the main 
-widget. That's it! Your first KDE application is ready - you only have to tell the compiler the KDE 
+widget. That's it! Your first TDE application is ready - you only have to tell the compiler the TDE 
 include path and the linker to link in the tdecore library with -ltdecore. 
 </para>
 <para>
@@ -602,7 +597,7 @@
 What you should have looked into additionally until now is the reference documentation for Qt, 
 especially the <classname>QApplication</classname>, <classname>QWidget</classname> and <classname>QObject
 </classname> class and the tdecore library documentation for the <classname>TDEApplication</classname> class. 
-The <ulink url="developer.kde.org/documentation/library/libraryref.html">KDE Library Reference handbook</ulink> 
+The <ulink url="developer.kde.org/documentation/library/libraryref.html">TDE Library Reference handbook</ulink> 
 also covers a complete description about the invocation of the <classname>QApplication</classname> and 
 <classname>TDEApplication</classname> constructors including command-line argument processing. 
 </para>
@@ -622,7 +617,7 @@
 already provided by the source skeleton.  You can choose from several project types according to your project goals:
 <itemizedlist>
 <listitem><para>
-KDE Application Framework: includes source code for a complete frame structre of a standard KDE application
+TDE Application Framework: includes source code for a complete frame structre of a standard TDE application
 </para></listitem>
 <listitem><para>
 QMake Project: Creates an application framework based around Trolltech's qmake configuration system
@@ -637,7 +632,7 @@
 </para>
 <para>
 In this chapter we'll see how the Application Wizard can be invoked and what has to be done to generate 
-a KDE application project.  This will also be the initial step of our coverage, where we will create the 
+a TDE application project.  This will also be the initial step of our coverage, where we will create the 
 initial version of a sample project.  For all other project types the steps are usualyl the same, but you 
 may not have as many options available.
 ** Diff limit reached (max: 250 lines) **