Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* versionr14.1.1

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
(cherry picked from commit d2728dd8dbad48f045a5eca1899924df15633a89)

5 files changed, 61 insertions, 61 deletions

diff --git a/doc/api/HowToAddPlugins.dox b/doc/api/HowToAddPlugins.dox
index 3f9d1b20..e40840a8 100644
--- a/doc/api/HowToAddPlugins.dox
+++ b/doc/api/HowToAddPlugins.dox
@@ -85,7 +85,7 @@ Your part must be derived from <code>KDevPlugin</code>.
   - KDevPlugin takes two arguments:
     - 1) A <i>parent</i> argument. This also comes from
 	  <code>createPartObject()</code>.
-	- 2) A <i>name</i>, which in turn is given to the <code>QObject</code>
+	- 2) A <i>name</i>, which in turn is given to the <code>TQObject</code>
 	  constructor.
 	.
   .
@@ -134,7 +134,7 @@ rooted in the <code>dom</code> document node.
 For example, the <code>autoproject</code> part uses the statement
 
 <code><pre>
-    QString cflags = DomUtil::readEntry( *part->document(),
+    TQString cflags = DomUtil::readEntry( *part->document(),
                                          "/kdevautoproject/cflags" );
 </pre></code>
 
@@ -181,7 +181,7 @@ void GDBBreakpointWidget::savePartialProjectSession(QDomElement* el)
     {
         BreakpointTableRow* btr = (BreakpointTableRow *) m_table->item(row, Control);
         Breakpoint* bp = btr->breakpoint();
-        QDomElement breakpointEl = domDoc.createElement("breakpoint"+QString::number(row));
+        QDomElement breakpointEl = domDoc.createElement("breakpoint"+TQString::number(row));
         breakpointEl.setAttribute("type", bp->type());
         breakpointEl.setAttribute("location", bp->location(false));
         breakpointEl.setAttribute("enabled", bp->isEnabled());
diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox
index 9ef228e2..78091009 100644
--- a/doc/api/HowToAddProgrammingLanguages.dox
+++ b/doc/api/HowToAddProgrammingLanguages.dox
@@ -71,10 +71,10 @@ Language support can offer additional features:
 
 \subsection sectionAttributeMethodWizard Attribute/Method wizard
   - add method dialog: (See <code>cpp</code> or <code>java</code>)
-    - <code>virtual void addMethod(const QString &className);</code>
+    - <code>virtual void addMethod(const TQString &className);</code>
     .
   - add attribute dialog: (See <code>cpp</code> or <code>java</code>)
-    - <code>virtual void addAttribute(const QString &className);</code>
+    - <code>virtual void addAttribute(const TQString &className);</code>
     .
   .
 
@@ -82,8 +82,8 @@ Language support can offer additional features:
 
 If there is a Qt bindings for your language and there is a possibility
 to use QtDesigner ui files, you could implement ui subclassing feature:
-  - <code>virtual QStringList subclassWidget(const QString& formName);</code>
-  - <code>virtual QStringList updateWidget(const QString& formName, const QString&
+  - <code>virtual QStringList subclassWidget(const TQString& formName);</code>
+  - <code>virtual QStringList updateWidget(const TQString& formName, const TQString&
         fileName);</code>
   .
 
diff --git a/doc/api/PropEditor.dox b/doc/api/PropEditor.dox
index 40ce4261..a0bd38a5 100644
--- a/doc/api/PropEditor.dox
+++ b/doc/api/PropEditor.dox
@@ -73,7 +73,7 @@ A simple example on how to create a property editor and use it with one property
     list->addProperty("My Group", new Property(String, "Second Property",
         "This is my second property", "Hello"));
     list->addProperty(new Property(Color, "Third Property",
-        "This is my third property", QColor("green")));
+        "This is my third property", TQColor("green")));
         
     m_editor->populateProperties(*list);
 \endcode
@@ -88,7 +88,7 @@ More advanced example with property accessors and list intersection:
     list->addProperty("My Group", new Property(String, "Second Property",
         "This is my second property", "Hello"));
     list->addProperty(new Property(Color, "Third Property",
-        "This is my third property", QColor("green")));
+        "This is my third property", TQColor("green")));
 
     PropertyList *list2 = new PropertyList;
     list2->addProperty("My Group", new Property(Integer, "First Property",
diff --git a/doc/kdearch/index.docbook b/doc/kdearch/index.docbook
index 97dee33d..b75978ff 100644
--- a/doc/kdearch/index.docbook
+++ b/doc/kdearch/index.docbook
@@ -337,7 +337,7 @@ Pixmap effects like gradients and patterns.
 
 <listitem><formalpara><title><ulink url="kdeapi:tdeui/KPixmapIO">KPixmapIO</ulink></title>
 <para>
-Fast <classname>QImage</classname> to <classname>QPixmap</classname> conversion.
+Fast <classname>TQImage</classname> to <classname>QPixmap</classname> conversion.
 </para>
 </formalpara></listitem>
 
@@ -684,7 +684,7 @@ The central graphics class for 2D painting with Qt is
 draw on a
 <ulink url="kdeapi:qt/QPaintDevice">QPaintDevice</ulink>.
 There are three possible paint devices implemented: One is 
-<ulink url="kdeapi:qt/QWidget">QWidget</ulink>
+<ulink url="kdeapi:qt/TQWidget">TQWidget</ulink>
 which represents a widget on the screen. The second is 
 <ulink url="kdeapi:qt/QPrinter">QPrinter</ulink> which
 represents a printer and produces Postscript output. The third it
@@ -967,11 +967,11 @@ Brushes can be constructed in four different ways:
 patterns shown below.</para>
 </listitem>
 <listitem>
-<para>QBrush::QBrush(const QColor &amp;, BrushStyle) - This creates a colored brush
+<para>QBrush::QBrush(const TQColor &amp;, BrushStyle) - This creates a colored brush
 with one of the patterns shown below.</para>
 </listitem>
 <listitem>
-<para>QBrush::QBrush(const QColor &amp;, const QPixmap) - This creates a colored
+<para>QBrush::QBrush(const TQColor &amp;, const QPixmap) - This creates a colored
 brush with the custom pattern you give as second parameter.</para>
 </listitem>
 </itemizedlist>
@@ -1000,7 +1000,7 @@ QPainter::setBrushOrigin().
 <para>
 Colors play a role both when stroking curves and when filling shapes. In Qt, 
 colors are represented by the class 
-<ulink url="kdeapi:qt/QColor">QColor</ulink>. Qt does not support 
+<ulink url="kdeapi:qt/TQColor">TQColor</ulink>. Qt does not support 
 advanced graphics features like ICC color profiles and color correction. Colors 
 are usually constructed by specifying their red, green and blue components, as 
 the RGB model is the way pixels are composed of on a monitor. 
@@ -1104,14 +1104,14 @@ to avoid flicker.
 </para>
 
 <para>
-In contrast, <ulink url="kdeapi:qt/QImage">QImage</ulink> objects 
+In contrast, <ulink url="kdeapi:qt/TQImage">TQImage</ulink> objects 
 live on the client side. Their emphasis in on providing direct access to the
 pixels of the image. This makes them of use for image manipulation, and things
-like loading and saving to disk (QPixmap's load() method takes QImage as 
+like loading and saving to disk (QPixmap's load() method takes TQImage as 
 intermediate step). On the other hand, painting an image on a widget is a
 relatively expensive operation, as it implies a transfer to the X server,
 which can take some time, especially for large images and for remote servers.
-Depending on the color depth, the conversion from QImage to QPixmap may also 
+Depending on the color depth, the conversion from TQImage to QPixmap may also 
 require dithering.
 </para>
 
@@ -1123,7 +1123,7 @@ require dithering.
 
 <para>
 Text can be drawn with one of the overloaded variants of the method 
-QPainter::drawText(). These draw a QString either at a given point or in a given
+QPainter::drawText(). These draw a TQString either at a given point or in a given
 rectangle, using the font set by QPainter::setFont(). There is also a parameter
 which takes an ORed combination of some flags from the enums
 <ulink url="kdeapi:qt/Qt#AlignmentFlags-enum">Qt::AlignmentFlags</ulink>
@@ -1658,7 +1658,7 @@ ask the client's factory for it:
 <programlisting>
 void MainWindow::popupRequested()
 {
-    QWidget *w = factory()->container("context_popup", this);
+    TQWidget *w = factory()->container("context_popup", this);
     QPopupMenu *popup = static_cast&lt;QPopupMenu *&gt;(w);
     popup->exec(QCursor::pos());
 }
@@ -1929,13 +1929,13 @@ X-TDE-ServiceType=TDevelop/Part
 Name=TDevelop Part
 
 [PropertyDef::X-TDevelop-Scope]
-Type=QString
+Type=TQString
 
 [PropertyDef::X-TDevelop-ProgrammingLanguages]
 Type=QStringList
 
 [PropertyDef::X-TDevelop-Args]
-Type=QString
+Type=TQString
 </programlisting>
 
 <para>
@@ -2032,11 +2032,11 @@ load the library and get a pointer to its factory object:
 
 <programlisting>
 KService *service = ...
-QString libName = QFile::encodeName(service->library());
+TQString libName = QFile::encodeName(service->library());
 KLibFactory *factory = KLibLoader::self()->factory(libName);
 if (!factory) {
-    QString name = service->name();
-    QString errorMessage = KLibLoader::self()->lastErrorMessage();
+    TQString name = service->name();
+    TQString errorMessage = KLibLoader::self()->lastErrorMessage();
     KMessageBox::error(0, i18n("There was an error loading service %1.\n"
                                "The diagnostics from libtool is:\n%2")
                           .arg(name).arg(errorMessage);
@@ -2054,7 +2054,7 @@ its create() method:
 <programlisting>
 if (factory->inherits("KParts::Factory")) {
     KParts::Factory *partFactory = static_cast&lt;KParts::Factory*&gt;(factory);
-    QObject *obj = partFactory->createPart(parentWidget, widgetName, 
+    TQObject *obj = partFactory->createPart(parentWidget, widgetName, 
                                            parent, name, "KParts::ReadOnlyPart");
     ...
 } else {
@@ -2142,7 +2142,7 @@ class:
 DCOPClient *client = kapp->dcopClient();
 client->attach();
 if (!client->isApplicationRegistered("tdeio_uiserver")) {
-    QString error;
+    TQString error;
     if (TDEApplication::startServiceByName("tdeio_uiserver", QStringList(), &amp;error))
         cout &lt;&lt; "Starting kioserver failed with message " &lt;&lt; error &lt;&lt; endl;
 }
@@ -2176,7 +2176,7 @@ the file name of its desktop file as argument, i.e. in this case
 <para>
 All these calls take a list of URLs as a second argument, which is given
 to the service on the command line. The third argument is a pointer to a
-<classname>QString</classname>. If starting the service fails, this argument
+<classname>TQString</classname>. If starting the service fails, this argument
 is set to a translated error message.
 </para>
 
@@ -2385,7 +2385,7 @@ contents of a local file. For remote files, there is a further possibility:
 
 <programlisting>
 KURL url("http://developer.kde.org/favicon.ico");
-QString type = TDEIO::NetAccess::mimetype(url);
+TQString type = TDEIO::NetAccess::mimetype(url);
 if (type == KMimeType::defaultMimeType())
     cout &lt;&lt; "Could not find out type" &lt;&lt; endl;
 else
@@ -2514,7 +2514,7 @@ and returns the associated icon.
 
 <programlisting>
 KURL url("ftp://ftp.kde.org/pub/incoming/wibble.c");
-QString icon = KMimeType::iconForURL(url);
+TQString icon = KMimeType::iconForURL(url);
 </programlisting>
 
 <para>
@@ -2652,7 +2652,7 @@ Renames a file.
 </para></listitem>
 </varlistentry>
 
-<varlistentry><term>TDEIO::symlink(const QString &amp;target, const KURL &amp;dest, 
+<varlistentry><term>TDEIO::symlink(const TQString &amp;target, const KURL &amp;dest, 
                                  bool overwrite, bool showProgressInfo)</term>
 <listitem><para>
 Creates a symbolic link.
@@ -2892,7 +2892,7 @@ files regardless of their location is the following code snippet:
 <programlisting>
 KURL url;
 url = ...;
-QString tempFile;
+TQString tempFile;
 if (TDEIO::NetAccess::download(url, tempFile) {
     // load the file with the name tempFile
     TDEIO::NetAccess::removeTempFile(tempFile);
@@ -2948,12 +2948,12 @@ void FooClass::printModifiedDate()
 
 void FooClass::transferResult(TDEIO::Job *job)
 {
-    QString mimetype;
+    TQString mimetype;
     if (job->error())
         job->showErrorDialog();
     else {
         TDEIO::TransferJob *transferJob = (TDEIO::TransferJob*) job;
-        QString modified = transferJob->queryMetaData("modified");
+        TQString modified = transferJob->queryMetaData("modified");
         cout &lt;&lt; "Last modified: " &lt;&lt; modified &lt;&lt; endl;
 }
 </programlisting>
@@ -3193,7 +3193,7 @@ or not (i.e. the default implementation returns an error).
 <listitem><para>copy(const KURL &amp;url, const KURL &amp;dest, int permissions, bool overwrite)</para></listitem></varlistentry>
 
 <varlistentry><term>Creates a symbolic link.</term>
-<listitem><para>void symlink(const QString &amp;target, const KURL &amp;dest, bool overwrite)</para></listitem></varlistentry>
+<listitem><para>void symlink(const TQString &amp;target, const KURL &amp;dest, bool overwrite)</para></listitem></varlistentry>
 
 </variablelist>
 
diff --git a/doc/tde_app_devel/index.docbook b/doc/tde_app_devel/index.docbook
index 24b3b005..4ab2cd22 100644
--- a/doc/tde_app_devel/index.docbook
+++ b/doc/tde_app_devel/index.docbook
@@ -305,14 +305,14 @@ But what about the <methodname>show()</methodname> method? Now, you see that lik
 This shows you a lot of other widgets that are inherited by <classname>QPushButton</classname>, 
 which we'll use later to explain the signal/slot mechanism. Anyway, the <methodname>show()</methodname> 
 method is not listed, therefore, it must be a method that is provided by inheritance as well. The class 
-that <classname>QButton</classname> inherits is <classname>QWidget</classname>. Just follow the link
-again, and you will see a whole bunch of methods that the QWidget class provides; including 
+that <classname>QButton</classname> inherits is <classname>TQWidget</classname>. Just follow the link
+again, and you will see a whole bunch of methods that the TQWidget class provides; including 
 the <methodname>show()</methodname> method. Now we understand what was done in the sample with the button: 
 <orderedlist>
 <listitem><para>Create an instance of <classname>QPushButton</classname>, use the second constructor to set the button text</para></listitem>
 <listitem><para>Resize the widget to its contents</para></listitem>
 <listitem><para>Set the widget as the main widget of the <classname>QApplication</classname> instance a</para></listitem>
-<listitem><para>Tell the widget to display itself on the screen by calling <methodname>show()</methodname>, an inherited method from <classname>QWidget</classname></para></listitem>
+<listitem><para>Tell the widget to display itself on the screen by calling <methodname>show()</methodname>, an inherited method from <classname>TQWidget</classname></para></listitem>
 </orderedlist>
 </para>
 <para>
@@ -327,7 +327,7 @@ user events.
 <note><para>
 For already advanced users: The button has no parent declared in the constructor, therefore it
 is a top-level widget alone and runs in a local event loop which doesn't need to wait for the main
-event loop.  See the QWidget class documentation and The TDE Library Reference Guide</para>
+event loop.  See the TQWidget class documentation and The TDE Library Reference Guide</para>
 </note> 
 
 </sect3>
@@ -352,7 +352,7 @@ provide methods that detect actions and methods that do something as a reaction
 The Window system therefore sends all interaction events to the according application. The 
 <classname>QApplication</classname> then sends them to the active window as a <classname>QEvent</classname>
 and the widgets themselves have to decide what to do with them. A widget receives the event and processes
-<methodname>QWidget::event(QEvent*)</methodname>, which then decides which event has been executed
+<methodname>TQWidget::event(QEvent*)</methodname>, which then decides which event has been executed
 and how to react; <methodname>event()</methodname> is therefore the main event handler. Then, 
 the <methodname>event()</methodname> method passes the event to so-called event filters 
 that determine what happened and what to do with the event. If no filter signs responsible for the 
@@ -405,9 +405,9 @@ Window events containing the widget</para>
 </para>
 <para>
 Note that all event functions are virtual and protected; therefore you can re-implement the events 
-that you need in your own widgets and specify how your widget has to react. <classname>QWidget</classname>
+that you need in your own widgets and specify how your widget has to react. <classname>TQWidget</classname>
 also contains some other virtual methods that can be useful in your programs; anyway, it is sufficient
-to know about <classname>QWidget</classname> very well. 
+to know about <classname>TQWidget</classname> very well. 
 </para>
 </sect2>
 <sect2 id="c1s2s4">
@@ -423,7 +423,7 @@ some things about this mechanism:
 <itemizedlist>
 <listitem><para>
 the class declaration of a class using signals/slots has to contain the TQ_OBJECT macro at the beginning
-(without a semicolon); and have to be derved from the <classname>QObject</classname> class
+(without a semicolon); and have to be derved from the <classname>TQObject</classname> class
 </para></listitem>
 <listitem><para>
 a signal can be emitted by the keyword emit, e.g. emit signal(parameters); from within any member function
@@ -445,9 +445,9 @@ implementation (which is not necessary to know).  The output files of moc are co
 </itemizedlist>
 </para>
 <para>
-Another way to use signals without deriving from <classname>QObject</classname> is to use the 
+Another way to use signals without deriving from <classname>TQObject</classname> is to use the 
 <classname>QSignal</classname> class- see the reference documentation for more information and example
-usage. In the following, we assume you're deriving from <classname>QObject</classname>. 
+usage. In the following, we assume you're deriving from <classname>TQObject</classname>. 
 </para>
 <para>
 This way, your class is able to send signals anywhere and to provide slots that signals can connect 
@@ -457,7 +457,7 @@ as normal methods during implementation.
 </para>
 <para>
 Now, to connect a signal to a slot, you have to use the <methodname>connect()</methodname> methods that 
-are provided by <classname>QObject</classname> or, where available, special methods that objects provide 
+are provided by <classname>TQObject</classname> or, where available, special methods that objects provide 
 to set the connection for a certain signal. 
 </para>
 
@@ -479,7 +479,7 @@ hello.resize( 100, 30 );
 
 a.setMainWidget( &amp;hello );
 
-QObject::connect(&amp;hello, SIGNAL( clicked() ), &amp;a, SLOT( quit() ));
+TQObject::connect(&amp;hello, SIGNAL( clicked() ), &amp;a, SLOT( quit() ));
 
 hello.show();
 return a.exec();
@@ -489,14 +489,14 @@ return a.exec();
 <para>
 You see, the only addition to give the button more interaction is to use a <methodname>connect()
 </methodname> method: <methodname>connect(&amp;hello, SIGNAL( clicked() ), &amp;a, SLOT( quit() ))</methodname>;
-is all you have to add. What is the meaning now? The class declaration of QObject says about the 
+is all you have to add. What is the meaning now? The class declaration of TQObject says about the 
 <methodname>connect()</methodname> method: 
 </para>
 <para><methodname>
-bool connect ( const QObject * sender, const char * signal, const QObject * receiver, const char * member ) 
+bool connect ( const TQObject * sender, const char * signal, const TQObject * receiver, const char * member ) 
 </methodname></para>
 <para>
-This means you have to specify a <classname>QObject</classname> instance pointer that is the sender 
+This means you have to specify a <classname>TQObject</classname> instance pointer that is the sender 
 of the signal, meaning that it can emit this signal as first parameter; then you have to specify the signal 
 that you want to connect to. The last two parameters are the receiver object that provides a slot, followed 
 by the member function which actually is the slot that will be executed on signal emission. 
@@ -573,7 +573,7 @@ hello.resize( 100, 30 );
 
 a.setTopWidget( &amp;hello );
 
-QObject::connect(&amp;hello, SIGNAL( clicked() ), &amp;a, SLOT( quit() ));
+TQObject::connect(&amp;hello, SIGNAL( clicked() ), &amp;a, SLOT( quit() ));
 
 hello.show();
 return a.exec();
@@ -595,7 +595,7 @@ mentioned before and see the effects.
 </para>
 <para>
 What you should have looked into additionally until now is the reference documentation for Qt, 
-especially the <classname>QApplication</classname>, <classname>QWidget</classname> and <classname>QObject
+especially the <classname>QApplication</classname>, <classname>TQWidget</classname> and <classname>TQObject
 </classname> class and the tdecore library documentation for the <classname>TDEApplication</classname> class. 
 The <ulink url="developer.kde.org/documentation/library/libraryref.html">TDE Library Reference handbook</ulink> 
 also covers a complete description about the invocation of the <classname>QApplication</classname> and 
@@ -924,10 +924,10 @@ Let's have a look at the constructor and see how this instance is called
 16     statusBar()->show();
 17 
 18     // allow the view to change the statusbar and caption
-19     connect(m_view, SIGNAL(signalChangeStatusbar(const QString&amp;)),
-20             this,   SLOT(changeStatusbar(const QString&amp;)));
-21     connect(m_view, SIGNAL(signalChangeCaption(const QString&amp;)),
-22             this,   SLOT(changeCaption(const QString&amp;)));
+19     connect(m_view, SIGNAL(signalChangeStatusbar(const TQString&amp;)),
+20             this,   SLOT(changeStatusbar(const TQString&amp;)));
+21     connect(m_view, SIGNAL(signalChangeCaption(const TQString&amp;)),
+22             this,   SLOT(changeCaption(const TQString&amp;)));
 23
 24  }
 </programlisting>
@@ -1011,10 +1011,10 @@ a joy if you know how to exploit it's capabilities- inheritance, information hid
 already existing code. 
 </para>
 <para>
-When creating a TDE or Qt project, you always have to have a view that inherits QWidget, either by 
-direct inheritance or because the library widget you want to use inherits QWidget. Therefore, the 
+When creating a TDE or Qt project, you always have to have a view that inherits TQWidget, either by 
+direct inheritance or because the library widget you want to use inherits TQWidget. Therefore, the 
 Application Wizard already constructed a view that is an instance of a class yourappView, which 
-inherits QWidget already.
+inherits TQWidget already.
 </para>
 <para>
 This chapter therefore describes how to use library widgets for creating views of TDE or 
@@ -1080,7 +1080,7 @@ inherit your own widget from <classname>QScrollView</classname> or use an instan
 document's view widget.
 </para></listitem> 
 <listitem><para>
-to create a ScrollView yourself, inherit the View widget from  <classname>QWidget</classname> 
+to create a ScrollView yourself, inherit the View widget from  <classname>TQWidget</classname> 
 and add vertical and horizontal  <classname>QScrollBars </classname>. 
 (This is done by TDE`s TDEHTMLView widget.)
 </para></listitem> 
@@ -1206,7 +1206,7 @@ such as F1 for accessing online-help, Ctrl+N for New File etc.
 </para>
 <para>
 If your application contains a lot of accelerators, you should make them configurable
-by an Options-menu; either it could be combined with other application configuration in a QWidget
+by an Options-menu; either it could be combined with other application configuration in a TQWidget
 or stand alone. The TDE library already provides a <classname>KKeyChooser</classname>
 for use in tab dialogs, whereas <classname>KKeyDialog</classname> provides a ready-to use 
 key-configuration dialog. 
@@ -1305,7 +1305,7 @@ a visible widget item and gets a help window. As an exercise, you could try this
 </para>
 <para>
 To add the What's This...? help to one of your widgets, use the static method 
-<methodname>QWhatsThis::add(QWidget *widget, const QString &amp;text)</methodname> 
+<methodname>QWhatsThis::add(TQWidget *widget, const TQString &amp;text)</methodname> 
 </para>
 </sect1>
 </chapter>