Initial TQt conversion

1 files changed, 203 insertions, 203 deletions

diff --git a/doc/qtdocs.sip b/doc/qtdocs.sip
index 1113e94..52ed1ed 100644
--- a/doc/qtdocs.sip
+++ b/doc/qtdocs.sip
@@ -1,22 +1,22 @@
-// This is the SIP file for organising the PyQt documentation.
+// This is the SIP file for organising the PyTQt documentation.
 //
 // Copyright (c) 2007
 // 	Riverbank Computing Limited <info@riverbankcomputing.co.uk>
 // 
-// This file is part of PyQt.
+// This file is part of PyTQt.
 // 
-// This copy of PyQt is free software; you can redistribute it and/or modify it
+// This copy of PyTQt is free software; you can redistribute it and/or modify it
 // under the terms of the GNU General Public License as published by the Free
 // Software Foundation; either version 2, or (at your option) any later
 // version.
 // 
-// PyQt is supplied in the hope that it will be useful, but WITHOUT ANY
+// PyTQt is supplied in the hope that it will be useful, but WITHOUT ANY
 // WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
 // FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
 // details.
 // 
 // You should have received a copy of the GNU General Public License along with
-// PyQt; see the file LICENSE.  If not, write to the Free Software Foundation,
+// PyTQt; see the file LICENSE.  If not, write to the Free Software Foundation,
 // Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
 
 
@@ -30,14 +30,14 @@
 <!DOCTYPE Article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
 <Article>
 <ArtHeader>
-	<Title>Python Bindings for Qt (3.18.1)</Title>
+	<Title>Python Bindings for TQt (3.18.1)</Title>
 	<Author>
 		<FirstName>Phil</FirstName>
 		<Surname>Thompson</Surname>
 	</Author>
 	<Abstract>
 	<Para>
-	This document describes a set of Python bindings for the Qt widget set.
+	This document describes a set of Python bindings for the TQt widget set.
 	Contact the author at <Email>phil@riverbankcomputing.co.uk</Email>.
 	</Para>
 	</Abstract>
@@ -46,34 +46,34 @@
 
 <Sect1><Title>Introduction</Title>
 <Para>
-PyQt is a set of Python bindings for the Qt toolkit and available for all
-platforms supported by Qt, including Windows, Linux, UNIX, MacOS/X and embedded
+PyTQt is a set of Python bindings for the TQt toolkit and available for all
+platforms supported by TQt, including Windows, Linux, UNIX, MacOS/X and embedded
 systems such as the Sharp Zaurus and the Compaq iPAQ.  They have been tested
-against Qt versions 1.43 to 3.3.6, Qt Non-commercial, Qtopia 1.5.0, and Python
-versions 1.5 to 2.4.2.  Qt/Embedded v3 is not supported.  Qt v4 is supported
-by PyQt v4.
+against TQt versions 1.43 to 3.3.6, TQt Non-commercial, TQtopia 1.5.0, and Python
+versions 1.5 to 2.4.2.  TQt/Embedded v3 is not supported.  TQt v4 is supported
+by PyTQt v4.
 </Para>
 
 <Para>
-PyQt is available under the GPL license for use with the GPL version of Qt, a
-a commercial license for use with the commercial version of Qt, a
-non-commercial license for use with the non-commercial version of Qt v2, and an
-educational license for use with the educational version of Qt.
+PyTQt is available under the GPL license for use with the GPL version of TQt, a
+a commercial license for use with the commercial version of TQt, a
+non-commercial license for use with the non-commercial version of TQt v2, and an
+educational license for use with the educational version of TQt.
 </Para>
 
 <Para>
-There is also an evaluation version of PyQt for Windows.  This must be used
-with the corresponding evaluation version of Qt.
+There is also an evaluation version of PyTQt for Windows.  This must be used
+with the corresponding evaluation version of TQt.
 </Para>
 
 <Para>
-PyQt is built using SIP (a tool for generating Python extension modules for
+PyTQt is built using SIP (a tool for generating Python extension modules for
 C++ class libraries).  SIP v4.6 or later must be installed in order to build
-and run this version of PyQt.
+and run this version of PyTQt.
 </Para>
 
 <Para>
-PyQt for MacOS/X requires Qt v3.1.0 or later and Python v2.3 or later.
+PyTQt for MacOS/X retquires TQt v3.1.0 or later and Python v2.3 or later.
 </Para>
 
 <Para>
@@ -91,81 +91,81 @@ user interface widgets.
 <ListItem>
 <Para>
 <Literal>qtaxcontainer</Literal> contains a sub-set of the classes implemented
-in Qt's QAxContainer module, part of Qt's ActiveQt framework.
+in TQt's TQAxContainer module, part of TQt's ActiveTQt framework.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>qtcanvas</Literal> contains the classes implemented in Qt's Canvas
+<Literal>qtcanvas</Literal> contains the classes implemented in TQt's Canvas
 module.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>qtgl</Literal> contains the classes implemented in Qt's OpenGL module.
+<Literal>qtgl</Literal> contains the classes implemented in TQt's OpenGL module.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>qtnetwork</Literal> contains the classes implemented in Qt's Network
+<Literal>qtnetwork</Literal> contains the classes implemented in TQt's Network
 module.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>qtpe</Literal> contains the classes implemented in Qtopia (originally
-called the Qt Palmtop Environment).  It is only supported with Qt/Embedded.
+<Literal>qtpe</Literal> contains the classes implemented in TQtopia (originally
+called the TQt Palmtop Environment).  It is only supported with TQt/Embedded.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>qtsql</Literal> contains the classes implemented in Qt's SQL module.
+<Literal>qtsql</Literal> contains the classes implemented in TQt's SQL module.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>qttable</Literal> contains the classes implemented in Qt's Table
+<Literal>qttable</Literal> contains the classes implemented in TQt's Table
 module.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>qtui</Literal> contains the classes implemented in Qt's qui library.
-These allow GUIs to be created directly from Qt Designer's
+<Literal>qtui</Literal> contains the classes implemented in TQt's tqui library.
+These allow GUIs to be created directly from TQt Designer's
 <Literal>.ui</Literal> files.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>qtxml</Literal> contains the classes implemented in Qt's XML module.
+<Literal>qtxml</Literal> contains the classes implemented in TQt's XML module.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
 <Literal>qtext</Literal> contains useful third-party classes that are not part
-of Qt.  At the moment it contains bindings for QScintilla, the port to Qt of
+of TQt.  At the moment it contains bindings for TQScintilla, the port to TQt of
 the Scintilla programmer's editor class.
 </Para>
 </ListItem>
 </ItemizedList>
 
 <Para>
-PyQt also includes the <Literal>pyuic</Literal> and
-<Literal>pylupdate</Literal> utilities which correspond to the Qt
+PyTQt also includes the <Literal>pyuic</Literal> and
+<Literal>pylupdate</Literal> utilities which correspond to the TQt
 <Literal>uic</Literal> and <Literal>lupdate</Literal> utilities.
-<Literal>pyuic</Literal> converts the GUI designs created with Qt Designer to
+<Literal>pyuic</Literal> converts the GUI designs created with TQt Designer to
 executable Python code.  <Literal>pylupdate</Literal> scans Python code,
 extracts all strings that are candidates for internationalisation, and creates
-an XML file for use by Qt Linguist.
+an XML file for use by TQt Linguist.
 </Para>
 
 <Sect2><Title>Changes</Title>
@@ -176,26 +176,26 @@ The changes visible to the Python programmer in this release are as follows.
 
 <ListItem>
 <Para>
-This version requires SIP v4.4 (or later).
+This version retquires SIP v4.4 (or later).
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-Concatenating Python strings and <Literal>QString</Literal>s is now supported.
+Concatenating Python strings and <Literal>TQString</Literal>s is now supported.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>QString</Literal> now supports the <Literal>*</Literal> and
+<Literal>TQString</Literal> now supports the <Literal>*</Literal> and
 <Literal>*=</Literal> operators that behave as they do for Python strings.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>QString</Literal> is more interoperable with Python string and unicode
+<Literal>TQString</Literal> is more interoperable with Python string and unicode
 objects.  For example they can be passed as arguments to
 <Literal>open()</Literal> and to most (but not all) string methods.
 </Para>
@@ -203,17 +203,17 @@ objects.  For example they can be passed as arguments to
 
 <ListItem>
 <Para>
-<Literal>QPopupMenu</Literal> (and sub-classes) instances now transfer
+<Literal>TQPopupMenu</Literal> (and sub-classes) instances now transfer
 ownership of the menu to Python in the call to <Literal>exec_loop()</Literal>.
 This means the menu's resources are all released when the Python wrapper is
 garbage collected without needing to call
-<Literal>QObject.deleteLater()</Literal>.
+<Literal>TQObject.deleteLater()</Literal>.
 </Para>
 </ListItem>
 
 <ListItem>
 <Para>
-<Literal>QObject.sender()</Literal> now handles Python signals.
+<Literal>TQObject.sender()</Literal> now handles Python signals.
 </Para>
 </ListItem>
 
@@ -233,7 +233,7 @@ The missing <Literal>MacintoshVersion</Literal> enum has been added.
 <Para>
 The convention for converting between a C/C++ null pointer and Python's
 <Literal>None</Literal> object has now been universally applied.  In previous
-versions a null pointer to, for example, a Qt list container would often be
+versions a null pointer to, for example, a TQt list container would often be
 converted to an empty list rather than <Literal>None</Literal>.
 </Para>
 </ListItem>
@@ -243,16 +243,16 @@ converted to an empty list rather than <Literal>None</Literal>.
 </Sect1>
 
 
-<Sect1><Title>Other PyQt Goodies</Title>
-<Sect2><Title>Using Qt Designer</Title>
+<Sect1><Title>Other PyTQt Goodies</Title>
+<Sect2><Title>Using TQt Designer</Title>
 <Para>
-Qt Designer is a GPL'ed GUI design editor provided by Trolltech as part of Qt.
-It generates an XML description of a GUI design. Qt includes
+TQt Designer is a GPL'ed GUI design editor provided by Trolltech as part of TQt.
+It generates an XML description of a GUI design. TQt includes
 <Literal>uic</Literal> which generates C++ code from that XML.
 </Para>
 
 <Para>
-PyQt includes <Literal>pyuic</Literal> which generates Python code from the
+PyTQt includes <Literal>pyuic</Literal> which generates Python code from the
 same XML. The Python code is self contained and can be executed immediately.
 </Para>
 
@@ -260,10 +260,10 @@ same XML. The Python code is self contained and can be executed immediately.
 It is sometimes useful to be able to include some specific Python code in the
 output generated by <Literal>pyuic</Literal>. For example, if you are using
 custom widgets, <Literal>pyuic</Literal> has no way of knowing the name of the
-Python module containing the widget and so cannot generate the required
+Python module containing the widget and so cannot generate the retquired
 <Literal>import</Literal> statement. To help get around this,
 <Literal>pyuic</Literal> will extract any lines entered in the
-<Literal>Comment</Literal> field of Qt Designer's
+<Literal>Comment</Literal> field of TQt Designer's
 <Literal>Form Settings</Literal> dialog that begin with
 <Literal>Python:</Literal> and copies them to the generated output.
 </Para>
@@ -293,7 +293,7 @@ from foo import bar
 
 <Para>
 Thanks to Christian Bird, <Literal>pyuic</Literal> will extract Python code
-entered using Qt Designer to implement slots. In Qt Designer, when you need to
+entered using TQt Designer to implement slots. In TQt Designer, when you need to
 edit a slot and the source editor appears, enter Python code between the curly
 braces. Don't worry about the correct starting indent level, each line is
 prepended with a correct indentation.
@@ -314,7 +314,7 @@ Here's an example of a simple slot.
 void DebMainWindowFrm::browsePushButtonClicked()
 {
 if self.debugging:
-    QMessageBox.critical(self, "Event", "browse pushbutton was clicked!")
+    TQMessageBox.critical(self, "Event", "browse pushbutton was clicked!")
 }
 </ProgramListing>
 
@@ -323,11 +323,11 @@ Here is the resulting code when <Literal>pyuic</Literal> is run.
 </Para>
 
 <ProgramListing>
-class DebMainWindowFrm(QMainWindow):
+class DebMainWindowFrm(TQMainWindow):
     ...stuff...
     def browsePushButtonClicked(self):
         if self.debugging:
-            QMessageBox.critical(self, "Event", "browse pushbutton was clicked!")
+            TQMessageBox.critical(self, "Event", "browse pushbutton was clicked!")
 </ProgramListing>
 
 <Para>
@@ -342,9 +342,9 @@ annoying when trying to code in Python.
 </Para>
 </Sect2>
 
-<Sect2><Title>Using Qt Linguist</Title>
+<Sect2><Title>Using TQt Linguist</Title>
 <Para>
-Qt includes the <Literal>lupdate</Literal> program which parses C++ source
+TQt includes the <Literal>lupdate</Literal> program which parses C++ source
 files converting calls to the <Literal>QT_TR_NOOP()</Literal> and
 <Literal>QT_TRANSLATE_NOOP()</Literal> macros to <Literal>.ts</Literal>
 language source files.  The <Literal>lrelease</Literal> program is then used to
@@ -353,21 +353,21 @@ your application.
 </Para>
 
 <Para>
-Thanks to Detlev Offenbach, PyQt includes the <Literal>pylupdate</Literal>
+Thanks to Detlev Offenbach, PyTQt includes the <Literal>pylupdate</Literal>
 program.  This generates the same <Literal>.ts</Literal> language source files
-from your PyQt source files.
+from your PyTQt source files.
 </Para>
 </Sect2>
 </Sect1>
 
 
-<Sect1><Title>Deploying Commercial PyQt Applications</Title>
+<Sect1><Title>Deploying Commercial PyTQt Applications</Title>
 <Para>
-When deploying commercial PyQt applications it is necessary to discourage users
-from accessing the underlying PyQt modules for themselves.  A user that used
+When deploying commercial PyTQt applications it is necessary to discourage users
+from accessing the underlying PyTQt modules for themselves.  A user that used
 the modules shipped with your application to develop new applications would
-themselves be considered a developer and would need their own commercial Qt and
-PyQt licenses.
+themselves be considered a developer and would need their own commercial TQt and
+PyTQt licenses.
 </Para>
 
 <Para>
@@ -376,13 +376,13 @@ One solution to this problem is the
 package.  This allows you to build Python extension modules that can only be
 imported by a digitally signed custom interpreter.  The package enables you to
 create such an interpreter with your application embedded within it.  The
-result is an interpreter that can only run your application, and PyQt modules
+result is an interpreter that can only run your application, and PyTQt modules
 that can only be imported by that interpreter.  You can use the package to
 similarly restrict access to any extension module.
 </Para>
 
 <Para>
-In order to build PyQt with support for the VendorID package, pass the
+In order to build PyTQt with support for the VendorID package, pass the
 <Literal>-i</Literal> command line flag to <Literal>configure.py</Literal>.
 </Para>
 </Sect1>
@@ -390,9 +390,9 @@ In order to build PyQt with support for the VendorID package, pass the
 <Sect1><Title><Literal>pyqtconfig</Literal> and Build System Support</Title>
 <Para>
 The SIP build system (ie. the <Literal>sipconfig</Literal> module) is described
-in the SIP documentation.  PyQt includes the <Literal>pyqtconfig</Literal>
+in the SIP documentation.  PyTQt includes the <Literal>pyqtconfig</Literal>
 module that can be used by configuration scripts of other bindings that are
-built on top of PyQt.
+built on top of PyTQt.
 </Para>
 
 <Para>
@@ -404,7 +404,7 @@ The <Literal>pyqtconfig</Literal> module contains the following classes:
 <Term><Literal>Configuration(sipconfig.Configuration)</Literal></Term>
 <ListItem>
 <Para>
-This class encapsulates additional configuration values, specific to PyQt, that
+This class encapsulates additional configuration values, specific to PyTQt, that
 can be accessed as instance variables.
 </Para>
 
@@ -429,7 +429,7 @@ The name of the directory containing the <Literal>pyuic</Literal> and
 <Term><Literal>pyqt_config_args</Literal></Term>
 <ListItem>
 <Para>
-The command line passed to <Literal>configure.py</Literal> when PyQt was
+The command line passed to <Literal>configure.py</Literal> when PyTQt was
 configured.
 </Para>
 <Para></Para><Para></Para>
@@ -440,7 +440,7 @@ configured.
 <Term><Literal>pyqt_mod_dir</Literal></Term>
 <ListItem>
 <Para>
-The name of the directory containing the PyQt modules.
+The name of the directory containing the PyTQt modules.
 </Para>
 <Para></Para><Para></Para>
 </ListItem>
@@ -450,7 +450,7 @@ The name of the directory containing the PyQt modules.
 <Term><Literal>pyqt_modules</Literal></Term>
 <ListItem>
 <Para>
-A string containing the names of the PyQt modules that were installed.
+A string containing the names of the PyTQt modules that were installed.
 </Para>
 <Para></Para><Para></Para>
 </ListItem>
@@ -581,7 +581,7 @@ any module that imports the <Literal>qtxml</Literal> module.
 <ListItem>
 <Para>
 The name of the base directory where the <Literal>.sip</Literal> files for each
-of the PyQt modules is installed. A sub-directory exists with the same name as
+of the PyTQt modules is installed. A sub-directory exists with the same name as
 the module.
 </Para>
 <Para></Para><Para></Para>
@@ -592,7 +592,7 @@ the module.
 <Term><Literal>pyqt_version</Literal></Term>
 <ListItem>
 <Para>
-The PyQt version as a 3 part hexadecimal number (eg. v3.10 is represented as
+The PyTQt version as a 3 part hexadecimal number (eg. v3.10 is represented as
 <Literal>0x030a00</Literal>).
 </Para>
 <Para></Para><Para></Para>
@@ -603,7 +603,7 @@ The PyQt version as a 3 part hexadecimal number (eg. v3.10 is represented as
 <Term><Literal>pyqt_version_str</Literal></Term>
 <ListItem>
 <Para>
-The PyQt version as a string. For development snapshots it will start with
+The PyTQt version as a string. For development snapshots it will start with
 <Literal>snapshot-</Literal>.
 </Para>
 <Para></Para><Para></Para>
@@ -615,7 +615,7 @@ The PyQt version as a string. For development snapshots it will start with
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtModuleMakefile(sipconfig.SIPModuleMakefile)</Literal></Term>
+<Term><Literal>TQtModuleMakefile(sipconfig.SIPModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qt</Literal> module.
@@ -635,7 +635,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtAxContainerModuleMakefile(QtModuleMakefile)</Literal></Term>
+<Term><Literal>TQtAxContainerModuleMakefile(TQtModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qtaxcontainer</Literal>
@@ -656,7 +656,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtCanvasModuleMakefile(QtModuleMakefile)</Literal></Term>
+<Term><Literal>TQtCanvasModuleMakefile(TQtModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qtcanvas</Literal>
@@ -677,7 +677,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtExtModuleMakefile(QtModuleMakefile)</Literal></Term>
+<Term><Literal>TQtExtModuleMakefile(TQtModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qtext</Literal> module.
@@ -697,7 +697,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtGLModuleMakefile(QtModuleMakefile)</Literal></Term>
+<Term><Literal>TQtGLModuleMakefile(TQtModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qtgl</Literal> module.
@@ -717,7 +717,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtNetworkModuleMakefile(QtModuleMakefile)</Literal></Term>
+<Term><Literal>TQtNetworkModuleMakefile(TQtModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qtnetwork</Literal>
@@ -738,7 +738,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtTableModuleMakefile(QtModuleMakefile)</Literal></Term>
+<Term><Literal>TQtTableModuleMakefile(TQtModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qttable</Literal>
@@ -759,7 +759,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtSQLModuleMakefile(QtTableModuleMakefile)</Literal></Term>
+<Term><Literal>TQtSQLModuleMakefile(TQtTableModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qtsql</Literal> module.
@@ -779,7 +779,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtUIModuleMakefile(QtModuleMakefile)</Literal></Term>
+<Term><Literal>TQtUIModuleMakefile(TQtModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qtui</Literal> module.
@@ -799,7 +799,7 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 </VarListEntry>
 
 <VarListEntry>
-<Term><Literal>QtXMLModuleMakefile(QtModuleMakefile)</Literal></Term>
+<Term><Literal>TQtXMLModuleMakefile(TQtModuleMakefile)</Literal></Term>
 <ListItem>
 <Para>
 The Makefile class for modules that import the <Literal>qtxml</Literal> module.
@@ -827,15 +827,15 @@ This is a reimplementation of <Literal>sipconfig.Makefile.finalise()</Literal>.
 <Sect1><Title>Things to be Aware Of</Title>
 <Sect2><Title>super and Wrapped Classes</Title>
 <Para>
-Internally PyQt implements a lazy technique for attribute lookup where
+Internally PyTQt implements a lazy technique for attribute lookup where
 attributes are only placed in type and instance dictionaries when they are
 first referenced.  This technique is needed to reduce the time taken to import
-large modules such as PyQt.
+large modules such as PyTQt.
 </Para>
 
 <Para>
 In most circumstances this technique is transparent to an application.  The
-exception is when <Literal>super</Literal> is used with a PyQt class.  The way
+exception is when <Literal>super</Literal> is used with a PyTQt class.  The way
 that <Literal>super</Literal> is currently implemented means that the lazy
 lookup is bypassed resulting in <Literal>AttributeError</Literal> exceptions
 unless the attribute has been previously referenced.
@@ -843,49 +843,49 @@ unless the attribute has been previously referenced.
 
 <Para>
 Note that this restriction applies to any class wrapped by SIP and not just
-PyQt.
+PyTQt.
 </Para>
 </Sect2>
 
 
-<Sect2><Title>Python Strings, Qt Strings and Unicode</Title>
+<Sect2><Title>Python Strings, TQt Strings and Unicode</Title>
 <Para>
-Unicode support was added to Qt in v2.0 and to Python in v1.6.  In Qt, Unicode
-support is implemented using the <Literal>QString</Literal> class.  It is
-important to understand that <Literal>QString</Literal>s, Python string objects
+Unicode support was added to TQt in v2.0 and to Python in v1.6.  In TQt, Unicode
+support is implemented using the <Literal>TQString</Literal> class.  It is
+important to understand that <Literal>TQString</Literal>s, Python string objects
 and Python Unicode objects are all different but conversions between them are
 automatic in almost all cases and easy to achieve manually when needed.
 </Para>
 
 <Para>
-Whenever PyQt expects a <Literal>QString</Literal> as a function argument, a
+Whenever PyTQt expects a <Literal>TQString</Literal> as a function argument, a
 Python string object or a Python Unicode object can be provided instead, and
-PyQt will do the necessary conversion automatically.
+PyTQt will do the necessary conversion automatically.
 </Para>
 
 <Para>
 You may also manually convert Python string and Unicode objects to
-<Literal>QString</Literal>s by using the <Literal>QString</Literal> constructor
+<Literal>TQString</Literal>s by using the <Literal>TQString</Literal> constructor
 as demonstrated in the following code fragment.
 </Para>
 
 <ProgramListing>
-qs1 = QString('Converted Python string object')
-qs2 = QString(u'Converted Python Unicode object')
+qs1 = TQString('Converted Python string object')
+qs2 = TQString(u'Converted Python Unicode object')
 </ProgramListing>
 
 <Para>
-In order to convert a <Literal>QString</Literal> to a Python string object use
+In order to convert a <Literal>TQString</Literal> to a Python string object use
 the Python <Literal>str()</Literal> function.  Applying
-<Literal>str()</Literal> to a null <Literal>QString</Literal> and an empty
-<Literal>QString</Literal> both result in an empty Python string object.
+<Literal>str()</Literal> to a null <Literal>TQString</Literal> and an empty
+<Literal>TQString</Literal> both result in an empty Python string object.
 </Para>
 
 <Para>
-In order to convert a <Literal>QString</Literal> to a Python Unicode object use
+In order to convert a <Literal>TQString</Literal> to a Python Unicode object use
 the Python <Literal>unicode()</Literal> function.  Applying
-<Literal>unicode()</Literal> to a null <Literal>QString</Literal> and an empty
-<Literal>QString</Literal> both result in an empty Python Unicode object.
+<Literal>unicode()</Literal> to a null <Literal>TQString</Literal> and an empty
+<Literal>TQString</Literal> both result in an empty Python Unicode object.
 </Para>
 </Sect2>
 
@@ -914,7 +914,7 @@ whenever it is returned by the underlying C++ code.
 
 <Sect2><Title>Support for C++ <Literal>void *</Literal> Data Types</Title>
 <Para>
-PyQt represents <Literal>void *</Literal> values as objects of type
+PyTQt represents <Literal>void *</Literal> values as objects of type
 <Literal>sip.voidptr</Literal>. Such values are often used to pass the
 addresses of external objects between different Python modules. To make this
 easier, a Python integer (or anything that Python can convert to an integer)
@@ -934,11 +934,11 @@ method takes an integer argument which is the length of the data in bytes.
 
 <Sect2><Title>Support for Threads</Title>
 <Para>
-PyQt implements the full set of Qt's thread classes.  Python, of course, also
+PyTQt implements the full set of TQt's thread classes.  Python, of course, also
 has its own thread extension modules.  If you are using SIP v4 (or later) and
-Python v2.3.5 (or later) then PyQt does not impose any additional restrictions.
-(Read the relevant part of the Qt documentation to understand the restrictions
-imposed by the Qt API.)
+Python v2.3.5 (or later) then PyTQt does not impose any additional restrictions.
+(Read the relevant part of the TQt documentation to understand the restrictions
+imposed by the TQt API.)
 </Para>
 <Para>
 If you are using earlier versions of either SIP or Python then it is possible
@@ -947,27 +947,27 @@ to use either of the APIs so long as you follow some simple rules.
 <ItemizedList>
 <ListItem>
 <Para>
-If you use the Qt API then the very first <Literal>import</Literal> of one of
-the PyQt modules must be done from the main thread.
+If you use the TQt API then the very first <Literal>import</Literal> of one of
+the PyTQt modules must be done from the main thread.
 </Para>
 </ListItem>
 <ListItem>
 <Para>
-If you use the Python API then all calls to PyQt (including any
+If you use the Python API then all calls to PyTQt (including any
 <Literal>import</Literal>s) must be done from one thread only.  Therefore, if
-you want to make calls to PyQt from several threads then you must use the Qt
+you want to make calls to PyTQt from several threads then you must use the TQt
 API.
 </Para>
 </ListItem>
 <ListItem>
 <Para>
-If you want to use both APIs in the same application then all calls to PyQt
-must be done from threads created using the Qt API.
+If you want to use both APIs in the same application then all calls to PyTQt
+must be done from threads created using the TQt API.
 </Para>
 </ListItem>
 </ItemizedList>
 <Para>
-The above comments actually apply to any SIP generated module, not just PyQt.
+The above comments actually apply to any SIP generated module, not just PyTQt.
 </Para>
 </Sect2>
 
@@ -979,8 +979,8 @@ longer be referenced from within the program:
 </Para>
 
 <ProgramListing>
-c = new QColor();
-c = new QColor();
+c = new TQColor();
+c = new TQColor();
 </ProgramListing>
 
 <Para>
@@ -989,8 +989,8 @@ the second is assigned to <Literal>c</Literal>:
 </Para>
 
 <ProgramListing>
-c = QColor()
-c = QColor()
+c = TQColor()
+c = TQColor()
 </ProgramListing>
 
 <Para>
@@ -999,29 +999,29 @@ is done within class definitions, so the code fragment would be something like:
 </Para>
 
 <ProgramListing>
-self.c1 = QColor()
-self.c2 = QColor()
+self.c1 = TQColor()
+self.c2 = TQColor()
 </ProgramListing>
 
 <Para>
-Sometimes a Qt class instance will maintain a pointer to another instance and
+Sometimes a TQt class instance will maintain a pointer to another instance and
 will eventually call the destructor of that second instance. The most common
-example is that a <Literal>QObject</Literal> (and any of its sub-classes) keeps
+example is that a <Literal>TQObject</Literal> (and any of its sub-classes) keeps
 pointers to its children and will automatically call their destructors. In
 these cases, the corresponding Python object will also keep a reference to the
 corresponding child objects.
 </Para>
 
 <Para>
-So, in the following Python fragment, the first <Literal>QLabel</Literal> is
+So, in the following Python fragment, the first <Literal>TQLabel</Literal> is
 not destroyed when the second is assigned to <Literal>l</Literal> because the
-parent <Literal>QWidget</Literal> still has a reference to it.
+parent <Literal>TQWidget</Literal> still has a reference to it.
 </Para>
 
 <ProgramListing>
-p = QWidget()
-l = QLabel('First label',p)
-l = QLabel('Second label',p)
+p = TQWidget()
+l = TQLabel('First label',p)
+l = TQLabel('Second label',p)
 </ProgramListing>
 </Sect2>
 
@@ -1032,9 +1032,9 @@ variables.  For example:
 </Para>
 
 <ProgramListing>
-tab = QTab()
+tab = TQTab()
 tab.label = "First Tab"
-tab.r = QRect(10,10,75,30)
+tab.r = TQRect(10,10,75,30)
 </ProgramListing>
 
 <Para>
@@ -1052,39 +1052,39 @@ the future.
 <Sect2><Title>Multiple Inheritance</Title>
 <Para>
 It is not possible to define a new Python class that sub-classes from more than
-one Qt class.
+one TQt class.
 </Para>
 </Sect2>
 
 <Sect2><Title>i18n Support</Title>
 <Para>
-Qt implements i18n support through the Qt Linguist application, the
-<Literal>QTranslator</Literal> class, and the
-<Literal>QApplication::translate()</Literal>, <Literal>QObject::tr()</Literal>
-and <Literal>QObject::trUtf8()</Literal> methods.  Usually the
+TQt implements i18n support through the TQt Linguist application, the
+<Literal>TQTranslator</Literal> class, and the
+<Literal>TQApplication::translate()</Literal>, <Literal>TQObject::tr()</Literal>
+and <Literal>TQObject::trUtf8()</Literal> methods.  Usually the
 <Literal>tr()</Literal> method is used to obtain the correct translation of a
 message.  The translation process uses a message context to allow the same
 message to be translated differently.  <Literal>tr()</Literal> is actually
 generated by <Literal>moc</Literal> and uses the hardcoded class name as the
-context.  On the other hand, <Literal>QApplication::translate()</Literal>
+context.  On the other hand, <Literal>TQApplication::translate()</Literal>
 allows to context to be explicitly stated.
 </Para>
 
 <Para>
-Unfortunately, because of the way Qt implents <Literal>tr()</Literal> (and
-<Literal>trUtf8()</Literal>) it is not possible for PyQt to exactly reproduce
-its behavour.  The PyQt implementation of <Literal>tr()</Literal> (and
+Unfortunately, because of the way TQt implents <Literal>tr()</Literal> (and
+<Literal>trUtf8()</Literal>) it is not possible for PyTQt to exactly reproduce
+its behavour.  The PyTQt implementation of <Literal>tr()</Literal> (and
 <Literal>trUtf8()</Literal>) uses the class name of the instance as the
 context.  The key difference, and the source of potential problems, is that the
-context is determined dynamically in PyQt, but is hardcoded in Qt. In other
+context is determined dynamically in PyTQt, but is hardcoded in TQt. In other
 words, the context of a translation may change depending on an instance's class
 hierarchy.
 </Para>
 
 <ProgramListing>
-class A(QObject):
+class A(TQObject):
     def __init__(self):
-        QObject.__init__(self)
+        TQObject.__init__(self)
 
     def hello(self):
         return self.tr("Hello")
@@ -1108,19 +1108,19 @@ would be <Literal>A</Literal> in both cases.
 </Para>
 
 <Para>
-The PyQt behaviour is unsatisfactory and may be changed in the future.  It is
-recommended that <Literal>QApplication.translate()</Literal> be used in
+The PyTQt behaviour is unsatisfactory and may be changed in the future.  It is
+recommended that <Literal>TQApplication.translate()</Literal> be used in
 preference to <Literal>tr()</Literal> (and <Literal>trUtf8()</Literal>).  This
-is guaranteed to work with current and future versions of PyQt and makes it
+is guaranteed to work with current and future versions of PyTQt and makes it
 much easier to share message files between Python and C++ code.  Below is the
 alternative implementation of <Literal>A</Literal> that uses
-<Literal>QApplication.translate()</Literal>.
+<Literal>TQApplication.translate()</Literal>.
 </Para>
 
 <ProgramListing>
-class A(QObject):
+class A(TQObject):
     def __init__(self):
-        QObject.__init__(self)
+        TQObject.__init__(self)
 
     def hello(self):
         return qApp.translate("A","Hello")
@@ -1128,7 +1128,7 @@ class A(QObject):
 
 <Para>
 Note that the code generated by <Literal>pyuic</Literal> uses
-<Literal>QApplication.translate()</Literal>.
+<Literal>TQApplication.translate()</Literal>.
 </Para>
 </Sect2>
 </Sect1>
@@ -1136,15 +1136,15 @@ Note that the code generated by <Literal>pyuic</Literal> uses
 
 <Sect1><Title>Signal and Slot Support</Title>
 <Para>
-A signal may be either a Qt signal (specified using
+A signal may be either a TQt signal (specified using
 <Literal>SIGNAL()</Literal>) or a Python signal (specified using
 <Literal>PYSIGNAL()</Literal>).
 </Para>
 
 <Para>
-A slot can be either a Python callable object, a Qt signal (specified using
+A slot can be either a Python callable object, a TQt signal (specified using
 <Literal>SIGNAL()</Literal>), a Python signal (specified using
-<Literal>PYSIGNAL()</Literal>), or a Qt slot (specified using
+<Literal>PYSIGNAL()</Literal>), or a TQt slot (specified using
 <Literal>SLOT()</Literal>).
 </Para>
 
@@ -1154,28 +1154,28 @@ example:
 </Para>
 
 <ProgramListing>
-QObject.connect(a,SIGNAL("QtSig()"),pyFunction)
-QObject.connect(a,SIGNAL("QtSig()"),pyClass.pyMethod)
-QObject.connect(a,SIGNAL("QtSig()"),PYSIGNAL("PySig"))
-QObject.connect(a,SIGNAL("QtSig()"),SLOT("QtSlot()"))
-QObject.connect(a,PYSIGNAL("PySig"),pyFunction)
-QObject.connect(a,PYSIGNAL("PySig"),pyClass.pyMethod)
-QObject.connect(a,PYSIGNAL("PySig"),SIGNAL("QtSig()"))
-QObject.connect(a,PYSIGNAL("PySig"),SLOT("QtSlot()"))
+TQObject.connect(a,SIGNAL("TQtSig()"),pyFunction)
+TQObject.connect(a,SIGNAL("TQtSig()"),pyClass.pyMethod)
+TQObject.connect(a,SIGNAL("TQtSig()"),PYSIGNAL("PySig"))
+TQObject.connect(a,SIGNAL("TQtSig()"),SLOT("TQtSlot()"))
+TQObject.connect(a,PYSIGNAL("PySig"),pyFunction)
+TQObject.connect(a,PYSIGNAL("PySig"),pyClass.pyMethod)
+TQObject.connect(a,PYSIGNAL("PySig"),SIGNAL("TQtSig()"))
+TQObject.connect(a,PYSIGNAL("PySig"),SLOT("TQtSlot()"))
 </ProgramListing>
 
 <Para>
-When a slot is a Python method that corresponds to a Qt slot then a signal can
-be connected to either the Python method or the Qt slot.  The following
+When a slot is a Python method that corresponds to a TQt slot then a signal can
+be connected to either the Python method or the TQt slot.  The following
 connections achieve the same effect.
 </Para>
 
 <ProgramListing>
-sbar = QScrollBar()
-lcd = QLCDNumber()
+sbar = TQScrollBar()
+lcd = TQLCDNumber()
 
-QObject.connect(sbar,SIGNAL("valueChanged(int)"),lcd.display)
-QObject.connect(sbar,SIGNAL("valueChanged(int)"),lcd,SLOT("display(int)"))
+TQObject.connect(sbar,SIGNAL("valueChanged(int)"),lcd.display)
+TQObject.connect(sbar,SIGNAL("valueChanged(int)"),lcd,SLOT("display(int)"))
 </ProgramListing>
 
 <Para>
@@ -1188,9 +1188,9 @@ Disconnecting signals works in exactly the same way.
 </Para>
 
 <Para>
-Any instance of a class that is derived from the <Literal>QObject</Literal>
+Any instance of a class that is derived from the <Literal>TQObject</Literal>
 class can emit a signal using the <Literal>emit</Literal> method.  This takes
-two arguments.  The first is the Python or Qt signal, the second is a Python
+two arguments.  The first is the Python or TQt signal, the second is a Python
 tuple which are the arguments to the signal.  For example:
 </Para>
 
@@ -1209,8 +1209,8 @@ garbage collected.
 </Para>
 
 <Para>
-Qt allows a signal to be connected to a slot that requires fewer arguments than
-the signal passes.  The extra arguments are quietly discarded.  Python slots
+TQt allows a signal to be connected to a slot that retquires fewer arguments than
+the signal passes.  The extra arguments are tquietly discarded.  Python slots
 can be used in the same way. 
 </Para>
 </Sect1>
@@ -1220,9 +1220,9 @@ can be used in the same way.
 <Para>
 Static member functions are implemented as Python class functions.
 For example the C++ static member function
-<Literal>QObject::connect()</Literal> is called from Python as
-<Literal>QObject.connect()</Literal> or <Literal>self.connect()</Literal> if
-called from a sub-class of <Literal>QObject</Literal>.
+<Literal>TQObject::connect()</Literal> is called from Python as
+<Literal>TQObject.connect()</Literal> or <Literal>self.connect()</Literal> if
+called from a sub-class of <Literal>TQObject</Literal>.
 </Para>
 </Sect1>
 
@@ -1239,9 +1239,9 @@ the enumerated type was defined in must be included.  For example:
 </Para>
 
 <ProgramListing>
-Qt.SolidPattern
-QWidget.TabFocus
-QFrame.TabFocus
+TQt.SolidPattern
+TQWidget.TabFocus
+TQFrame.TabFocus
 </ProgramListing>
 </Sect1>
 
@@ -1548,13 +1548,13 @@ This takes no parameters and returns a tuple of the values returned by the
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerBash (QScintilla v1.4+)</Title>
+<Sect2><Title>QextScintillaLexerBash (TQScintilla v1.4+)</Title>
 <Para>
 <Literal>QextScintillaLexerBash</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerBatch (QScintilla v1.6+)</Title>
+<Sect2><Title>QextScintillaLexerBatch (TQScintilla v1.6+)</Title>
 <Para>
 <Literal>QextScintillaLexerBatch</Literal> is fully implemented.
 </Para>
@@ -1572,19 +1572,19 @@ This takes no parameters and returns a tuple of the values returned by the
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerCSS (QScintilla v1.6+)</Title>
+<Sect2><Title>QextScintillaLexerCSS (TQScintilla v1.6+)</Title>
 <Para>
 <Literal>QextScintillaLexerCSS</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerDiff (QScintilla v1.6+)</Title>
+<Sect2><Title>QextScintillaLexerDiff (TQScintilla v1.6+)</Title>
 <Para>
 <Literal>QextScintillaLexerDiff</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerHTML (QScintilla v1.1+)</Title>
+<Sect2><Title>QextScintillaLexerHTML (TQScintilla v1.1+)</Title>
 <Para>
 <Literal>QextScintillaLexerHTML</Literal> is fully implemented.
 </Para>
@@ -1608,13 +1608,13 @@ This takes no parameters and returns a tuple of the values returned by the
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerLua (QScintilla v1.5+)</Title>
+<Sect2><Title>QextScintillaLexerLua (TQScintilla v1.5+)</Title>
 <Para>
 <Literal>QextScintillaLexerLua</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerMakefile (QScintilla v1.6+)</Title>
+<Sect2><Title>QextScintillaLexerMakefile (TQScintilla v1.6+)</Title>
 <Para>
 <Literal>QextScintillaLexerMakefile</Literal> is fully implemented.
 </Para>
@@ -1626,13 +1626,13 @@ This takes no parameters and returns a tuple of the values returned by the
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerPOV (QScintilla v1.6+)</Title>
+<Sect2><Title>QextScintillaLexerPOV (TQScintilla v1.6+)</Title>
 <Para>
 <Literal>QextScintillaLexerPOV</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerProperties (QScintilla v1.6+)</Title>
+<Sect2><Title>QextScintillaLexerProperties (TQScintilla v1.6+)</Title>
 <Para>
 <Literal>QextScintillaLexerProperties</Literal> is fully implemented.
 </Para>
@@ -1644,19 +1644,19 @@ This takes no parameters and returns a tuple of the values returned by the
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerRuby (QScintilla v1.5+)</Title>
+<Sect2><Title>QextScintillaLexerRuby (TQScintilla v1.5+)</Title>
 <Para>
 <Literal>QextScintillaLexerRuby</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerSQL (QScintilla v1.1+)</Title>
+<Sect2><Title>QextScintillaLexerSQL (TQScintilla v1.1+)</Title>
 <Para>
 <Literal>QextScintillaLexerSQL</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QextScintillaLexerTeX (QScintilla v1.6+)</Title>
+<Sect2><Title>QextScintillaLexerTeX (TQScintilla v1.6+)</Title>
 <Para>
 <Literal>QextScintillaLexerTeX</Literal> is fully implemented.
 </Para>
@@ -1715,16 +1715,16 @@ This takes no parameters and returns a tuple of the values returned by the
 %ExportedDoc
 <Sect1><Title><Literal>qtpe</Literal> Module Reference</Title>
 
-<Sect2><Title>QPEApplication</Title>
+<Sect2><Title>TQPEApplication</Title>
 <FuncSynopsis>
-	<FuncDef><Function>QApplication</Function></FuncDef>
+	<FuncDef><Function>TQApplication</Function></FuncDef>
 	<ParamDef>int& <Parameter>argc</Parameter></ParamDef>
 	<ParamDef>char **<Parameter>argv</Parameter></ParamDef>
 	<ParamDef>Type <Parameter>type</Parameter></ParamDef>
 </FuncSynopsis>
 <Para>
 This takes two parameters, the first of which is a list of argument strings.
-Arguments used by Qt are removed from the list.
+Arguments used by TQt are removed from the list.
 </Para>
 
 <FuncSynopsis>
@@ -1738,7 +1738,7 @@ This has been renamed to <Literal>exec_loop</Literal> in Python.
 
 <Sect2><Title>AppLnk</Title>
 <FuncSynopsis>
-	<FuncDef>virtual QString <Function>exec</Function> const</FuncDef>
+	<FuncDef>virtual TQString <Function>exec</Function> const</FuncDef>
 	<ParamDef></ParamDef>
 </FuncSynopsis>
 <Para>
@@ -1766,7 +1766,7 @@ This has been renamed to <Literal>exec_property</Literal> in Python.
 
 <Sect2><Title>DocLnk</Title>
 <FuncSynopsis>
-	<FuncDef>QString <Function>exec</Function> const</FuncDef>
+	<FuncDef>TQString <Function>exec</Function> const</FuncDef>
 	<ParamDef></ParamDef>
 </FuncSynopsis>
 <Para>
@@ -1820,27 +1820,27 @@ Not implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QCopEnvelope</Title>
+<Sect2><Title>TQCopEnvelope</Title>
 <Para>
-<Literal>QCopEnvelope</Literal> is fully implemented.
+<Literal>TQCopEnvelope</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QDawg</Title>
+<Sect2><Title>TQDawg</Title>
 <Para>
-<Literal>QDawg</Literal> is fully implemented.
+<Literal>TQDawg</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QPEMenuBar</Title>
+<Sect2><Title>TQPEMenuBar</Title>
 <Para>
-<Literal>QPEMenuBar</Literal> is fully implemented.
+<Literal>TQPEMenuBar</Literal> is fully implemented.
 </Para>
 </Sect2>
 
-<Sect2><Title>QPEToolBar</Title>
+<Sect2><Title>TQPEToolBar</Title>
 <Para>
-<Literal>QPEToolBar</Literal> is fully implemented.
+<Literal>TQPEToolBar</Literal> is fully implemented.
 </Para>
 </Sect2>