1 files changed, 12 insertions, 12 deletions
diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook
index f5af2265..c1ed3ba9 100644
--- a/doc/kde_app_devel/index.docbook
+++ b/doc/kde_app_devel/index.docbook
@@ -749,7 +749,7 @@ the compilation phase.
    -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -O2 -fno-exceptions -fno-check-new 
    -c -o kscribble.o `test -f 'kscribble.cpp' || echo '/home/caleb/kscribble/src/'`kscribble.cpp
 30 kscribble.cpp: In member function `void KScribble::setupActions()'
-31 kscribble.cpp:107: warning: unused variable `KAction*custom'
+31 kscribble.cpp:107: warning: unused variable `TDEAction*custom'
 32 /usr/lib/qt/bin/moc /home/caleb/kscribble/src/kscribbleview.h -o kscribbleview.moc
 33 source='kscribbleview.cpp' object='kscribbleview.o' libtool=no \
 34 depfile='.deps/kscribbleview.Po' tmpdepfile='.deps/kscribbleview.TPo' \
@@ -912,14 +912,14 @@ added some KDE methods that set program and author information for this applicat
 Let's have a look at the constructor and see how this instance is called
 <programlisting>
 1  KScribble::KScribble()
-2      : KMainWindow( 0, "KScribble" ),
+2      : TDEMainWindow( 0, "KScribble" ),
 3        m_view(new KScribbleView(this)),
 4        m_printer(0)
 5  {
 6      // accept dnd
 7      setAcceptDrops(true);
 8  
-9      // tell the KMainWindow that this is indeed the main widget
+9      // tell the TDEMainWindow that this is indeed the main widget
 10     setCentralWidget(m_view);
 11 
 12     // then, setup our actions
@@ -938,7 +938,7 @@ Let's have a look at the constructor and see how this instance is called
 </programlisting>
 </para>
 <para>
-Notice that <classname>KScribble</classname> inherits the <classname>KMainWindow</classname> class - a 
+Notice that <classname>KScribble</classname> inherits the <classname>TDEMainWindow</classname> class - a 
 commonly used base class for TDE applications.  We initialize a class called <classname>KScribbleView</classname>
 as our central widget, create a <classname>KStatusBar</classname> via the <methodname>statusBar()</methodname>
 method (line 16), and connect some signals and slots together.
@@ -1123,7 +1123,7 @@ The KDE libraries were invented to make designing applications for the K Desktop
 and capable of more functionality than what Qt alone is offering. The tdeui library offers: 
 <orderedlist>
 <listitem><para>
-KListView: a more powerful version of <classname>QListView</classname>
+TDEListView: a more powerful version of <classname>QListView</classname>
 </para></listitem>
 <listitem><para>
 KIconView: a graphical viewer of icon files
@@ -1164,9 +1164,9 @@ icons or provide quick access methods like combos to select values.
 <sect1 id="c5s2">
 <title>How does it work?</title>
 <para>
-Our application inherits the <classname>KMainWindow</classname> class, which automatically handles creating
+Our application inherits the <classname>TDEMainWindow</classname> class, which automatically handles creating
 a menu bar and tool bars for us.  In the <methodname>KScribble::setupActions()</methodname> method there is
-a call to <methodname>KMainWindow::createGUI()</methodname>.  This method loads a resource file, in this
+a call to <methodname>TDEMainWindow::createGUI()</methodname>.  This method loads a resource file, in this
 case kscribbleui.rc, to initialize menus at startup.  Note that kscribbleui.rc is listed as one of the
 project files in the Automake Manager.  Opening that file up reveals this:
 <programlisting>
@@ -1192,7 +1192,7 @@ a large number of <methodname>insertItem()</methodname> methods which allow you
 menu bar.
 </para>
 <para>
-<classname>KMainWindow</classname>'s methods <methodname>statusBar()</methodname> and <methodname>
+<classname>TDEMainWindow</classname>'s methods <methodname>statusBar()</methodname> and <methodname>
 toolBar()</methodname> will also provide you with applicable widgets.
 </para>
 </sect1>
@@ -1202,7 +1202,7 @@ toolBar()</methodname> will also provide you with applicable widgets.
 A very professional thing you should always add to your application are keyboard accelerators.
 Those are mainly used by experienced users that want to work fast with their applications and 
 are willing to learn shortcuts. For this, the KDE libraries provide the class <classname>
-KAction</classname>, which provides the keyboard accelerator keys and access to global configured
+TDEAction</classname>, which provides the keyboard accelerator keys and access to global configured
 standard keyboard accelerators. 
 </para>
 <para>
@@ -1249,7 +1249,7 @@ Within the application, those are:</para>
 <para>
 Additionally, the application should provide means to access a HTML-based online manual directly
 using the standard help key F1.  This context based help system is provided automatically through the
-<classname>KMainWindow</classname> class, though as the author you must provide the content.
+<classname>TDEMainWindow</classname> class, though as the author you must provide the content.
 </para>
 <para>
 As &tdevelop; also offers all types of help as well as the KDE framework generated by the 
@@ -1273,7 +1273,7 @@ as possible because toolbars can be configured to display their contents in vari
 either displaying the button, button with text on the right, button with text below, text only. 
 This possibility should be made configurable by the user, but isn't a must-be. The text is shown
 as a tool-tip anyway and a toolbar usually consists of buttons and other widgets like lineedits and 
-combo boxes. For a complete reference, see the <classname>KToolBar</classname> class reference located 
+combo boxes. For a complete reference, see the <classname>TDEToolBar</classname> class reference located 
 in the tdeui library. 
 </para>
 <para>
@@ -1291,7 +1291,7 @@ provided by Qt. An example of that would be:
 <sect1 id="c8s3">
 <title>Extending the Statusbar</title>
 <para>
-As the applications that inherit <classname>KMainWindow</classname> contain a statusbar as well, 
+As the applications that inherit <classname>TDEMainWindow</classname> contain a statusbar as well, 
 it also offers a set of statusbar messages already for all menu and toolbar items. A statusbar 
 help message is a short message that extends the meaning of a tool-tip or can be seen as a replacement 
 for a tool-tip over menubar items and is (as the name suggests) displayed in the statusbar when the user