Rename a number of classes to enhance compatibility with KDE4

2 files changed, 4 insertions, 4 deletions

diff --git a/doc/kommander/tutorials.docbook b/doc/kommander/tutorials.docbook
index e4fd5054..ba051e78 100644
--- a/doc/kommander/tutorials.docbook
+++ b/doc/kommander/tutorials.docbook
@@ -325,7 +325,7 @@ The examples are installed to <command>$TDEDIR/share/apps/kmdr-editor/editor</co
 <para>
 The little dialog that grew into a Mainwindow. As &kommander; does not have a native MainWindow widget it has been assumed it only does dialogs. In fact only dialogs are officially supported... but you can run MainWindows in &kommander;. This is an example editor. If you want to create a MainWindow application in &kommander; just open Qt Designer and make one, save it and rename the *.ui file to a *.kmdr file. Now open it in &kommander; and do what you would do normally.
 </para>
-<note><para>As of this writing what is known not to work on the &kommander; side is the settings read and write. There is no Initialize or Destroy section as there is no &kommander; Text, however there are signals for this on the window, so the functionality is intact. On the MainWindow side it is not possible to talk to any actions via DCOP as these are QActions from Designer and KActions are not derived from QActions in KDE 3.x. This means a DCOP call to list actions or set states will not work. It is also not possible to talk to the Statusbar. Also submenus on the menubar and dropdown actions on the Toolbar will not work. Even though this is not a &kommander; widget, or officicially supported, it seems suitable for many small application uses.</para></note>
+<note><para>As of this writing what is known not to work on the &kommander; side is the settings read and write. There is no Initialize or Destroy section as there is no &kommander; Text, however there are signals for this on the window, so the functionality is intact. On the MainWindow side it is not possible to talk to any actions via DCOP as these are QActions from Designer and TDEActions are not derived from QActions in KDE 3.x. This means a DCOP call to list actions or set states will not work. It is also not possible to talk to the Statusbar. Also submenus on the menubar and dropdown actions on the Toolbar will not work. Even though this is not a &kommander; widget, or officicially supported, it seems suitable for many small application uses.</para></note>
 <para>
 There is a quick help dialog this editor launches that discusses in depth what is happening inside.
 </para>
diff --git a/doc/kommander/widgets.docbook b/doc/kommander/widgets.docbook
index fa187cfc..1596d25e 100644
--- a/doc/kommander/widgets.docbook
+++ b/doc/kommander/widgets.docbook
@@ -132,7 +132,7 @@ A ListBox has only one state, default.
 The widget text for a ListBox is the items contained in the ListBox.  @selectedWidgetText will return only the items that are currently selected.
 </para>
 <para>
-See the KListBox documentation to learn more about it.
+See the TDEListBox documentation to learn more about it.
 </para>
 </listitem>
 </varlistentry>
@@ -172,7 +172,7 @@ TreeWidget
 A widget that provides a list in the form of a tree structure. You can add child items and multi-column data. The current limitation is that you cannot modify columns. To add a child node use <quote>/</quote> as a separator. To add column data use the escaped tab <quote>\t</quote> character between columns.
 </para>
 <para>
-See the KListView documentation to learn more about it.
+See the TDEListView documentation to learn more about it.
 </para>
 
 </listitem>
@@ -316,7 +316,7 @@ RadioButton has 2 states checked and unchecked.
 There is no widget text associated with a RadioButton.
 </para>
 <para>
-See the KRadioButton documentation to learn more about it.
+See the TDERadioButton documentation to learn more about it.
 </para>
 </listitem>
 </varlistentry>