Additional renaming of kde to tde

1 files changed, 13 insertions, 13 deletions

diff --git a/doc/api/HowToAddApplicationTemplates.dox b/doc/api/HowToAddApplicationTemplates.dox
index 7eec80c7..b948c934 100644
--- a/doc/api/HowToAddApplicationTemplates.dox
+++ b/doc/api/HowToAddApplicationTemplates.dox
@@ -6,7 +6,7 @@
 Project templates provide the developer with a basic application framework.
 This is necessary for rapid application development (RAD) and makes it even possible
 for an inexperienced 3rd party developer to create standard conforming
-applications like kedit as well as plugins for example for kdevelop or noatun.\n\n
+applications like kedit as well as plugins for example for tdevelop or noatun.\n\n
 \ref templates_1\n
     - \ref templates_1_1
     - \ref templates_1_2
@@ -36,7 +36,7 @@ Create a directory <code>template-khello</code> with the files
     - template-khello/app.cpp
     - template-khello/app.h
     - template-khello/app.desktop
-    - template-khello/app.kdevelop
+    - template-khello/app.tdevelop
     - template-khello/appui.rc
     - template-khello/khello
     - template-khello/main.cpp
@@ -64,7 +64,7 @@ wizard will replace:
     - \%{YEAR} ........ by the year
     .
 </pre></code>
-All this can be found in <code>$KDEDIR/share/apps/kdevappwizard/template-common/kdevelop.pm</code>.
+All this can be found in <code>$KDEDIR/share/apps/kdevappwizard/template-common/tdevelop.pm</code>.
 \subsubsection templates_1_2a I.2.1. The Source Files
 
 The files <code>template-khello/app.cpp, template-khello/app.h</code> and
@@ -117,7 +117,7 @@ This file will be copied to the <code>$PROJECTDIR/src/</code>.
 
 The following script is used to install the template and replaces all
 variables by the corresponding value. The result is a hopefully working
-kdevelop project!
+tdevelop project!
 \verbinclude khello/script
 <br>
 \note There are several application templates which use some identical
@@ -155,7 +155,7 @@ if [ ! -e "${newdir}/template-common" ]; then ln -s "${kde_prefix}/share/apps/kd
 # install now
 cp -R --target-directory "$newdir" template-khello
 # the file template-khello/khello must go to the "templates" directory that
-# kdevelop knows that it exists
+# tdevelop knows that it exists
 mv "$newdir/template-khello/khello" "$newdir/templates/"
 echo "done"
 \endcode
@@ -164,9 +164,9 @@ echo "done"
 
 \section templates_3 III. How To Add The Template To KDevelop CVS HEAD
 
-This section is for kdevelop developers only. Most probably you don't have to read this!.\n
-Move the directory <code>"template-khello"</code> to <code>kdevelop/languages/cpp/app_templates/</code>
-and then add the following files in <code>kdevelop/languages/cpp/app_templates/template-khello/</code>
+This section is for tdevelop developers only. Most probably you don't have to read this!.\n
+Move the directory <code>"template-khello"</code> to <code>tdevelop/languages/cpp/app_templates/</code>
+and then add the following files in <code>tdevelop/languages/cpp/app_templates/template-khello/</code>
 (in this example the language is c++ if you use other language replace cpp with the language name):
     - <code>".kdev_ignore"</code> is an empty file. It prevents KDevelop's
     C++-parser from parsing the C++ template files. This is necessary because the template files are just code templates and not real code (yet).
@@ -179,9 +179,9 @@ script.local
     - <code>"Makefile.am"</code> looks like this:
     \verbinclude khello/Makefile.am
     .
-Finally add <code>"template-khello"</code> to "SUBDIRS = " in <code>kdevelop/languages/cpp/app_templates/Makefile.am</code>.\n
+Finally add <code>"template-khello"</code> to "SUBDIRS = " in <code>tdevelop/languages/cpp/app_templates/Makefile.am</code>.\n
 \attention Please test your template whether it installs and behaves correctly!
-Test, test and test again! It works? Well - now talk to the kdevelop guys so
+Test, test and test again! It works? Well - now talk to the tdevelop guys so
 that they know what's going on and probably you may commit. ;)
 
 \section templates_4 IV. Changes to the template system (VERY IMPORTANT)
@@ -192,14 +192,14 @@ information from the script file will need to be moved into the ini file.
 The example is as follows:
 \code
 install(
-"${src}/template-chello/app.kdevelop","${dest}/${APPNAMELC}.kdevelop" );
+"${src}/template-chello/app.tdevelop","${dest}/${APPNAMELC}.tdevelop" );
 \endcode
 becomes
 \code
 [PROJECT]
 Type=install
-Source=%{src}/template-chello/app.kdevelop
-Dest=%{dest}/%{APPNAMELC}.kdevelop
+Source=%{src}/template-chello/app.tdevelop
+Dest=%{dest}/%{APPNAMELC}.tdevelop
 \endcode
 
 Things like <code>installIncAdmin();</code> and <code>installGNU();</code> now involve unpacking