Additional renaming of kde to tde

9 files changed, 15 insertions, 15 deletions

diff --git a/doc/kommander/credits.docbook b/doc/kommander/credits.docbook
index 95c38541..0b4c90b3 100644
--- a/doc/kommander/credits.docbook
+++ b/doc/kommander/credits.docbook
@@ -38,7 +38,7 @@
 <listitem><para>Developer</para></listitem>
 </varlistentry>
 <varlistentry>
-<term>Rudolf, Michal <email>mrudolf@kdewebdev.org</email></term>
+<term>Rudolf, Michal <email>mrudolf@tdewebdev.org</email></term>
 <listitem><para>Developer</para></listitem>
 </varlistentry>
 </variablelist>
diff --git a/doc/kommander/extending.docbook b/doc/kommander/extending.docbook
index 380fc46e..1adfdc25 100644
--- a/doc/kommander/extending.docbook
+++ b/doc/kommander/extending.docbook
@@ -11,7 +11,7 @@
 <author>
 <firstname>Michal</firstname>
 <surname>Rudolf</surname>
-<affiliation><address><email>mrudolf@kdewebdev.org</email></address></affiliation>
+<affiliation><address><email>mrudolf@tdewebdev.org</email></address></affiliation>
 </author>
 
 <!-- TRANS:ROLES_OF_TRANSLATORS -->
diff --git a/doc/kommander/index.docbook b/doc/kommander/index.docbook
index 71582056..77f8f63f 100644
--- a/doc/kommander/index.docbook
+++ b/doc/kommander/index.docbook
@@ -2,7 +2,7 @@
 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
   <!ENTITY kommander "<application>Kommander</application>">
   <!ENTITY kappname "&kommander;">
-  <!ENTITY package "kdewebdev">
+  <!ENTITY package "tdewebdev">
   <!ENTITY basics SYSTEM "basics.docbook">
   <!ENTITY commands SYSTEM "commands.docbook">
   <!ENTITY parser SYSTEM "parser.docbook">
@@ -53,7 +53,7 @@
 <firstname>Eric</firstname>
 <surname>Laffoon</surname>
 <affiliation>
-<address><email>eric@kdewebdev.org</email></address>
+<address><email>eric@tdewebdev.org</email></address>
 </affiliation>
 </author>
 <author>
@@ -88,7 +88,7 @@ Do NOT change these in the translation. -->
 <!-- Abstract about this handbook -->
 
 <abstract>
-<para>These docs have been partially complete for years, but not always available or easy to find. Since around 2002 little spurts of effort on &kommander; have produced dramtic results. &kommander; is a new approach to development and there have been modifications in approach and features. Consequently much of this documentation is out of date, however still useful due to legacy support. Please refer to our web site at <ulink url="http://kommander.kdewebdev.org">http://kommander.kdewebdev.org</ulink> for up to date information, news on KDE4 development, new tools, plugins, tips and tutorials.</para>
+<para>These docs have been partially complete for years, but not always available or easy to find. Since around 2002 little spurts of effort on &kommander; have produced dramtic results. &kommander; is a new approach to development and there have been modifications in approach and features. Consequently much of this documentation is out of date, however still useful due to legacy support. Please refer to our web site at <ulink url="http://kommander.tdewebdev.org">http://kommander.tdewebdev.org</ulink> for up to date information, news on KDE4 development, new tools, plugins, tips and tutorials.</para>
 <para>
 &kommander; is a set of tools that allow you to create dynamic &GUI; windows that has been used as a front end for command line programs, database front ends, simple program extentions and much more. The best part of it all?  You aren't required to write a single line of code! Okay, that was old text... You can actually use the function browser and even with the new parser write almost none of the code. The inherent difference between &kommander; and other &GUI; scripting tools is that &kommander; doesn't care about how the window gets drawn. &kommander; was designed from the GUI down to the language elements and can embrace multiple languages. &kommander; does not use scripting to draw a window on the screen like other &GUI; scripting tools. As Kommander matures it will expose all it's internals to any scripting language people want to enable. We welcome anyone wishing to enhance support for any scripting language.
 </para>
diff --git a/doc/kommander/installation.docbook b/doc/kommander/installation.docbook
index f91f57ad..b7860caf 100644
--- a/doc/kommander/installation.docbook
+++ b/doc/kommander/installation.docbook
@@ -12,7 +12,7 @@ application -->
 
 &install.intro.documentation;
 
-<para>There is a dedicated homepage for &kommander; at <ulink url="http://kommander.kdewebdev.org">http://kommander.kdewebdev.org</ulink>.
+<para>There is a dedicated homepage for &kommander; at <ulink url="http://kommander.tdewebdev.org">http://kommander.tdewebdev.org</ulink>.
 </para>
 </sect1>
 
@@ -22,7 +22,7 @@ application -->
 <!--
 List any special requirements for your application here. This should include:
 .Libraries or other software that is not included in tdesupport,
-kdelibs, or kdebase.
+tdelibs, or tdebase.
 .Hardware requirements like amount of RAM, disk space, graphics card
 capabilities, screen resolution, special expansion cards, etc.
 .Operating systems the app will run on. If your app is designed only for a
diff --git a/doc/kommander/introduction.docbook b/doc/kommander/introduction.docbook
index 7b40475a..cbe9b324 100644
--- a/doc/kommander/introduction.docbook
+++ b/doc/kommander/introduction.docbook
@@ -125,7 +125,7 @@ extensibility in &quantaplus;.
 
 <para>
 We hope you enjoy &kommander;. Please help us with bug reports and example
-dialogs, as well as any requests you may have. You can join our <ulink url="http://mail.kdewebdev.org/mailman/listinfo/kommander">user list</ulink>
+dialogs, as well as any requests you may have. You can join our <ulink url="http://mail.tdewebdev.org/mailman/listinfo/kommander">user list</ulink>
 for help developing &kommander; applications.
 </para>
 
diff --git a/doc/kommander/parser.docbook b/doc/kommander/parser.docbook
index a008c431..197eb8ff 100644
--- a/doc/kommander/parser.docbook
+++ b/doc/kommander/parser.docbook
@@ -9,7 +9,7 @@
 <othername></othername>
 <surname>Rudolf</surname>
 <affiliation>
-<address><email>mrudolf@kdewebdev.org</email></address>
+<address><email>mrudolf@tdewebdev.org</email></address>
 </affiliation>
 </author>
 <author>
@@ -17,7 +17,7 @@
 <othername></othername>
 <surname>Laffoon</surname>
 <affiliation>
-<address><email>eric@kdewebdev.org</email></address>
+<address><email>eric@tdewebdev.org</email></address>
 </affiliation>
 </author>
 <!-- TRANS:ROLES_OF_TRANSLATORS -->
diff --git a/doc/kommander/q-and-a.docbook b/doc/kommander/q-and-a.docbook
index 2b76331c..945b3d56 100644
--- a/doc/kommander/q-and-a.docbook
+++ b/doc/kommander/q-and-a.docbook
@@ -6,6 +6,6 @@
 </chapterinfo>
 
 <title>Questions and Answers</title>
-<para>The list of Frequently Asked Questions can be found on <ulink url="http://kommander.kdewebdev.org/faq.php">our home page</ulink>.
+<para>The list of Frequently Asked Questions can be found on <ulink url="http://kommander.tdewebdev.org/faq.php">our home page</ulink>.
 </para>
 </chapter>
diff --git a/doc/kommander/translating.docbook b/doc/kommander/translating.docbook
index 15db90bd..15d7def2 100644
--- a/doc/kommander/translating.docbook
+++ b/doc/kommander/translating.docbook
@@ -11,7 +11,7 @@
 <author>
 <firstname>Michal</firstname>
 <surname>Rudolf</surname>
-<affiliation><address><email>mrudolf@kdewebdev.org</email></address></affiliation>
+<affiliation><address><email>mrudolf@tdewebdev.org</email></address></affiliation>
 </author>
 
 <!-- TRANS:ROLES_OF_TRANSLATORS -->
diff --git a/doc/kommander/tutorials.docbook b/doc/kommander/tutorials.docbook
index 095e9a28..0f6fd954 100644
--- a/doc/kommander/tutorials.docbook
+++ b/doc/kommander/tutorials.docbook
@@ -8,7 +8,7 @@
 <firstname>Eric</firstname>
 <surname>Laffoon</surname>
 <affiliation><address>
-<email>eric@kdewebdev.org</email>
+<email>eric@tdewebdev.org</email>
 </address></affiliation>
 </author>
 
@@ -316,7 +316,7 @@ Shows how to use Table widget
 These examples reflect the most recent development state of &kommander;. In its current state &kommander; has few limitations for developing small to medium applications. It certainly is not suitable for building a KWord clone, but for a simple editor, database frontend, GUI for commandline programs or any application in the spirit of Unix/Linux small applications it is a good choice. The examples presented here are intended to show the potential as well as how to work around limitations. There are some useful tricks included in these if you want to do a more capable small application with &kommander;. Remember &kommander; is not intended to do everything, but to do most things. For this concession you should be able to build something in &kommander; faster than other alternatives ad add GUI to scripting languages not otherwise supported in KDE.
 </para>
 <note><para>
-The examples are installed to <command>$KDEDIR/share/apps/kmdr-editor/editor</command>. In case you do not have them there, get from <ulink url="http://kommander.kdewebdev.org">our home page</ulink>, by downloading the latest release.
+The examples are installed to <command>$KDEDIR/share/apps/kmdr-editor/editor</command>. In case you do not have them there, get from <ulink url="http://kommander.tdewebdev.org">our home page</ulink>, by downloading the latest release.
 </para>
 </note>
 
@@ -334,7 +334,7 @@ There is a quick help dialog this editor launches that discusses in depth what i
 <sect2 id="example-key-value">
 <title>kevaluecombo.kmdr</title>
 <para>
-&kommander; can be used with databases and has an optional <ulink url="http://kommander.kdewebdev.org/releases.php#plugins">database plugin</ulink>. One shortcoming is not being able to store key/value pairs in the ComboBox. An ingenious trick was realized for this. It requires only that the content of the ComboBox not be changed unless it is done using the arrays that go with it. As this is commonly used with SQL in small data sets it's quite fast even to reload the whole Combobox. The inherent problem is that &kommander; does not have internally indexed arrays by default. This is compounded by the fact that to accommodate shell commands that return lines separated by newlines &kommander;'s array functions will load what is effectively an array of keys. Such an array can only be accessed with a foreach loop. This is the reason new indexed array functions were added. It is important to remember that these arrays are not self maintaining, but their insert and delete functions will help you. 
+&kommander; can be used with databases and has an optional <ulink url="http://kommander.tdewebdev.org/releases.php#plugins">database plugin</ulink>. One shortcoming is not being able to store key/value pairs in the ComboBox. An ingenious trick was realized for this. It requires only that the content of the ComboBox not be changed unless it is done using the arrays that go with it. As this is commonly used with SQL in small data sets it's quite fast even to reload the whole Combobox. The inherent problem is that &kommander; does not have internally indexed arrays by default. This is compounded by the fact that to accommodate shell commands that return lines separated by newlines &kommander;'s array functions will load what is effectively an array of keys. Such an array can only be accessed with a foreach loop. This is the reason new indexed array functions were added. It is important to remember that these arrays are not self maintaining, but their insert and delete functions will help you. 
 </para>
 <para>
 Getting back to the ComboBox, it will return selected text, but it also will return the current index. It does rigidly maintain a contiguous zero based array. That's the key. We loop through a data set with a zero based index counter and create two arrays, as &kommander; also cannot create arrays of arrays. It can however use an array value to represent a key just like any value could. .If you look at the included dialog the code actually managing this is in <quote>ScriptObject36</quote>. We will extract the key code here.