From 3e98ce7f85f06e95ad121c6f541d14464d85919e Mon Sep 17 00:00:00 2001 From: Michele Calgaro Date: Thu, 27 Sep 2018 16:03:48 +0900 Subject: qt -> tqt conversion: QTDIR -> TQTDIR QTDOC -> TQTDOC INCDIR_QT -> INCDIR_TQT LIBDIR_QT -> LIBDIR_TQT QT_INC -> TQT_INC QT_LIB -> TQT_LIB Signed-off-by: Michele Calgaro --- doc/html/assistant-6.html | 2 +- doc/html/commonproblems.html | 24 ++++++++--------- doc/html/customstyles.html | 2 +- doc/html/demo-example.html | 2 +- doc/html/designer-manual-6.html | 4 +-- doc/html/dragdrop-example.html | 2 +- doc/html/emb-classes.html | 2 +- doc/html/emb-envvars.html | 4 +-- doc/html/emb-fonts.html | 2 +- doc/html/emb-install.html | 4 +-- doc/html/emb-running.html | 10 +++---- doc/html/emb-tqvfb.html | 2 +- doc/html/helpsystem-example.html | 2 +- doc/html/how-to-learn-ntqt.html | 2 +- doc/html/i18n.html | 2 +- doc/html/install-mac.html | 32 +++++++++++----------- doc/html/install-x11.html | 22 +++++++-------- doc/html/netscape-plugin.html | 2 +- doc/html/opengl-box-example.html | 2 +- doc/html/opengl-gear-example.html | 2 +- doc/html/opengl-overlay-example.html | 2 +- doc/html/opengl-overlay-x11-example.html | 2 +- doc/html/opengl-pixmap-example.html | 2 +- doc/html/opengl-sharedbox-example.html | 2 +- doc/html/opengl-texture-example.html | 2 +- doc/html/plugins-howto.html | 6 ++--- doc/html/porting.html | 4 +-- doc/html/qaxcontainer.html | 4 +-- doc/html/qaxserver.html | 4 +-- doc/html/qmake-manual-2.html | 4 +-- doc/html/qmake-manual-8.html | 8 +++--- doc/html/sql-driver.html | 46 ++++++++++++++++---------------- doc/html/tablet-example.html | 2 +- doc/html/textedit-example.html | 2 +- doc/html/toplevel-example.html | 4 +-- doc/html/widgets-example.html | 4 +-- 36 files changed, 112 insertions(+), 112 deletions(-) (limited to 'doc/html') diff --git a/doc/html/assistant-6.html b/doc/html/assistant-6.html index 266490db3..d2b420914 100644 --- a/doc/html/assistant-6.html +++ b/doc/html/assistant-6.html @@ -118,7 +118,7 @@ body { background: #ffffff; color: black; } > assistant -profile helpdemo.adp

See the HelpDemo example in the TQt distribution for a demonstration on how to use TQt Assistant with profiles for your own applications.

-

When distributing TQt Assistant with your application, you will also need to copy the icon files from the QTDIR/tools/assistant/images directory so that TQt Assistant finds its icons.

+

When distributing TQt Assistant with your application, you will also need to copy the icon files from the TQTDIR/tools/assistant/images directory so that TQt Assistant finds its icons.

diff --git a/doc/html/commonproblems.html b/doc/html/commonproblems.html index c410232c7..5b5c9fd12 100644 --- a/doc/html/commonproblems.html +++ b/doc/html/commonproblems.html @@ -66,13 +66,13 @@ moc-generated object code into your executable. See Using the are usually located in the include subdirectory of TQt distributions. Care must be taken to include the header files of the relevant release of TQt. Those with a command-line compiler will typically use options such as -/I%QTDIR%\include +/I%TQTDIR%\include the relevant release of TQt.

Meta Object Compiler and other tools - Compile time

Programmers need to run moc and other tools such as uic. These tools are usually located in the bin subdirectory of TQt distributions. -Either run "$QTDIR"/bin/moc and "$QTDIR"/bin/uic or add "$QTDIR"/bin +Either run "$TQTDIR"/bin/moc and "$TQTDIR"/bin/uic or add "$TQTDIR"/bin to your PATH and run moc and uic. If you use qmake the appropriate lines will be added to your Makefiles so that uic and moc will be executed as required. @@ -81,7 +81,7 @@ appropriate lines will be added to your Makefiles so that uic and libraries are usually located in the lib subdirectory of TQt distributions. Care must be taken to link with the libraries of the relevant release of TQt. Those with a command-line compiler will typically use options such as -/L%QTDIR%\lib\qt.lib or -L"$QTDIR"/lib -lqt provided QTDIR +/L%TQTDIR%\lib\qt.lib or -L"$TQTDIR"/lib -lqt provided TQTDIR specifies the relevant release of TQt.

Shared libraries - Run time

Users of programs linked with shared TQt libraries need these same @@ -125,7 +125,7 @@ TQt 2.x. They are included in the regular packages of TQt 3.x (qt3 or similar) and TQt 2.x (qt2 or similar).

Just install the packages, qt2, qt3, and qt3-dev. You may -need to set the environment variable QTDIR to point to TQt 3.x. +need to set the environment variable TQTDIR to point to TQt 3.x.

Developers building for two versions of TQt on Unix - TQt sources

@@ -143,14 +143,14 @@ and TQt 2.x to build programs, $ cd /opt $ gunzip -c \c qt-x11-2.3.1.tar.gz | tar xf - $ cd qt-2.3.1 -$ setenv QTDIR /opt/qt-2.3.1 +$ setenv TQTDIR /opt/qt-2.3.1 $ configure [options] $ make $ cd /opt $ gunzip -c qt-x11-free-3.0.0.tar.gz | tar xf - $ cd qt-3.0.0 -$ setenv QTDIR /opt/qt-3.0.0 +$ setenv TQTDIR /opt/qt-3.0.0 $ configure [options] $ make @@ -172,19 +172,19 @@ ln -s /opt/qt-3.0.0/lib/libtqui.so.1 .

To develop with TQt 2.x use: 

-setenv QTDIR /opt/qt-2.3.1
-setenv PATH ${QTDIR}/bin:${PATH}
+setenv TQTDIR /opt/qt-2.3.1
+setenv PATH ${TQTDIR}/bin:${PATH}

To develop with TQt 3.x use: 

-setenv QTDIR /opt/qt-3.0.0
-setenv PATH ${QTDIR}/bin:${PATH}
+setenv TQTDIR /opt/qt-3.0.0
+setenv PATH ${TQTDIR}/bin:${PATH}
-

Setting QTDIR ensures that the proper resources are used, such as the +

Setting TQTDIR ensures that the proper resources are used, such as the documentation appropriate to the version of TQt you're using. Also -your Makfiles may refer to "$QTDIR"/include and "$QTDIR"/lib to +your Makfiles may refer to "$TQTDIR"/include and "$TQTDIR"/lib to include the proper header files and link with the proper libraries. Setting the PATH ensures that the proper version of moc and other tools is being used. diff --git a/doc/html/customstyles.html b/doc/html/customstyles.html index 560a4a7b8..b4b231278 100644 --- a/doc/html/customstyles.html +++ b/doc/html/customstyles.html @@ -192,7 +192,7 @@ you to recompile. The TQt Plugin system makes it possible to create styles as plugins. Styles created as plugins are loaded as shared objects at runtime by TQt itself. Please refer to the TQt Plugin documentation for more information on how to go about creating a style plugin. -

Compile your plugin and put it into $QTDIR/plugins/styles. We now have +

Compile your plugin and put it into $TQTDIR/plugins/styles. We now have a pluggable style that TQt can load automatically. To use your new style with existing applications, simply start the application with the following argument: diff --git a/doc/html/demo-example.html b/doc/html/demo-example.html index 8a61c2a0d..1b14b03bb 100644 --- a/doc/html/demo-example.html +++ b/doc/html/demo-example.html @@ -36,7 +36,7 @@ body { background: #ffffff; color: black; } This program shows off some of TQt's widgets and functionality. It isn't intended as a code example, but rather as a single application that you can run to see many of TQt's features. -

See $QTDIR/examples/demo for the source code. +

See $TQTDIR/examples/demo for the source code.

See also Examples. diff --git a/doc/html/designer-manual-6.html b/doc/html/designer-manual-6.html index dfa747a96..b21aa1652 100644 --- a/doc/html/designer-manual-6.html +++ b/doc/html/designer-manual-6.html @@ -169,10 +169,10 @@ CONFIG += qt warn_on release TARGET = receiver SOURCES += main.cpp unix:LIBS += -ltqui -win32:LIBS += $(QTDIR)/lib/tqui.lib +win32:LIBS += $(TQTDIR)/lib/tqui.lib FORMS = mainform.ui LANGUAGE = C++ -INCLUDEPATH += $(QTDIR)/tools/designer/uilib +INCLUDEPATH += $(TQTDIR)/tools/designer/uilib

We do not include the creditformbase.ui file since this file will be read at runtime, as we'll see shortly. We must include the tqui library since the functionality we require is not part of the standard TQt library.

Creating main.cpp

diff --git a/doc/html/dragdrop-example.html b/doc/html/dragdrop-example.html index ba1430e71..064555707 100644 --- a/doc/html/dragdrop-example.html +++ b/doc/html/dragdrop-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; }

This program demonstrates TQt's drag and drop functionality. -

See $QTDIR/examples/dragdrop for the source code. +

See $TQTDIR/examples/dragdrop for the source code.

See also Examples. diff --git a/doc/html/emb-classes.html b/doc/html/emb-classes.html index b6dae6467..385b96317 100644 --- a/doc/html/emb-classes.html +++ b/doc/html/emb-classes.html @@ -99,7 +99,7 @@ indicates inheritance.

TQFontManager

There is one of these per application. At application startup time it -reads the font definition file from $QTDIR/etc/fonts/fontdir (or /usr/local/etc/qt-embedded/fonts/fontdir if QTDIR is undefined). It +reads the font definition file from $TQTDIR/etc/fonts/fontdir (or /usr/local/etc/qt-embedded/fonts/fontdir if TQTDIR is undefined). It keeps track of all font information and maintains a cache of rendered fonts. It also creates the font factories: TQFontManager::TQFontManager is the place to add constructors for new factories. It provides a diff --git a/doc/html/emb-envvars.html b/doc/html/emb-envvars.html index 78e0fa946..5156acab7 100644 --- a/doc/html/emb-envvars.html +++ b/doc/html/emb-envvars.html @@ -53,9 +53,9 @@ VNC. Transformed displays have a special format: within the specification should be a multiple of 90 degrees rotation specified as Rot<x>, for instance Transformed:Rot90.

-
QTDIR +TQTDIR If defined this tells TQt/Embedded to where to find its fonts: -fontdir should be in $QTDIR/etc/fonts/. If undefined it's assumed +fontdir should be in $TQTDIR/etc/fonts/. If undefined it's assumed to be /usr/local/qt-embedded
TQWS_SIZE diff --git a/doc/html/emb-fonts.html b/doc/html/emb-fonts.html index 60f7b042a..f9faed9ac 100644 --- a/doc/html/emb-fonts.html +++ b/doc/html/emb-fonts.html @@ -97,7 +97,7 @@ font uses over 1 MB of memory.

The font definition file

When TQt/Embedded applications run, they look for a file called -$QTDIR/lib/fonts/fontdir or +$TQTDIR/lib/fonts/fontdir or /usr/local/qt-embedded/lib/fonts/fontdir. This file defines the fonts available to the application. It has the following format:

diff --git a/doc/html/emb-install.html b/doc/html/emb-install.html index b9c336727..9d2d43349 100644 --- a/doc/html/emb-install.html +++ b/doc/html/emb-install.html @@ -48,7 +48,7 @@ Replace VERSION with the TQt/Embedded version number throughout.
  • Compile the TQt/Embedded library and examples. 

         cd ~/qt-embedded-commercial-VERSION
-    export QTDIR=~/qt-embedded-commercial-VERSION
+    export TQTDIR=~/qt-embedded-commercial-VERSION
     ./configure
     make
    @@ -70,7 +70,7 @@ as a starting point. a little-endian machine (e.g. x86) for a big-endian processor (e.g. PowerPC) will use the host's endianness instead of the target's. Workaround: after running configure, and before running -make, edit $QTDIR/include/ntqconfig.h and change the definition of +make, edit $TQTDIR/include/ntqconfig.h and change the definition of Q_BYTE_ORDER.

  • Enable framebuffer support.

    You may need to recompile your kernel to enable the framebuffer. diff --git a/doc/html/emb-running.html b/doc/html/emb-running.html index c6ac9db94..681ed217b 100644 --- a/doc/html/emb-running.html +++ b/doc/html/emb-running.html @@ -45,17 +45,17 @@ and no master process is running. If you do not have a working Linux framebuffer you can use the TQt/Embedded virtual framebuffer, or you can run TQt/Embedded as a VNC server. -

    Change to a Linux console and select an example to run, e.g. examples/widgets. Make sure $QTDIR is set to the directory where you -installed TQt/Embedded and add the $QTDIR/lib directory to +

    Change to a Linux console and select an example to run, e.g. examples/widgets. Make sure $TQTDIR is set to the directory where you +installed TQt/Embedded and add the $TQTDIR/lib directory to $LD_LIBRARY_PATH, e.g.: 

    -export QTDIR=$HOME/qt-VERSION
-export LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
+export TQTDIR=$HOME/qt-VERSION
+export LD_LIBRARY_PATH=$TQTDIR/lib:$LD_LIBRARY_PATH

    Run the application with the -qws option: 

    -cd $QTDIR/examples/widgets
+cd $TQTDIR/examples/widgets
 ./widgets -qws
    diff --git a/doc/html/emb-tqvfb.html b/doc/html/emb-tqvfb.html index a6b662616..caeb0ffde 100644 --- a/doc/html/emb-tqvfb.html +++ b/doc/html/emb-tqvfb.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; }

    The virtual framebuffer allows TQt/Embedded programs to be developed on a desktop machine, without switching between consoles and X11. -

    The virtual framebuffer is located in $QTDIR/tools/tqvfb. +

    The virtual framebuffer is located in $TQTDIR/tools/tqvfb.

    Using the Virtual Framebuffer

      diff --git a/doc/html/helpsystem-example.html b/doc/html/helpsystem-example.html index 835e00d21..028ac9403 100644 --- a/doc/html/helpsystem-example.html +++ b/doc/html/helpsystem-example.html @@ -471,7 +471,7 @@ in TQt Assistant.

      The main function is a standard implementation opening the application main window.

      To build the example go to the helpsystem directory -(QTDIR/examples/helpsystem) run qmake to generate the makefile, +(TQTDIR/examples/helpsystem) run qmake to generate the makefile, and use the make tool to build the library.

      diff --git a/doc/html/how-to-learn-ntqt.html b/doc/html/how-to-learn-ntqt.html index 2dcbe46e1..1e8675c1b 100644 --- a/doc/html/how-to-learn-ntqt.html +++ b/doc/html/how-to-learn-ntqt.html @@ -68,7 +68,7 @@ projects. You may also find it useful to browse the source code of the examples that have things in common with your projects. You can also read TQt's source code since this is supplied. -

      If you run the demo application (in $QTDIR/examples/demo) +

      If you run the demo application (in $TQTDIR/examples/demo) you'll see many of TQt's widgets in action.

      TQt comes with extensive documentation, with hypertext cross-references throughout, so you can easily click your way to whatever interests diff --git a/doc/html/i18n.html b/doc/html/i18n.html index 55ca647e6..99e2894c8 100644 --- a/doc/html/i18n.html +++ b/doc/html/i18n.html @@ -361,7 +361,7 @@ source you choose.

      TQt itself contains over 400 strings that will also need to be translated into the languages that you are targeting. You will find -translation files for French and German in $QTDIR/translations as +translation files for French and German in $TQTDIR/translations as well as a template for translating to other languages. (This directory also contains some additional unsupported translations which may be useful.) diff --git a/doc/html/install-mac.html b/doc/html/install-mac.html index 44a8a5cc4..afa1f9933 100644 --- a/doc/html/install-mac.html +++ b/doc/html/install-mac.html @@ -53,7 +53,7 @@ files from the main archive. depending on your shell) in your home directory. Create the file if it is not there already.

        -
      • QTDIR -- the directory in which you're building TQt +
      • TQTDIR -- the directory in which you're building TQt
      • PATH -- to locate the moc program and other TQt tools
      • MANPATH -- to access the TQt man pages
      • LD_LIBRARY_PATH -- for the shared TQt library @@ -62,20 +62,20 @@ file if it is not there already.

        In .profile (if your shell is bash, ksh, zsh or sh), add the following lines: 

        -    QTDIR=/Developer/qt
-    PATH=$QTDIR/bin:$PATH
-    MANPATH=$QTDIR/man:$MANPATH
-    DYLD_LIBRARY_PATH=$QTDIR/lib:$DYLD_LIBRARY_PATH
+    TQTDIR=/Developer/qt
+    PATH=$TQTDIR/bin:$PATH
+    MANPATH=$TQTDIR/man:$MANPATH
+    DYLD_LIBRARY_PATH=$TQTDIR/lib:$DYLD_LIBRARY_PATH
 
-    export QTDIR PATH MANPATH DYLD_LIBRARY_PATH
+    export TQTDIR PATH MANPATH DYLD_LIBRARY_PATH

        In .login (in case your shell is csh or tcsh), add the following lines: 

        -    setenv QTDIR /Developer/qt
-    setenv PATH $QTDIR/bin:$PATH
-    setenv MANPATH $QTDIR/man:$MANPATH
-    setenv DYLD_LIBRARY_PATH $QTDIR/lib:$DYLD_LIBRARY_PATH
+    setenv TQTDIR /Developer/qt
+    setenv PATH $TQTDIR/bin:$PATH
+    setenv MANPATH $TQTDIR/man:$MANPATH
+    setenv DYLD_LIBRARY_PATH $TQTDIR/lib:$DYLD_LIBRARY_PATH

        After you have done this, you will need to login again, or @@ -87,7 +87,7 @@ the tutorial and the tools (e.g. TQt Designer) as follows.

        Type: 

        -    cd $QTDIR
+    cd $TQTDIR
     ./configure
        @@ -108,8 +108,8 @@ libraries in a directory where they can be found. We recommend making these symbolic links (if you have configured TQt with -thread please change the libtqt below with libtqt-mt): 

        -    ln -sf $QTDIR/lib/libtqt.3.dylib /usr/lib
-    ln -sf $QTDIR/lib/libtqui.1.dylib /usr/lib
+    ln -sf $TQTDIR/lib/libtqt.3.dylib /usr/lib
+    ln -sf $TQTDIR/lib/libtqui.1.dylib /usr/lib

        You may need to have 'administrator' access to do this, (in which @@ -120,14 +120,14 @@ a user install (rather than system install) of the libraries you can do (if you have configured TQt with -thread please change the libtqt below with libtqt-mt): 

        -    ln -sf $QTDIR/lib/libtqt.3.dylib $HOME/lib
-    ln -sf $QTDIR/lib/libtqui.1.dylib $HOME/lib
+    ln -sf $TQTDIR/lib/libtqt.3.dylib $HOME/lib
+    ln -sf $TQTDIR/lib/libtqui.1.dylib $HOME/lib

    That's all! TQt is now installed. TQt's documentation can be read with TQt Assistant or by any web browser; the contents page is -$QTDIR/doc/html/index.html. +$TQTDIR/doc/html/index.html.

    diff --git a/doc/html/install-x11.html b/doc/html/install-x11.html index 37823e838..8132de2a8 100644 --- a/doc/html/install-x11.html +++ b/doc/html/install-x11.html @@ -54,7 +54,7 @@ files from the main archive. depending on your shell) in your home directory. Create the file if it is not there already.

      -
    • QTDIR -- the directory in which you're building TQt +
    • TQTDIR -- the directory in which you're building TQt
    • PATH -- to locate the moc program and other TQt tools
    • MANPATH -- to access the TQt man pages
    • LD_LIBRARY_PATH -- for the shared TQt library @@ -63,24 +63,24 @@ file if it is not there already.

      In .profile (if your shell is bash, ksh, zsh or sh), add the following lines: 

      -    QTDIR=/usr/local/qt
-    PATH=$QTDIR/bin:$PATH
-    MANPATH=$QTDIR/man:$MANPATH
-    LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
+    TQTDIR=/usr/local/qt
+    PATH=$TQTDIR/bin:$PATH
+    MANPATH=$TQTDIR/man:$MANPATH
+    LD_LIBRARY_PATH=$TQTDIR/lib:$LD_LIBRARY_PATH
 
-    export QTDIR PATH MANPATH LD_LIBRARY_PATH
+    export TQTDIR PATH MANPATH LD_LIBRARY_PATH

      In .login (in case your shell is csh or tcsh), add the following lines: 

      -    setenv QTDIR /usr/local/qt
-    setenv PATH $QTDIR/bin:$PATH
-    setenv MANPATH $QTDIR/man:$MANPATH
-    setenv LD_LIBRARY_PATH $QTDIR/lib:$LD_LIBRARY_PATH
+    setenv TQTDIR /usr/local/qt
+    setenv PATH $TQTDIR/bin:$PATH
+    setenv MANPATH $TQTDIR/man:$MANPATH
+    setenv LD_LIBRARY_PATH $TQTDIR/lib:$LD_LIBRARY_PATH

      After you have done this, you will need to login again, or -re-source the profile before continuing, so that at least $QTDIR +re-source the profile before continuing, so that at least $TQTDIR is set. The installation will give an error message and not proceed otherwise.

      On AIX set LIBPATH and on HP-UX set SHLIB_PATH instead of LD_LIBRARY_PATH. diff --git a/doc/html/netscape-plugin.html b/doc/html/netscape-plugin.html index ff72f4d4e..3e5c728fc 100644 --- a/doc/html/netscape-plugin.html +++ b/doc/html/netscape-plugin.html @@ -52,7 +52,7 @@ the ActiveTQt Framework to develop plugi

      1. Download the Plugin SDK from Netscape, and copy the following files from there to -$QTDIR/extensions/nsplugin/src +$TQTDIR/extensions/nsplugin/src
        • common/npwin.cpp
        • common/npunix.c diff --git a/doc/html/opengl-box-example.html b/doc/html/opengl-box-example.html index 36393d0fd..583c59a0f 100644 --- a/doc/html/opengl-box-example.html +++ b/doc/html/opengl-box-example.html @@ -37,7 +37,7 @@ This example demonstrates how to use OpenGL in TQt.

          Essentially, all you do is put your OpenGL code in a class inherited from TQGLWidget. This class may then be used like any other TQt widget, including the use of signals and slots and geometry management. -

          See $QTDIR/examples/opengl/box for the source code. +

          See $TQTDIR/examples/opengl/box for the source code.

          See also OpenGL Examples. diff --git a/doc/html/opengl-gear-example.html b/doc/html/opengl-gear-example.html index 5e3b221c8..eb8ab85b2 100644 --- a/doc/html/opengl-gear-example.html +++ b/doc/html/opengl-gear-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; }

          This example demonstrates how to use OpenGL display lists. -

          See $QTDIR/examples/opengl/gear for the source code. +

          See $TQTDIR/examples/opengl/gear for the source code.

          See also OpenGL Examples. diff --git a/doc/html/opengl-overlay-example.html b/doc/html/opengl-overlay-example.html index 16ab9e1d3..ed655bd11 100644 --- a/doc/html/opengl-overlay-example.html +++ b/doc/html/opengl-overlay-example.html @@ -39,7 +39,7 @@ operation, and rubber-band drawing in the overlay plane. Using the overlay has the advantage that the rubber-band may be drawn and erased without damaging the image in the main plane, so costly redraws are avoided. -

          See $QTDIR/examples/opengl/overlay for the source code. +

          See $TQTDIR/examples/opengl/overlay for the source code.

          See also OpenGL Examples. diff --git a/doc/html/opengl-overlay-x11-example.html b/doc/html/opengl-overlay-x11-example.html index aed2f05c0..399186586 100644 --- a/doc/html/opengl-overlay-x11-example.html +++ b/doc/html/opengl-overlay-x11-example.html @@ -40,7 +40,7 @@ following is a discussion on how to use non-TQGL widgets in overlay planes.

          Overlayrubber: An example program showing how to use TQt and TQt OpenGL Extension with X11 overlay visuals. -

          See $QTDIR/examples/opengl/overlay_x11 for the source code. +

          See $TQTDIR/examples/opengl/overlay_x11 for the source code.

          Background information for this example can be found in the information on overlays.

          The example program has three main parts: diff --git a/doc/html/opengl-pixmap-example.html b/doc/html/opengl-pixmap-example.html index df307db16..1ad2a1164 100644 --- a/doc/html/opengl-pixmap-example.html +++ b/doc/html/opengl-pixmap-example.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; }

          This example program is an extension of the OpenGL Box example.

          It demonstrates how to render OpenGL into a TQPixmap. -

          See $QTDIR/examples/opengl/glpixmap for the source code. +

          See $TQTDIR/examples/opengl/glpixmap for the source code.

          See also OpenGL Examples. diff --git a/doc/html/opengl-sharedbox-example.html b/doc/html/opengl-sharedbox-example.html index 28166c321..a8c346f19 100644 --- a/doc/html/opengl-sharedbox-example.html +++ b/doc/html/opengl-sharedbox-example.html @@ -36,7 +36,7 @@ body { background: #ffffff; color: black; } This example program is an extension of the Box example.

          It demonstrates how to use OpenGL display list sharing with TQGLWidgets. -

          See $QTDIR/examples/opengl/sharedbox for the source code. +

          See $TQTDIR/examples/opengl/sharedbox for the source code.

          See also OpenGL Examples. diff --git a/doc/html/opengl-texture-example.html b/doc/html/opengl-texture-example.html index b3670df3b..f6970aa16 100644 --- a/doc/html/opengl-texture-example.html +++ b/doc/html/opengl-texture-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; }

          This example program demonstrates how to use OpenGL 2D textures. -

          See $QTDIR/examples/opengl/texture for the source code. +

          See $TQTDIR/examples/opengl/texture for the source code.

          See also OpenGL Examples. diff --git a/doc/html/plugins-howto.html b/doc/html/plugins-howto.html index 1e91156d4..7bb3a2dcd 100644 --- a/doc/html/plugins-howto.html +++ b/doc/html/plugins-howto.html @@ -128,7 +128,7 @@ must be reimplemented for each type of plugin. because plugins are stored in the standard plugin subdirectories. Because of this applications don't require any code to find and load plugins, since TQt handles them automatically. -

          The default directory for plugins is QTDIR/plugins*, +

          The default directory for plugins is TQTDIR/plugins*, with each type of plugin in a subdirectory for that type, e.g. styles. If you want your applications to use plugins and you don't want to use the standard plugins path, have your installation process determine the path you want to use for the plugins, and save the path, @@ -143,9 +143,9 @@ compile it in with the application, or to compile it into a DLL (or other library. If you want the plugin to be loadable then one approach is to create a subdirectory under the application, e.g. appdir/plugins/designer, and place the plugin in that directory.

          For TQt Designer, you may need to -call TQApplication::addLibraryPath("QTDIR/plugins/designer") to load +call TQApplication::addLibraryPath("TQTDIR/plugins/designer") to load your TQt Designer plugins. -

          * All references to QTDIR refer to the path +

          * All references to TQTDIR refer to the path where TQt was installed.

          Loading and Verifying Plugins

          diff --git a/doc/html/porting.html b/doc/html/porting.html index e5ca33762..58d1a0598 100644 --- a/doc/html/porting.html +++ b/doc/html/porting.html @@ -497,7 +497,7 @@ published the internal data structure. work without problems. Applications that worked in terms of lines may require some porting.

          The source code for the old 2.x version of TQMultiLineEdit can be found -in $QTDIR/src/attic/qtmultilineedit.h/cpp. Note that the class has +in $TQTDIR/src/attic/qtmultilineedit.h/cpp. Note that the class has been renamed to TQtMultiLineEdit to avoid name clashes. If you really need to keep compatibility with the old TQMultiLineEdit, simply include this class in your project and rename TQMultiLineEdit to @@ -643,7 +643,7 @@ or a plain TQPtrList instead.

          The TQTableView class has been obsoleted and is no longer a part of the TQt API. Either use the powerful TQTable class or the simplistic TQGridView in any new code you create. If you really need the old table -view for compatibility you can find it in $QTDIR/src/attic/qttableview.{cpp,h}. Note that the class has been +view for compatibility you can find it in $TQTDIR/src/attic/qttableview.{cpp,h}. Note that the class has been renamed from TQTableView to TQtTableView to avoid name clashes. To use it, simply include it in your project and rename TQTableView to TQtTableView throughout. diff --git a/doc/html/qaxcontainer.html b/doc/html/qaxcontainer.html index d944ac0a5..d764b5baf 100644 --- a/doc/html/qaxcontainer.html +++ b/doc/html/qaxcontainer.html @@ -95,11 +95,11 @@ that use standard ActiveX controls to provide high level user interface functionality are provided.

          Building the library

          -

          In the activeqt directory (usually QTDIR/extensions/activeqt) +

          In the activeqt directory (usually TQTDIR/extensions/activeqt) enter the container subdirectory and run qmake to generate the makefile, and use the make tool (nmake for VC++, make for Borland) to build the library. The library qaxcontainer.lib will be linked -into QTDIR/lib. +into TQTDIR/lib.

          If you have a shared configuration of TQt enter the plugin subdirectory and run qmake and your make tool to build a plugin that integrates the TQAxWidget class into TQt Designer. diff --git a/doc/html/qaxserver.html b/doc/html/qaxserver.html index 8ab281cb0..33eb8b3f4 100644 --- a/doc/html/qaxserver.html +++ b/doc/html/qaxserver.html @@ -158,11 +158,11 @@ ActiveX control. of ActiveX controls are provided.

          Building the library

          -

          In the activeqt directory (usually QTDIR/extensions/activeqt) +

          In the activeqt directory (usually TQTDIR/extensions/activeqt) enter the control subdirectory and run qmake to generate the makefile, and use the make tool (nmake for VC++, make for Borland) to build the library. The library qaxserver.lib will be linked into -QTDIR/lib. +TQTDIR/lib.

          Using the library

          To turn a standard TQt application into an ActiveX server using the diff --git a/doc/html/qmake-manual-2.html b/doc/html/qmake-manual-2.html index e9c0d2b1b..4ee0895bd 100644 --- a/doc/html/qmake-manual-2.html +++ b/doc/html/qmake-manual-2.html @@ -41,8 +41,8 @@ body { background: #ffffff; color: black; }

          aix-64 hpux-cc irix-032 netbsd-g++ solaris-cc unixware7-g++ aix-g++ hpux-g++ linux-cxx openbsd-g++ solaris-g++ win32-borland aix-xlc hpux-n64 linux-g++ openunix-cc sunos-g++ win32-g++ bsdi-g++ hpux-o64 linux-icc qnx-g++ tru64-cxx win32-msvc dgux-g++ hurd-g++ linux-kcc reliant-64 tru64-g++ win32-watc freebsd-g++ irix-64 macx-pbuilder reliant-cds ultrix-g++ win32-visa hpux-acc irix-g++ macx-g++ sco-g++ unixware-g hpux-acc irix-n32 solaris-64 unixware7-cc

          The environment variable should be set to qws/envvar where envvar is one of the following:

          linux-arm-g++ linux-generic-g++ linux-mips-g++ linux-x86-g++ linux-freebsd-g++ linux-ipaq-g++ linux-solaris-g++ qnx-rtp-g++

          -

        • QTDIR
          This must be set to where TQt is (or will be) installed. For example, c:\qt and \local\qt

          -

        Once the environment variables are set go into the qmake directory, $QTDIR/qmake, e.g. C:\qt\qmake. Now run make or nmake depending on your compiler.

        +

      2. TQTDIR
        This must be set to where TQt is (or will be) installed. For example, c:\qt and \local\qt

        +

    Once the environment variables are set go into the qmake directory, $TQTDIR/qmake, e.g. C:\qt\qmake. Now run make or nmake depending on your compiler.

    When the make has completed, qmake is ready for use.

    [Prev: Introduction to qmake] [Home] [Next: The 10 minute guide to using qmake]

    diff --git a/doc/html/qmake-manual-8.html b/doc/html/qmake-manual-8.html index bfa3cb044..b22e6dce5 100644 --- a/doc/html/qmake-manual-8.html +++ b/doc/html/qmake-manual-8.html @@ -383,7 +383,7 @@ app {

    This list will go before all builtin dependencies.

    QMAKE_INCDIR_OPENGL

    This variable contains the location of OpenGL header files to be added to INCLUDEPATH when building an application with OpenGL support. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.

    -
    QMAKE_INCDIR_QT
    +
    QMAKE_INCDIR_TQT

    This variable contains the location of all known header file paths to be added to INCLUDEPATH when building a TQt application. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.

    QMAKE_INCDIR_THREAD

    This variable contains the location of all known header file paths to be added to INCLUDEPATH when building a multi-threaded application. The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.

    @@ -430,7 +430,7 @@ app {

    This variable contains the list of all directories to look in to resolve dependencies. This will be used when crawling through 'included' files.

    QMAKE_LIBDIR_OPENGL

    This variable contains the location of the OpenGL library directory.The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.

    -
    QMAKE_LIBDIR_QT
    +
    QMAKE_LIBDIR_TQT

    This variable contains the location of the TQt library directory.The value of this variable is typically handled by qmake or qmake.conf and rarely needs to be modified.

    QMAKE_LIBDIR_X11

    This is used on Unix platforms only

    @@ -571,7 +571,7 @@ OPTIONS = standard custom

    This function will test if file exists. If the file exists, then it will succeed; otherwise it will fail. You can specify a regular expression in file and it will succeed if any file matches the regular expression specified.

    For example:

    -exists( $(QTDIR)/lib/libtqt-mt* ) {
+exists( $(TQTDIR)/lib/libtqt-mt* ) {
       message( "Configuring for multi-threaded TQt..." )
       CONFIG += thread
 }
@@ -645,7 +645,7 @@ QMAKE_VERS = $$[QMAKE_VERSION]
 
    qmake requires a platform and compiler description file which contains many default values used to generate appropriate makefiles. The standard TQt distribution comes with many of these files, located in the 'mkspecs' subdirectory of the TQt installation.
    
 
    The QMAKESPEC environment variable can contain any of the following:
    
 
    • A complete path to a directory containing a qmake.conf file. In this case qmake will open the qmake.conf file from within that directory. If the file does not exist, qmake will exit with an error.
      
-
    • The name of a platform-compiler combination. In this case, qmake will search in the directory specified by the QTDIR environment variable.
      
+
    • The name of a platform-compiler combination. In this case, qmake will search in the directory specified by the TQTDIR environment variable.
      
 
    Note: the QMAKESPEC path will automatically be added to the INCLUDEPATH system variable.
    
 
    INSTALLS
    
 
    It is common on UNIX to be able to install from the same utility as you build with (e.g make install). For this qmake has introduce the concept of an install set. The notation for this is quite simple, first you fill in an "object" in qmake for example:
    
diff --git a/doc/html/sql-driver.html b/doc/html/sql-driver.html
index e6f6b3d50..6c984250c 100644
--- a/doc/html/sql-driver.html
+++ b/doc/html/sql-driver.html
@@ -135,7 +135,7 @@ install a package which is usually called "mysql-devel".
 header files and shared libraries (here it is assumed that MySQL is
 installed in /usr/local) and run make:
 
     
    -cd $QTDIR/plugins/src/sqldrivers/mysql
+cd $TQTDIR/plugins/src/sqldrivers/mysql
 qmake -o Makefile "INCLUDEPATH+=/usr/local/include" "LIBS+=-L/usr/local/lib -lmysqlclient" mysql.pro
 make
 
    
@@ -147,7 +147,7 @@ choose "Custom Install". Install the "Libs & Include Files" Module.
 Build the plugin as follows (here it is assumed that MySQL is
 installed in C:\MYSQL):
 
     
    -cd %QTDIR%\plugins\src\sqldrivers\mysql
+cd %TQTDIR%\plugins\src\sqldrivers\mysql
 qmake -o Makefile "INCLUDEPATH+=C:\MYSQL\INCLUDE" "LIBS+=C:\MYSQL\LIB\OPT\LIBMYSQL.LIB" mysql.pro
 nmake
 
    
@@ -175,7 +175,7 @@ columns, you have to use a forward only query to select LOB fields
 (see TQSqlQuery::setForwardOnly()).
 
     Inserting BLOBs should be done using either a prepared query where the
 BLOBs are bound to placeholders, or TQSqlCursor which uses a prepared
-query to do this internally (see $QTDIR/examples/sql/blob).
+query to do this internally (see $TQTDIR/examples/sql/blob).
 
     
     Know problems 
 
    
 
     When a query is in forward only mode a call to TQSqlQuery::last() will
@@ -195,21 +195,21 @@ libraries (it is assumed that the variable $ORACLE_HOME points to
 the directory where Oracle is installed) and run make:
 
     If you are using Oracle 8:
 
    -cd $QTDIR/plugins/src/sqldrivers/oci
+cd $TQTDIR/plugins/src/sqldrivers/oci
 qmake -o Makefile "INCLUDEPATH+=$ORACLE_HOME/rdbms/public $ORACLE_HOME/rdbms/demo" "LIBS+=-L$ORACLE_HOME/lib -lclntsh -lwtc8" oci.pro
 make
 
    
  
 
     For Oracle version 9:
 
    -cd $QTDIR/plugins/src/sqldrivers/oci
+cd $TQTDIR/plugins/src/sqldrivers/oci
 qmake -o Makefile "INCLUDEPATH+=$ORACLE_HOME/rdbms/public $ORACLE_HOME/rdbms/demo" "LIBS+=-L$ORACLE_HOME/lib -lclntsh -lwtc9" oci.pro
 make
 
    
  
 
     For Oracle version 10:
 
    -cd $QTDIR/plugins/src/sqldrivers/oci
+cd $TQTDIR/plugins/src/sqldrivers/oci
 qmake -o Makefile "INCLUDEPATH+=$ORACLE_HOME/rdbms/public $ORACLE_HOME/rdbms/demo" "LIBS+=-L$ORACLE_HOME/lib -lclntsh" oci.pro
 make
 
    
@@ -230,7 +230,7 @@ installed in C:\oracle):
 
     
     set INCLUDE=%INCLUDE%;c:\oracle\oci\include
 set LIB=%LIB%;c:\oracle\oci\lib\msvc
-cd %QTDIR%\plugins\src\sqldrivers\oci
+cd %TQTDIR%\plugins\src\sqldrivers\oci
 qmake -o Makefile oci.pro
 nmake
 
    
@@ -288,7 +288,7 @@ You need the unixODBC header files and shared libraries.
 libraries (here it is assumed that unixODBC is installed in
 /usr/local/unixODBC) and run make:
 
     
    -cd $QTDIR/plugins/src/sqldrivers/odbc
+cd $TQTDIR/plugins/src/sqldrivers/odbc
 qmake "INCLUDEPATH+=/usr/local/unixODBC/include" "LIBS+=-L/usr/local/unixODBC/lib -lodbc"
 make
 
    
@@ -298,7 +298,7 @@ make
 
     The ODBC header and include files should already be installed in the
 right directories. You just have to build the plugin as follows:
 
     
    -cd %QTDIR%\plugins\src\sqldrivers\odbc
+cd %TQTDIR%\plugins\src\sqldrivers\odbc
 qmake -o Makefile odbc.pro
 nmake
 
    
@@ -352,7 +352,7 @@ header files that are usually not a part of the binary distribution.
 libraries, run qmake the following way (assuming that the
 PostgreSQL sources can be found in /usr/src/psql):
 
     
    -cd $QTDIR/plugins/src/sqldrivers/psql
+cd $TQTDIR/plugins/src/sqldrivers/psql
 qmake -o Makefile "INCLUDEPATH+=/usr/src/psql/src/include /usr/src/psql/src/interfaces/libpq" "LIBS+=-L/usr/lib -lpq" psql.pro
 make
 
    
@@ -363,7 +363,7 @@ make
 the PostgreSQL documentation. Assuming the PostgreSQL sources resides
 in C:\psql, build the plugin as follows:
 
     
    -cd %QTDIR%\plugins\src\sqldrivers\psql
+cd %TQTDIR%\plugins\src\sqldrivers\psql
 qmake -o Makefile "INCLUDEPATH+=C:\psql\src\include C:\psql\src\interfaces\libpq" psql.pro
 nmake
 
    
@@ -391,7 +391,7 @@ Note for Linux users: Get the Open Client RPM from
 point to the directory where you installed the client library and
 execute qmake:
 
     
    -cd $QTDIR/plugins/src/sqldrivers/tds
+cd $TQTDIR/plugins/src/sqldrivers/tds
 qmake -o Makefile "INCLUDEPATH=$SYBASE/include" "LIBS=-L$SYBASE/lib -lsybdb"
 make
 
    
@@ -401,14 +401,14 @@ make
 
     You can either use the DB-Library supplied by Microsoft or the Sybase
 Open Client (http://www.sybase.com). You must include NTWDBLIB.LIB to build the plugin:
 
     
    -cd %QTDIR%\plugins\src\sqldrivers\tds
+cd %TQTDIR%\plugins\src\sqldrivers\tds
 qmake -o Makefile "LIBS+=NTWDBLIB.LIB" tds.pro
 nmake
 
    
  
 
     By default the Microsoft library is used on Windows, if you want to force
 the use of the Sybase Open Client, you must define
-Q_USE_SYBASE in %QTDIR%\src\sql\drivers\tds\qsql_tds.cpp.
+Q_USE_SYBASE in %TQTDIR%\src\sql\drivers\tds\qsql_tds.cpp.
 
     
 
     TQDB2 - IBM DB2 Driver (v7.1 or higher)
 
    
@@ -426,7 +426,7 @@ in DB2 (see TQSqlQuery::setForwardOnly
 
     
     How to build the plugin on Unix/Linux
 
    
 
     
    -cd $QTDIR/plugins/src/sqldrivers/db2
+cd $TQTDIR/plugins/src/sqldrivers/db2
 qmake -o Makefile "INCLUDEPATH+=$DB2DIR/include" "LIBS+=-L$DB2DIR/lib -ldb2"
 make
 
    
@@ -436,7 +436,7 @@ make
 
     The DB2 header and include files should already be installed in the
 right directories. You just have to build the plugin as follows:
 
     
    -cd %QTDIR%\plugins\src\sqldrivers\db2
+cd %TQTDIR%\plugins\src\sqldrivers\db2
 qmake -o Makefile "INCLUDEPATH+=<DB2 home>/sqllib/include" "LIBS+=<DB2 home>/sqllib/lib/db2cli.lib"
 nmake
 
    
@@ -468,7 +468,7 @@ directly into the TQt library).
 build it manually (replace $SQLITE by the directory where SQLite
 resides):
 
     
    -cd $QTDIR/plugins/src/sqldrivers/sqlite
+cd $TQTDIR/plugins/src/sqldrivers/sqlite
 qmake -o Makefile "INCLUDEPATH+=$SQLITE/include" "LIBS+=-L$SQLITE/lib -lsqlite"
 make
 
    
@@ -501,7 +501,7 @@ or the free edition of Interbase.
 
     The following assumes Interbase or Firebird is installed in
 /opt/interbase:
 
     
    -cd $QTDIR/plugins/src/sqldrivers/ibase
+cd $TQTDIR/plugins/src/sqldrivers/ibase
 qmake -o Makefile "INCLUDEPATH+=/opt/interbase/include" "LIBS+=-L/opt/interbase/lib" ibase.pro
 make
 
    
@@ -511,7 +511,7 @@ make
 
     The following assumes Interbase or Firebird is installed in
 C:\interbase:
 
     
    -cd %QTDIR%\plugins\src\sqldrivers\ibase
+cd %TQTDIR%\plugins\src\sqldrivers\ibase
 qmake -o Makefile "INCLUDEPATH+=C:\interbase\include" ibase.pro
 nmake
 
    
@@ -535,8 +535,8 @@ make sure that the following requirements are met:
 
     
      
 
    •  Ensure that you are using a shared TQt library; you cannot use the
 plugins with a static build.
-
    •  Ensure that the environment variable QTDIR points to the right
-directory. Go to the $QTDIR/plugins/sqldrivers directory and
+
    •  Ensure that the environment variable TQTDIR points to the right
+directory. Go to the $TQTDIR/plugins/sqldrivers directory and
 make sure that the plugin exists in that directory.
 
    •  Ensure that the client libraries of the DBMS are available on the 
 system. On Unix, run the command ldd and pass the name of the
@@ -587,8 +587,8 @@ loaded by the TQt library at runtime), the driver must use the
 Q_EXPORT_PLUGIN macro. Read the TQt
 Plugin documentation for more information on this. You can
 also check out how this is done in the SQL plugins that is provided
-with TQt in QTDIR/plugins/src/sqldrivers and
-QTDIR/src/sql/drivers.
+with TQt in TQTDIR/plugins/src/sqldrivers and
+TQTDIR/src/sql/drivers.
 
       The following code can be used as a skeleton for a SQL driver:
 
       
       class TQNullResult : public TQSqlResult
diff --git a/doc/html/tablet-example.html b/doc/html/tablet-example.html
index b8d3a0763..ee49f444c 100644
--- a/doc/html/tablet-example.html
+++ b/doc/html/tablet-example.html
@@ -34,7 +34,7 @@ body { background: #ffffff; color: black; }
    
 
       
 This example shows how to interact with a tablet device.
-
       See $QTDIR/examples/tablet for the source code.
+
       See $TQTDIR/examples/tablet for the source code.
 
      See also Examples.
 
 
diff --git a/doc/html/textedit-example.html b/doc/html/textedit-example.html
index 1ae287e03..6e5f47bbd 100644
--- a/doc/html/textedit-example.html
+++ b/doc/html/textedit-example.html
@@ -37,7 +37,7 @@ This example displays a text editor with the user interface written
 in pure C++. 
 
       A similar example which uses TQt
   Designer to produce the user interface is in the TQt Designer manual.
-
       See $QTDIR/examples/textedit for the source code.
+
       See $TQTDIR/examples/textedit for the source code.
 
       
      See also Examples.
 
 
diff --git a/doc/html/toplevel-example.html b/doc/html/toplevel-example.html
index ec51c6691..9822093be 100644
--- a/doc/html/toplevel-example.html
+++ b/doc/html/toplevel-example.html
@@ -212,7 +212,7 @@ this attribute for toplevel window.
 
       
          }
 
      Finally the window is shown with the new attributes.
 
       To build the example go to the toplevel directory
-(QTDIR/examples/toplevel) 
+(TQTDIR/examples/toplevel) 
 (3) 
 and run qmake to generate the makefile, then use the make tool to
 build the library. 
@@ -225,7 +225,7 @@ The example uses TQGuardedPtr to make sure that
 pointer is reset to zero when the widget object is destroyed 
 due to the WDestructiveClose flag.  Back... 
    • 
 
-We use QTDIR to stand for the directory where TQt is installed.
+We use TQTDIR to stand for the directory where TQt is installed.
  Back...
 
      See also Examples.
 
diff --git a/doc/html/widgets-example.html b/doc/html/widgets-example.html
index ea368d6c0..5ec5c8647 100644
--- a/doc/html/widgets-example.html
+++ b/doc/html/widgets-example.html
@@ -34,10 +34,10 @@ body { background: #ffffff; color: black; }
    
 
       
 This example shows most of TQt's widgets in action. It is similar
-to the demo example in $QTDIR/examples/demo.
+to the demo example in $TQTDIR/examples/demo.
 
       Run the program, then click the right mouse button + Ctrl to
 identify a widget.
-
       See $QTDIR/examples/widgets for the source code.
+
       See $TQTDIR/examples/widgets for the source code.
 
       
      See also Examples.
 
 
-- 
cgit v1.2.1