Additional renaming of kde to tde

1 files changed, 26 insertions, 26 deletions

diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook
index 0ebf7e71..3cc34883 100644
--- a/doc/kde_app_devel/index.docbook
+++ b/doc/kde_app_devel/index.docbook
@@ -1,7 +1,7 @@
 <?xml version="1.0" ?>
 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
-  <!ENTITY kdevelop "<application>KDevelop</application>">
-  <!ENTITY kappname "&kdevelop;">
+  <!ENTITY tdevelop "<application>KDevelop</application>">
+  <!ENTITY kappname "&tdevelop;">
   <!ENTITY % addindex "INCLUDE">
   <!ENTITY % English "INCLUDE" > <!-- change language only here -->
 ]>
@@ -9,7 +9,7 @@
 <book lang="&language;">
 
 <bookinfo>
-<title>The &kdevelop; Programming Handbook</title>
+<title>The &tdevelop; Programming Handbook</title>
 
 <date>2002-12-05</date>
 <releaseinfo>2.0</releaseinfo>
@@ -42,7 +42,7 @@
 
 <abstract>
 <para>The User Guide to C++ Application Design for the K Desktop Environment (KDE) with
-the &kdevelop; IDE</para>
+the &tdevelop; IDE</para>
 </abstract>
 
 <keywordset>
@@ -76,7 +76,7 @@ C++ is available through various sources either in printed form at your local bo
 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 
-yourself comfortable with &kdevelop; by reading The User Manual to &kdevelop;, which contains a descriptive 
+yourself comfortable with &tdevelop; by reading The User Manual to &tdevelop;, which contains a descriptive 
 review of the functionality provided by the IDE. 
 </para>
 </sect1>
@@ -106,8 +106,8 @@ online-manuals.
 <para>
 We'll take a look at the Qt and KDE 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 
-kdevelop;, so beginners can already see first results with a few steps, and thereby will learn how to make 
-use of some of &kdevelop;'s best features. 
+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. 
 </para>
 </sect2>
 
@@ -135,7 +135,7 @@ You will learn how to:
 Additional information about Qt/KDE 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 KDevelop IDE</ulink></para></listitem>
+<listitem><para><ulink url="www.tdevelop.org">The User Manual to KDevelop, provided with the KDevelop 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>
 </itemizedlist>
@@ -147,7 +147,7 @@ Unix Systems as well as about the C and C++ programming language.
 </para>
 <para>
 For obtaining help about the KDevelop IDE, you should send requests to our mailinglist at 
-<email>kdevelop@kdevelop.org</email>. Mind that the KDevelop team is dedicated to provide the means to enable you to 
+<email>tdevelop@tdevelop.org</email>. Mind that the KDevelop team is dedicated to provide the means to enable you to 
 program applications and therefore is not intended as a technical support team in cases where the 
 applications you're developing don't work due to implementation errors or misconfigurations of your 
 operating system. By this, we ask all users to take advantage of the mailinglist in any case you're running 
@@ -259,7 +259,7 @@ an integer value to the overlaying Operating System signaling that the applicati
 <title>The Reference Documentation for Qt</title>
 <para>
 Now, let's have a quick look at the reference documentation of the Qt library. To do this, start 
-&kdevelop; and select "Qt" from the tree in the Documentation tab. The documentation browser opens 
+&tdevelop; and select "Qt" from the tree in the Documentation tab. The documentation browser opens 
 and shows you the start page of the Qt reference. This will be your first place to get information 
 about Qt, it's classes and the available functions they provide. Also, the above program is the first 
 that is included in the tutorials section. To get to the classes we want to have a look at, 
@@ -595,7 +595,7 @@ include path and the linker to link in the tdecore library with -ltdecore.
 <para>
 As you now know what at least the <function>main()</function> function provides generally and how an 
 application gets visible and allows user and object interaction, we'll go on with the next chapter, 
-where our first application is made with &kdevelop;.  There you can also test everything which was 
+where our first application is made with &tdevelop;.  There you can also test everything which was 
 mentioned before and see the effects. 
 </para>
 <para>
@@ -617,7 +617,7 @@ also covers a complete description about the invocation of the <classname>QAppli
 <sect1 id="c3s1">
 <title>The Application Wizard</title>
 <para>
-&kdevelop;'s Application Wizard is intended to let you start working on new project with &kdevelop;.  Therefore 
+&tdevelop;'s Application Wizard is intended to let you start working on new project with &tdevelop;.  Therefore 
 all of your projects are first created by the wizard, and then you can start building them and extend what is 
 already provided by the source skeleton.  You can choose from several project types according to your project goals:
 <itemizedlist>
@@ -648,7 +648,7 @@ may not have as many options available.
 <sect2 id="c3s2s1">
 <title>Starting the Application Wizard and the First Page</title>
 <para>
-To start with your KDE application, open &kdevelop;.  From the Project menu, selection New Project.  The 
+To start with your KDE application, open &tdevelop;.  From the Project menu, selection New Project.  The 
 Application Wizard starts, and you'll see the selection tree on the first page containing available project 
 types that can be created.  Choose the C++ subtree, then KDE, then Application Framework.
 </para>
@@ -673,7 +673,7 @@ and select Next.
 <title>Header and Source Templates</title>
 <para>
 The next two pages show example headers that will go at the top of each of the header and source files that 
-you create using &kdevelop;.  For now, just leave these as the default, and select Next, then Finish.  If the
+you create using &tdevelop;.  For now, just leave these as the default, and select Next, then Finish.  If the
 Finish button is not activated, you haven't set all of the options correct.  Use the Back button to return
 to earlier menus and correct any mistakes.
 </para>
@@ -682,7 +682,7 @@ to earlier menus and correct any mistakes.
 <title>Finishing Up</title>
 <para>
 Upon completion, the Application Wizard should close and the messages window should popup displaying
-information about the tasks that &kdevelop; is currently doing.  At the end of all of the tasks, you
+information about the tasks that &tdevelop; is currently doing.  At the end of all of the tasks, you
 should see **** Success *****.  This means the application framework was successfully loaded.
 </para>
 </sect2>
@@ -696,7 +696,7 @@ of how the application framework looks.  This won't only help us get started, bu
 what in later steps.
 </para>
 <para>
-This chapter makes the assumption that you understand the basic navigation of &kdevelop;.  Consult the
+This chapter makes the assumption that you understand the basic navigation of &tdevelop;.  Consult the
 KDevelop User Manual for information if you need it.
 </para>
 <para>
@@ -707,7 +707,7 @@ The Automake manager shows the project files as follows:
 </mediaobject></screenshot>
 </para>
 <para>
-Before diving into the sources, we'll let &kdevelop; build an run our new application.  To do this, select
+Before diving into the sources, we'll let &tdevelop; build an run our new application.  To do this, select
 Build Project from the Build menu, or press F8.  The output window opens and displays output messages during
 the compilation phase.
 <programlisting>
@@ -822,7 +822,7 @@ returns to the directory it was started, processes it, then finishes.
 Our first line of interest is 24.  Notice on this line that g++, which is our C++ compiler, gets called by make
 to compile the first source code file in our project - in this case main.cpp.  Many extra command line options
 are also being used with the g++ compiler; some of which are defaults and some of which can be configured 
-via &kdevelop;.
+via &tdevelop;.
 </para>
 <para>
 Before the next file (kscribble.cpp, line 29) is compiled, the moc (meta object compiler) is first
@@ -1023,7 +1023,7 @@ inherits QWidget already.
 </para>
 <para>
 This chapter therefore describes how to use library widgets for creating views of KDE or 
-Qt applications that are generated with &kdevelop;, then we look at the libraries and what kind of 
+Qt applications that are generated with &tdevelop;, then we look at the libraries and what kind of 
 views are already offered. 
 </para>
 </sect1>
@@ -1046,7 +1046,7 @@ Change the inheritance of the provided view class to the class of the library wi
 <para>
 In either way, it is important to know that if the application framework is currently not linked 
 against the library that contains the widget, the linker will fail. After you decided to use a 
-certain widget, look for the library to link to; then open "Project"->"Options" from the &kdevelop; 
+certain widget, look for the library to link to; then open "Project"->"Options" from the &tdevelop; 
 menubar. Switch to the "Linker Options" page and look for the checkmarks indicating the libraries 
 that are currently used. If the library of your view widget is already checked, you can leave the 
 project options untouched and start doing the necessary changes due to your choice. If not, and the 
@@ -1206,7 +1206,7 @@ KAction</classname>, which provides the keyboard accelerator keys and access to
 standard keyboard accelerators. 
 </para>
 <para>
-By default, frame applications generated by &kdevelop; only use standard keyboard accelerators
+By default, frame applications generated by &tdevelop; only use standard keyboard accelerators
 such as F1 for accessing online-help, Ctrl+N for New File etc.
 </para>
 <para>
@@ -1252,7 +1252,7 @@ using the standard help key F1.  This context based help system is provided auto
 <classname>KMainWindow</classname> class, though as the author you must provide the content.
 </para>
 <para>
-As &kdevelop; also offers all types of help as well as the KDE framework generated by the 
+As &tdevelop; also offers all types of help as well as the KDE framework generated by the 
 application wizard already contains support for this, this chapter will help you find out where 
 and how to add your help functionality. </para>
 <para>
@@ -1306,7 +1306,7 @@ that the user wants to get help about a certain widget within the working view o
 It is placed in the toolbar and gets activated once the user hits the button. The cursor changes 
 to an arrow cursor with a question mark like the button itself looks like. The the user can press on 
 a visible widget item and gets a help window. As an exercise, you could try this behavior with the 
-<guibutton>What's this...?</guibutton> button within &kdevelop;. 
+<guibutton>What's this...?</guibutton> button within &tdevelop;. 
 </para>
 <para>
 To add the What's This...? help to one of your widgets, use the static method 
@@ -1321,7 +1321,7 @@ To add the What's This...? help to one of your widgets, use the static method
 <title>Introduction</title>
 <para>
 Due to the fact that projects often lack a complete set of user documentation, 
-all &kdevelop; projects contain a pre-build handbook that can be easily adapted; 
+all &tdevelop; projects contain a pre-build handbook that can be easily adapted; 
 therefore fulfiling another goal of KDE: providing enough online-help to support users that 
 are not familiar with an application. This chapter therefore introduces you on how to extend 
 the provided documentation template and what you have to do to make it available to the user. 
@@ -1341,10 +1341,10 @@ The format for editing this file is explained on
 <para>
 Another important part of the documentation is including a descriptive help for your class interfaces. 
 This will allow you and other programmers to use your classes by reading the HTML class documentation 
-that can be created with KDoc. &kdevelop; supports the use of KDoc completely by creating the 
+that can be created with KDoc. &tdevelop; supports the use of KDoc completely by creating the 
 KDE-library documentation, also your application frameworks are already documented. To work yourself 
 into the provided code, it would be a good start to read the included documentation online. 
-The following describes what to do to get the API documentation, where &kdevelop; helps you add it 
+The following describes what to do to get the API documentation, where &tdevelop; helps you add it 
 and what kind of special tags KDoc provides.
 </para>
 </sect1>