diff options
Diffstat (limited to 'doc/html')
36 files changed, 112 insertions, 112 deletions
diff --git a/doc/html/assistant-6.html b/doc/html/assistant-6.html index 266490db..d2b42091 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 </pre> <p>See the HelpDemo example in the TQt distribution for a demonstration on how to use <em>TQt Assistant</em> with profiles for your own applications.</p> -<p>When distributing <em>TQt Assistant</em> with your application, you will also need to copy the icon files from the <tt>QTDIR/tools/assistant/images</tt> directory so that <em>TQt Assistant</em> finds its icons.</p> +<p>When distributing <em>TQt Assistant</em> with your application, you will also need to copy the icon files from the <tt>TQTDIR/tools/assistant/images</tt> directory so that <em>TQt Assistant</em> finds its icons.</p> <!-- eof --> <p><address><hr><div align=center> <table width=100% cellspacing=0 border=0><tr> diff --git a/doc/html/commonproblems.html b/doc/html/commonproblems.html index c410232c..5b5c9fd1 100644 --- a/doc/html/commonproblems.html +++ b/doc/html/commonproblems.html @@ -66,13 +66,13 @@ moc-generated object code into your executable. See <a href="moc.html">Using the are usually located in the <tt>include</tt> 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 -<tt>/I%QTDIR%\include</tt> +<tt>/I%TQTDIR%\include</tt> the relevant release of TQt. <p> <dt>Meta Object Compiler and other tools - Compile time <p> <dd>Programmers need to run <em>moc</em> and other tools such as <em>uic</em>. These tools are usually located in the <tt>bin</tt> subdirectory of TQt distributions. -Either run <tt>"$QTDIR"/bin/moc</tt> and <tt>"$QTDIR"/bin/uic</tt> or add <tt>"$QTDIR"/bin</tt> +Either run <tt>"$TQTDIR"/bin/moc</tt> and <tt>"$TQTDIR"/bin/uic</tt> or add <tt>"$TQTDIR"/bin</tt> to your <tt>PATH</tt> and run <a href="moc.html#moc">moc</a> and <tt>uic</tt>. If you use <tt>qmake</tt> the appropriate lines will be added to your Makefiles so that <em>uic</em> and <em>moc</em> will be executed as required. @@ -81,7 +81,7 @@ appropriate lines will be added to your Makefiles so that <em>uic</em> and libraries are usually located in the <tt>lib</tt> 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 -<tt>/L%QTDIR%\lib\qt.lib</tt> or <tt>-L"$QTDIR"/lib</tt> <tt>-lqt</tt> provided <tt>QTDIR</tt> +<tt>/L%TQTDIR%\lib\qt.lib</tt> or <tt>-L"$TQTDIR"/lib</tt> <tt>-lqt</tt> provided <tt>TQTDIR</tt> specifies the relevant release of TQt. <p> <dt>Shared libraries - Run time <p> <dd>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 (<tt>qt3</tt> or similar) and TQt 2.x (<tt>qt2</tt> or similar). <p> </ul> <p> Just install the packages, <tt>qt2</tt>, <tt>qt3</tt>, and <tt>qt3-dev</tt>. You may -need to set the environment variable <tt>QTDIR</tt> to point to TQt 3.x. +need to set the environment variable <tt>TQTDIR</tt> to point to TQt 3.x. <p> <a name="qtsrc"></a> <h3> Developers building for two versions of TQt on Unix - TQt sources </h3> @@ -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 </pre> @@ -172,19 +172,19 @@ ln -s /opt/qt-3.0.0/lib/libtqui.so.1 . <p> </ol> <p> To develop with TQt 2.x use: <p> <pre> -setenv QTDIR /opt/qt-2.3.1 -setenv PATH ${QTDIR}/bin:${PATH} +setenv TQTDIR /opt/qt-2.3.1 +setenv PATH ${TQTDIR}/bin:${PATH} </pre> <p> To develop with TQt 3.x use: <p> <pre> -setenv QTDIR /opt/qt-3.0.0 -setenv PATH ${QTDIR}/bin:${PATH} +setenv TQTDIR /opt/qt-3.0.0 +setenv PATH ${TQTDIR}/bin:${PATH} </pre> -<p> Setting <tt>QTDIR</tt> ensures that the proper resources are used, such as the +<p> Setting <tt>TQTDIR</tt> 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 <tt>"$QTDIR"/include</tt> and <tt>"$QTDIR"/lib</tt> to +your Makfiles may refer to <tt>"$TQTDIR"/include</tt> and <tt>"$TQTDIR"/lib</tt> to include the proper header files and link with the proper libraries. Setting the <tt>PATH</tt> 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 560a4a7b..b4b23127 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 <a href="plugins-howto.html">TQt Plugin</a> documentation for more information on how to go about creating a style plugin. -<p> Compile your plugin and put it into $QTDIR/plugins/styles. We now have +<p> 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 8a61c2a0..1b14b03b 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. -<p> See $QTDIR/examples/demo for the source code. +<p> See $TQTDIR/examples/demo for the source code. <p> <p>See also <a href="examples.html">Examples</a>. <!-- eof --> diff --git a/doc/html/designer-manual-6.html b/doc/html/designer-manual-6.html index dfa747a9..b21aa165 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 </pre> <p>We do <em>not</em> include the <tt>creditformbase.ui</tt> file since this file will be read at runtime, as we'll see shortly. We must include the <tt>tqui</tt> library since the functionality we require is not part of the standard TQt library.</p> <h4><a name="2-2"></a>Creating main.cpp</h4> diff --git a/doc/html/dragdrop-example.html b/doc/html/dragdrop-example.html index ba1430e7..06455570 100644 --- a/doc/html/dragdrop-example.html +++ b/doc/html/dragdrop-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; } <p> This program demonstrates TQt's drag and drop functionality. -<p> See $QTDIR/examples/dragdrop for the source code. +<p> See $TQTDIR/examples/dragdrop for the source code. <p> <p>See also <a href="examples.html">Examples</a>. <!-- eof --> diff --git a/doc/html/emb-classes.html b/doc/html/emb-classes.html index b6dae646..385b9631 100644 --- a/doc/html/emb-classes.html +++ b/doc/html/emb-classes.html @@ -99,7 +99,7 @@ indicates inheritance. <p> <h2> <a href="qfontmanager.html">TQFontManager</a> </h2> <a name="1"></a><p> There is one of these per application. At application startup time it -reads the font definition file from <tt>$QTDIR/etc/fonts/fontdir</tt> (or <tt>/usr/local/etc/qt-embedded/fonts/fontdir</tt> if QTDIR is undefined). It +reads the font definition file from <tt>$TQTDIR/etc/fonts/fontdir</tt> (or <tt>/usr/local/etc/qt-embedded/fonts/fontdir</tt> 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 78e0fa94..5156acab 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. <tr bgcolor="#f0f0f0"> -<td valign="top">QTDIR +<td valign="top">TQTDIR <td valign="top">If defined this tells TQt/Embedded to where to find its fonts: -fontdir should be in <tt>$QTDIR/etc/fonts/</tt>. If undefined it's assumed +fontdir should be in <tt>$TQTDIR/etc/fonts/</tt>. If undefined it's assumed to be <tt>/usr/local/qt-embedded</tt> <tr bgcolor="#d0d0d0"> <td valign="top">TQWS_SIZE diff --git a/doc/html/emb-fonts.html b/doc/html/emb-fonts.html index 60f7b042..f9faed9a 100644 --- a/doc/html/emb-fonts.html +++ b/doc/html/emb-fonts.html @@ -97,7 +97,7 @@ font uses over 1 MB of memory. <p> <h2> The font definition file </h2> <a name="5"></a><p> When TQt/Embedded applications run, they look for a file called -<tt>$QTDIR/lib/fonts/fontdir</tt> or +<tt>$TQTDIR/lib/fonts/fontdir</tt> or <tt>/usr/local/qt-embedded/lib/fonts/fontdir</tt>. This file defines the fonts available to the application. It has the following format: <blockquote> diff --git a/doc/html/emb-install.html b/doc/html/emb-install.html index b9c33672..9d2d4334 100644 --- a/doc/html/emb-install.html +++ b/doc/html/emb-install.html @@ -48,7 +48,7 @@ Replace <tt>VERSION</tt> with the TQt/Embedded version number throughout. <li> Compile the TQt/Embedded library and examples. <p> <pre> cd ~/qt-embedded-commercial-VERSION - export QTDIR=~/qt-embedded-commercial-VERSION + export TQTDIR=~/qt-embedded-commercial-VERSION ./configure make </pre> @@ -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 <tt>$QTDIR/include/ntqconfig.h</tt> and change the definition of +make, edit <tt>$TQTDIR/include/ntqconfig.h</tt> and change the definition of <tt>Q_BYTE_ORDER</tt>. <p> <li> Enable framebuffer support. <p> 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 c6ac9db9..681ed217 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 <a href="emb-tqvfb.html">TQt/Embedded virtual framebuffer</a>, or you can run TQt/Embedded as a <a href="emb-vnc.html">VNC server</a>. -<p> Change to a Linux console and select an example to run, e.g. <tt>examples/widgets</tt>. Make sure $QTDIR is set to the directory where you -installed TQt/Embedded and add the $QTDIR/lib directory to +<p> Change to a Linux console and select an example to run, e.g. <tt>examples/widgets</tt>. 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.: <pre> -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 </pre> <p> Run the application with the <em>-qws</em> option: <p> <pre> -cd $QTDIR/examples/widgets +cd $TQTDIR/examples/widgets ./widgets -qws </pre> diff --git a/doc/html/emb-tqvfb.html b/doc/html/emb-tqvfb.html index a6b66261..caeb0ffd 100644 --- a/doc/html/emb-tqvfb.html +++ b/doc/html/emb-tqvfb.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; } <p> The virtual framebuffer allows TQt/Embedded programs to be developed on a desktop machine, without switching between consoles and X11. -<p> The virtual framebuffer is located in <tt>$QTDIR/tools/tqvfb</tt>. +<p> The virtual framebuffer is located in <tt>$TQTDIR/tools/tqvfb</tt>. <p> <h2> Using the Virtual Framebuffer </h2> <a name="1"></a><p> <ol type=1> diff --git a/doc/html/helpsystem-example.html b/doc/html/helpsystem-example.html index 835e00d2..028ac940 100644 --- a/doc/html/helpsystem-example.html +++ b/doc/html/helpsystem-example.html @@ -471,7 +471,7 @@ in TQt Assistant. <p> The main function is a standard implementation opening the application main window. <p> 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. <hr> diff --git a/doc/html/how-to-learn-ntqt.html b/doc/html/how-to-learn-ntqt.html index 2dcbe46e..1e8675c1 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 <a href="examples.html">examples</a> that have things in common with your projects. You can also read TQt's source code since this is supplied. -<p> If you run the <tt>demo</tt> application (in <tt>$QTDIR/examples/demo</tt>) +<p> If you run the <tt>demo</tt> application (in <tt>$TQTDIR/examples/demo</tt>) you'll see many of TQt's widgets in action. <p> 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 55ca647e..99e2894c 100644 --- a/doc/html/i18n.html +++ b/doc/html/i18n.html @@ -361,7 +361,7 @@ source you choose. <p> <a name="qt-itself"></a> 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 <tt>$QTDIR/translations</tt> as +translation files for French and German in <tt>$TQTDIR/translations</tt> 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 44a8a5cc..afa1f993 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. <p> <ul> -<li> QTDIR -- the directory in which you're building TQt +<li> TQTDIR -- the directory in which you're building TQt <li> PATH -- to locate the <a href="moc.html#moc">moc</a> program and other TQt tools <li> MANPATH -- to access the TQt man pages <li> LD_LIBRARY_PATH -- for the shared TQt library @@ -62,20 +62,20 @@ file if it is not there already. <p> In <tt>.profile</tt> (if your shell is bash, ksh, zsh or sh), add the following lines: <p> <pre> - 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 </pre> <p> In <tt>.login</tt> (in case your shell is csh or tcsh), add the following lines: <p> <pre> - 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 </pre> <p> After you have done this, you will need to login again, or @@ -87,7 +87,7 @@ the tutorial and the tools (e.g. <a href="designer-manual.html">TQt Designer</a>) as follows. <p> Type: <pre> - cd $QTDIR + cd $TQTDIR ./configure </pre> @@ -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): <p> <pre> - 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 </pre> <p> 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): <p> <pre> - 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 </pre> </ol> <p> 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 -<tt>$QTDIR/doc/html/index.html</tt>. +<tt>$TQTDIR/doc/html/index.html</tt>. <p> <!-- eof --> <p><address><hr><div align=center> diff --git a/doc/html/install-x11.html b/doc/html/install-x11.html index 37823e83..8132de2a 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. <p> <ul> -<li> QTDIR -- the directory in which you're building TQt +<li> TQTDIR -- the directory in which you're building TQt <li> PATH -- to locate the <a href="moc.html#moc">moc</a> program and other TQt tools <li> MANPATH -- to access the TQt man pages <li> LD_LIBRARY_PATH -- for the shared TQt library @@ -63,24 +63,24 @@ file if it is not there already. <p> In <tt>.profile</tt> (if your shell is bash, ksh, zsh or sh), add the following lines: <p> <pre> - 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 </pre> <p> In <tt>.login</tt> (in case your shell is csh or tcsh), add the following lines: <p> <pre> - 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 </pre> <p> After you have done this, you will need to login again, or -re-source the profile before continuing, so that at least <tt>$QTDIR</tt> +re-source the profile before continuing, so that at least <tt>$TQTDIR</tt> is set. The installation will give an error message and not proceed otherwise. <p> 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 ff72f4d4..3e5c728f 100644 --- a/doc/html/netscape-plugin.html +++ b/doc/html/netscape-plugin.html @@ -52,7 +52,7 @@ the <a href="activentqt.html#ActiveTQt">ActiveTQt</a> Framework to develop plugi <a name="2"></a><p> <ol type=1> <li> Download the <a href="http://home.netscape.com/comprod/development_partners/plugin_api/index.html">Plugin SDK from Netscape</a>, and copy the following files from there to -<tt>$QTDIR/extensions/nsplugin/src</tt> +<tt>$TQTDIR/extensions/nsplugin/src</tt> <ul> <li> <tt>common/npwin.cpp</tt> <li> <tt>common/npunix.c</tt> diff --git a/doc/html/opengl-box-example.html b/doc/html/opengl-box-example.html index 36393d0f..583c59a0 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. <p> Essentially, all you do is put your OpenGL code in a class inherited from <a href="qglwidget.html">TQGLWidget</a>. This class may then be used like any other TQt widget, including the use of signals and slots and geometry management. -<p> See <tt>$QTDIR/examples/opengl/box</tt> for the source code. +<p> See <tt>$TQTDIR/examples/opengl/box</tt> for the source code. <p> <p>See also <a href="opengl-examples.html">OpenGL Examples</a>. <!-- eof --> diff --git a/doc/html/opengl-gear-example.html b/doc/html/opengl-gear-example.html index 5e3b221c..eb8ab85b 100644 --- a/doc/html/opengl-gear-example.html +++ b/doc/html/opengl-gear-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; } <p> This example demonstrates how to use OpenGL display lists. -<p> See <tt>$QTDIR/examples/opengl/gear</tt> for the source code. +<p> See <tt>$TQTDIR/examples/opengl/gear</tt> for the source code. <p> <p>See also <a href="opengl-examples.html">OpenGL Examples</a>. <!-- eof --> diff --git a/doc/html/opengl-overlay-example.html b/doc/html/opengl-overlay-example.html index 16ab9e1d..ed655bd1 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. -<p> See <tt>$QTDIR/examples/opengl/overlay</tt> for the source code. +<p> See <tt>$TQTDIR/examples/opengl/overlay</tt> for the source code. <p> <p>See also <a href="opengl-examples.html">OpenGL Examples</a>. <!-- eof --> diff --git a/doc/html/opengl-overlay-x11-example.html b/doc/html/opengl-overlay-x11-example.html index aed2f05c..39918658 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. <p> Overlayrubber: An example program showing how to use TQt and TQt OpenGL Extension with X11 overlay visuals. -<p> See <tt>$QTDIR/examples/opengl/overlay_x11</tt> for the source code. +<p> See <tt>$TQTDIR/examples/opengl/overlay_x11</tt> for the source code. <p> Background information for this example can be found in the information on <a href="opengl-x11-overlays.html">overlays</a>. <p> The example program has three main parts: diff --git a/doc/html/opengl-pixmap-example.html b/doc/html/opengl-pixmap-example.html index df307db1..1ad2a116 100644 --- a/doc/html/opengl-pixmap-example.html +++ b/doc/html/opengl-pixmap-example.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; } <p> This example program is an extension of the <a href="opengl-box-example.html">OpenGL Box example</a>. <p> It demonstrates how to render OpenGL into a <a href="ntqpixmap.html">TQPixmap</a>. -<p> See <tt>$QTDIR/examples/opengl/glpixmap</tt> for the source code. +<p> See <tt>$TQTDIR/examples/opengl/glpixmap</tt> for the source code. <p> <p>See also <a href="opengl-examples.html">OpenGL Examples</a>. <!-- eof --> diff --git a/doc/html/opengl-sharedbox-example.html b/doc/html/opengl-sharedbox-example.html index 28166c32..a8c346f1 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 <a href="opengl-box-example.html">Box example</a>. <p> It demonstrates how to use OpenGL display list sharing with TQGLWidgets. -<p> See <tt>$QTDIR/examples/opengl/sharedbox</tt> for the source code. +<p> See <tt>$TQTDIR/examples/opengl/sharedbox</tt> for the source code. <p> <p>See also <a href="opengl-examples.html">OpenGL Examples</a>. <!-- eof --> diff --git a/doc/html/opengl-texture-example.html b/doc/html/opengl-texture-example.html index b3670df3..f6970aa1 100644 --- a/doc/html/opengl-texture-example.html +++ b/doc/html/opengl-texture-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; } <p> This example program demonstrates how to use OpenGL 2D textures. -<p> See <tt>$QTDIR/examples/opengl/texture</tt> for the source code. +<p> See <tt>$TQTDIR/examples/opengl/texture</tt> for the source code. <p> <p>See also <a href="opengl-examples.html">OpenGL Examples</a>. <!-- eof --> diff --git a/doc/html/plugins-howto.html b/doc/html/plugins-howto.html index 1e91156d..7bb3a2dc 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. -<p> The default directory for plugins is <tt>QTDIR/plugins</tt><sup>*</sup>, +<p> The default directory for plugins is <tt>TQTDIR/plugins</tt><sup>*</sup>, with each type of plugin in a subdirectory for that type, e.g. <tt>styles</tt>. 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 <tt>DLL</tt> (or other library. If you want the plugin to be loadable then one approach is to create a subdirectory under the application, e.g. <tt>appdir/plugins/designer</tt>, and place the plugin in that directory. <p> For <a href="designer-manual.html">TQt Designer</a>, you may need to -call TQApplication::addLibraryPath("QTDIR/plugins/designer") to load +call TQApplication::addLibraryPath("TQTDIR/plugins/designer") to load your <a href="designer-manual.html">TQt Designer</a> plugins. -<p> <sup>*</sup><small> All references to <tt>QTDIR</tt> refer to the path +<p> <sup>*</sup><small> All references to <tt>TQTDIR</tt> refer to the path where TQt was installed. </small> <p> <h2> Loading and Verifying Plugins </h2> diff --git a/doc/html/porting.html b/doc/html/porting.html index e5ca3376..58d1a059 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. <p> The source code for the old 2.x version of TQMultiLineEdit can be found -in <tt>$QTDIR/src/attic/qtmultilineedit.h/cpp</tt>. Note that the class has +in <tt>$TQTDIR/src/attic/qtmultilineedit.h/cpp</tt>. 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 <a href="ntqptrlist.html">TQPtrList</a> instead. <a name="20"></a><p> The TQTableView class has been obsoleted and is no longer a part of the TQt API. Either use the powerful <a href="ntqtable.html">TQTable</a> class or the simplistic <a href="ntqgridview.html">TQGridView</a> in any new code you create. If you really need the old table -view for compatibility you can find it in <tt>$QTDIR/src/attic/qttableview.{cpp,h}</tt>. Note that the class has been +view for compatibility you can find it in <tt>$TQTDIR/src/attic/qttableview.{cpp,h}</tt>. 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 d944ac0a..d764b5ba 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. <p> <h2> Building the library </h2> -<a name="2"></a><p> In the <tt>activeqt</tt> directory (usually <tt>QTDIR/extensions/activeqt</tt>) +<a name="2"></a><p> In the <tt>activeqt</tt> directory (usually <tt>TQTDIR/extensions/activeqt</tt>) enter the <tt>container</tt> subdirectory and run <tt>qmake</tt> to generate the makefile, and use the make tool (<tt>nmake</tt> for VC++, <tt>make</tt> for Borland) to build the library. The library <tt>qaxcontainer.lib</tt> will be linked -into <tt>QTDIR/lib</tt>. +into <tt>TQTDIR/lib</tt>. <p> If you have a shared configuration of TQt enter the <tt>plugin</tt> subdirectory and run <tt>qmake</tt> and your make tool to build a plugin that integrates the <a href="qaxwidget.html">TQAxWidget</a> class into <a href="designer-manual.html">TQt Designer</a>. diff --git a/doc/html/qaxserver.html b/doc/html/qaxserver.html index 8ab281cb..33eb8b3f 100644 --- a/doc/html/qaxserver.html +++ b/doc/html/qaxserver.html @@ -158,11 +158,11 @@ ActiveX control. of ActiveX controls are provided. <p> <h2> Building the library </h2> -<a name="2"></a><p> In the <tt>activeqt</tt> directory (usually <tt>QTDIR/extensions/activeqt</tt>) +<a name="2"></a><p> In the <tt>activeqt</tt> directory (usually <tt>TQTDIR/extensions/activeqt</tt>) enter the <tt>control</tt> subdirectory and run <tt>qmake</tt> to generate the makefile, and use the make tool (<tt>nmake</tt> for VC++, <tt>make</tt> for Borland) to build the library. The library <tt>qaxserver.lib</tt> will be linked into -<tt>QTDIR/lib</tt>. +<tt>TQTDIR/lib</tt>. <p> <h2> Using the library </h2> <a name="3"></a><p> 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 e9c0d2b1..4ee0895b 100644 --- a/doc/html/qmake-manual-2.html +++ b/doc/html/qmake-manual-2.html @@ -41,8 +41,8 @@ body { background: #ffffff; color: black; } <p>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</p> <p>The environment variable should be set to qws/envvar where envvar is one of the following:</p> <p>linux-arm-g++ linux-generic-g++ linux-mips-g++ linux-x86-g++ linux-freebsd-g++ linux-ipaq-g++ linux-solaris-g++ qnx-rtp-g++</p> -<li><p>QTDIR <br> This must be set to where TQt is (or will be) installed. For example, <em>c:\qt</em> and <em>\local\qt</em></p> -</ul><p>Once the environment variables are set go into the qmake directory, <em>$QTDIR/qmake</em>, e.g. <em>C:\qt\qmake</em>. Now run <em>make</em> or <em>nmake</em> depending on your compiler.</p> +<li><p>TQTDIR <br> This must be set to where TQt is (or will be) installed. For example, <em>c:\qt</em> and <em>\local\qt</em></p> +</ul><p>Once the environment variables are set go into the qmake directory, <em>$TQTDIR/qmake</em>, e.g. <em>C:\qt\qmake</em>. Now run <em>make</em> or <em>nmake</em> depending on your compiler.</p> <p>When the make has completed, <em>qmake</em> is ready for use.</p> <!-- eof --> <p align="right">[<a href="qmake-manual-1.html">Prev: Introduction to qmake</a>] [<a href="qmake-manual.html">Home</a>] [<a href="qmake-manual-3.html">Next: The 10 minute guide to using qmake</a>]</p> diff --git a/doc/html/qmake-manual-8.html b/doc/html/qmake-manual-8.html index bfa3cb04..b22e6dce 100644 --- a/doc/html/qmake-manual-8.html +++ b/doc/html/qmake-manual-8.html @@ -383,7 +383,7 @@ app { <p>This list will go before all builtin dependencies.</p> <a name="QMAKE_INCDIR_OPENGL"></a><h5><a name="4-2-43"></a>QMAKE_INCDIR_OPENGL</h5> <p>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 <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> -<a name="QMAKE_INCDIR_QT"></a><h5><a name="4-2-44"></a>QMAKE_INCDIR_QT</h5> +<a name="QMAKE_INCDIR_TQT"></a><h5><a name="4-2-44"></a>QMAKE_INCDIR_TQT</h5> <p>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 <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> <a name="QMAKE_INCDIR_THREAD"></a><h5><a name="4-2-45"></a>QMAKE_INCDIR_THREAD</h5> <p>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 <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> @@ -430,7 +430,7 @@ app { <p>This variable contains the list of all directories to look in to resolve dependencies. This will be used when crawling through 'included' files.</p> <h5><a name="4-2-63"></a>QMAKE_LIBDIR_OPENGL</h5> <p>This variable contains the location of the OpenGL library directory.The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> -<h5><a name="4-2-64"></a>QMAKE_LIBDIR_QT</h5> +<h5><a name="4-2-64"></a>QMAKE_LIBDIR_TQT</h5> <p>This variable contains the location of the TQt library directory.The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> <h5><a name="4-2-65"></a>QMAKE_LIBDIR_X11</h5> <p><em>This is used on Unix platforms only</em></p> @@ -571,7 +571,7 @@ OPTIONS = standard custom <p>This function will test if <em>file</em> 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.</p> <p>For example:</p> <pre> -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] <p><em>qmake</em> 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.</p> <p>The QMAKESPEC environment variable can contain any of the following:</p> <ul><li><p>A complete path to a directory containing a qmake.conf file. In this case <em>qmake</em> will open the qmake.conf file from within that directory. If the file does not exist, <em>qmake</em> will exit with an error.</p> -<li><p>The name of a platform-compiler combination. In this case, <em>qmake</em> will search in the directory specified by the QTDIR environment variable.</p> +<li><p>The name of a platform-compiler combination. In this case, <em>qmake</em> will search in the directory specified by the TQTDIR environment variable.</p> </ul><p>Note: the QMAKESPEC path will automatically be added to the <a href="qmake-manual-8.html#INCLUDEPATH">INCLUDEPATH</a> system variable.</p> <a name="INSTALLS"></a><h4><a name="7-2"></a>INSTALLS</h4> <p>It is common on UNIX to be able to install from the same utility as you build with (e.g make install). For this <em>qmake</em> 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:</p> diff --git a/doc/html/sql-driver.html b/doc/html/sql-driver.html index e6f6b3d5..6c984250 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 <tt>/usr/local</tt>) and run <tt>make</tt>: <p> <pre> -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 </pre> @@ -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 <tt>C:\MYSQL</tt>): <p> <pre> -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 </pre> @@ -175,7 +175,7 @@ columns, you have to use a forward only query to select LOB fields (see <a href="ntqsqlquery.html#setForwardOnly">TQSqlQuery::setForwardOnly</a>()). <p> Inserting BLOBs should be done using either a prepared query where the BLOBs are bound to placeholders, or <a href="ntqsqlcursor.html">TQSqlCursor</a> which uses a prepared -query to do this internally (see $QTDIR/examples/sql/blob). +query to do this internally (see $TQTDIR/examples/sql/blob). <p> <h4> Know problems </h4> <a name="3-2-4"></a><p> When a query is in forward only mode a call to <a href="ntqsqlquery.html#last">TQSqlQuery::last</a>() will @@ -195,21 +195,21 @@ libraries (it is assumed that the variable <tt>$ORACLE_HOME</tt> points to the directory where Oracle is installed) and run make: <p> If you are using Oracle 8: <pre> -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 </pre> <p> For Oracle version 9: <pre> -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 </pre> <p> For Oracle version 10: <pre> -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 </pre> @@ -230,7 +230,7 @@ installed in <tt>C:\oracle</tt>): <p> <pre> 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 </pre> @@ -288,7 +288,7 @@ You need the unixODBC header files and shared libraries. libraries (here it is assumed that unixODBC is installed in <tt>/usr/local/unixODBC</tt>) and run <tt>make</tt>: <p> <pre> -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 </pre> @@ -298,7 +298,7 @@ make <a name="3-3-4"></a><p> The ODBC header and include files should already be installed in the right directories. You just have to build the plugin as follows: <p> <pre> -cd %QTDIR%\plugins\src\sqldrivers\odbc +cd %TQTDIR%\plugins\src\sqldrivers\odbc qmake -o Makefile odbc.pro nmake </pre> @@ -352,7 +352,7 @@ header files that are usually not a part of the binary distribution. libraries, run <tt>qmake</tt> the following way (assuming that the PostgreSQL sources can be found in <tt>/usr/src/psql</tt>): <p> <pre> -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 </pre> @@ -363,7 +363,7 @@ make the PostgreSQL documentation. Assuming the PostgreSQL sources resides in <tt>C:\psql</tt>, build the plugin as follows: <p> <pre> -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 </pre> @@ -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 <tt>qmake</tt>: <p> <pre> -cd $QTDIR/plugins/src/sqldrivers/tds +cd $TQTDIR/plugins/src/sqldrivers/tds qmake -o Makefile "INCLUDEPATH=$SYBASE/include" "LIBS=-L$SYBASE/lib -lsybdb" make </pre> @@ -401,14 +401,14 @@ make <a name="3-5-2"></a><p> You can either use the DB-Library supplied by Microsoft or the Sybase Open Client (<a href="http://www.sybase.com">http://www.sybase.com</a>). You must include <tt>NTWDBLIB.LIB</tt> to build the plugin: <p> <pre> -cd %QTDIR%\plugins\src\sqldrivers\tds +cd %TQTDIR%\plugins\src\sqldrivers\tds qmake -o Makefile "LIBS+=NTWDBLIB.LIB" tds.pro nmake </pre> <p> By default the Microsoft library is used on Windows, if you want to force the use of the Sybase Open Client, you must define -<tt>Q_USE_SYBASE</tt> in <tt>%QTDIR%\src\sql\drivers\tds\qsql_tds.cpp</tt>. +<tt>Q_USE_SYBASE</tt> in <tt>%TQTDIR%\src\sql\drivers\tds\qsql_tds.cpp</tt>. <p> <a name="TQDB2"></a> <h3> TQDB2 - IBM DB2 Driver (v7.1 or higher) </h3> @@ -426,7 +426,7 @@ in DB2 (see <a href="ntqsqlquery.html#setForwardOnly">TQSqlQuery::setForwardOnly <p> <h4> How to build the plugin on Unix/Linux </h4> <a name="3-6-2"></a><p> <pre> -cd $QTDIR/plugins/src/sqldrivers/db2 +cd $TQTDIR/plugins/src/sqldrivers/db2 qmake -o Makefile "INCLUDEPATH+=$DB2DIR/include" "LIBS+=-L$DB2DIR/lib -ldb2" make </pre> @@ -436,7 +436,7 @@ make <a name="3-6-3"></a><p> The DB2 header and include files should already be installed in the right directories. You just have to build the plugin as follows: <p> <pre> -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 </pre> @@ -468,7 +468,7 @@ directly into the TQt library). build it manually (replace <tt>$SQLITE</tt> by the directory where SQLite resides): <p> <pre> -cd $QTDIR/plugins/src/sqldrivers/sqlite +cd $TQTDIR/plugins/src/sqldrivers/sqlite qmake -o Makefile "INCLUDEPATH+=$SQLITE/include" "LIBS+=-L$SQLITE/lib -lsqlite" make </pre> @@ -501,7 +501,7 @@ or the free edition of Interbase. <a name="3-8-2"></a><p> The following assumes Interbase or Firebird is installed in <tt>/opt/interbase</tt>: <p> <pre> -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 </pre> @@ -511,7 +511,7 @@ make <a name="3-8-3"></a><p> The following assumes Interbase or Firebird is installed in <tt>C:\interbase</tt>: <p> <pre> -cd %QTDIR%\plugins\src\sqldrivers\ibase +cd %TQTDIR%\plugins\src\sqldrivers\ibase qmake -o Makefile "INCLUDEPATH+=C:\interbase\include" ibase.pro nmake </pre> @@ -535,8 +535,8 @@ make sure that the following requirements are met: <p> <ul> <li> Ensure that you are using a shared TQt library; you cannot use the plugins with a static build. -<li> Ensure that the environment variable <tt>QTDIR</tt> points to the right -directory. Go to the <tt>$QTDIR/plugins/sqldrivers</tt> directory and +<li> Ensure that the environment variable <tt>TQTDIR</tt> points to the right +directory. Go to the <tt>$TQTDIR/plugins/sqldrivers</tt> directory and make sure that the plugin exists in that directory. <li> Ensure that the client libraries of the DBMS are available on the system. On Unix, run the command <tt>ldd</tt> and pass the name of the @@ -587,8 +587,8 @@ loaded by the TQt library at runtime), the driver must use the <tt>Q_EXPORT_PLUGIN</tt> macro. Read the <a href="plugins-howto.html">TQt Plugin</a> 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 <tt>QTDIR/plugins/src/sqldrivers</tt> and -<tt>QTDIR/src/sql/drivers</tt>. +with TQt in <tt>TQTDIR/plugins/src/sqldrivers</tt> and +<tt>TQTDIR/src/sql/drivers</tt>. <p> The following code can be used as a skeleton for a SQL driver: <p> <pre> class TQNullResult : public <a href="ntqsqlresult.html">TQSqlResult</a> diff --git a/doc/html/tablet-example.html b/doc/html/tablet-example.html index b8d3a076..ee49f444 100644 --- a/doc/html/tablet-example.html +++ b/doc/html/tablet-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; } <p> This example shows how to interact with a tablet device. -<p> See <tt>$QTDIR/examples/tablet</tt> for the source code. +<p> See <tt>$TQTDIR/examples/tablet</tt> for the source code. <p>See also <a href="examples.html">Examples</a>. <!-- eof --> diff --git a/doc/html/textedit-example.html b/doc/html/textedit-example.html index 1ae287e0..6e5f47bb 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++. <p> A similar example which uses <a href="designer-manual.html">TQt Designer</a> to produce the user interface is in the <a href="designer-manual.html">TQt Designer manual</a>. -<p> See <tt>$QTDIR/examples/textedit</tt> for the source code. +<p> See <tt>$TQTDIR/examples/textedit</tt> for the source code. <p> <p>See also <a href="examples.html">Examples</a>. <!-- eof --> diff --git a/doc/html/toplevel-example.html b/doc/html/toplevel-example.html index ec51c669..9822093b 100644 --- a/doc/html/toplevel-example.html +++ b/doc/html/toplevel-example.html @@ -212,7 +212,7 @@ this attribute for toplevel window. <p> <pre> } </pre>Finally the window is shown with the new attributes. <p> To build the example go to the toplevel directory -(<tt>QTDIR/examples/toplevel</tt>) +(<tt>TQTDIR/examples/toplevel</tt>) <a href="#footnote3"><sup>(3)</sup></a><a name="footnote-call3"></a> and run <tt>qmake</tt> to generate the makefile, then use the make tool to build the library. @@ -225,7 +225,7 @@ The example uses <a href="ntqguardedptr.html">TQGuardedPtr</a> to make sure that pointer is reset to zero when the widget object is destroyed due to the <tt>WDestructiveClose</tt> flag. <a href="#footnote-call2">Back...</a> <li><a name="footnote3"></a> -We use <tt>QTDIR</tt> to stand for the directory where TQt is installed. +We use <tt>TQTDIR</tt> to stand for the directory where TQt is installed. <a href="#footnote-call3">Back...</a></ol> </hr><p>See also <a href="examples.html">Examples</a>. diff --git a/doc/html/widgets-example.html b/doc/html/widgets-example.html index ea368d6c..5ec5c864 100644 --- a/doc/html/widgets-example.html +++ b/doc/html/widgets-example.html @@ -34,10 +34,10 @@ body { background: #ffffff; color: black; } <p> This example shows most of TQt's widgets in action. It is similar -to the demo example in <tt>$QTDIR/examples/demo</tt>. +to the demo example in <tt>$TQTDIR/examples/demo</tt>. <p> Run the program, then click the right mouse button + Ctrl to identify a widget. -<p> See <tt>$QTDIR/examples/widgets</tt> for the source code. +<p> See <tt>$TQTDIR/examples/widgets</tt> for the source code. <p> <p>See also <a href="examples.html">Examples</a>. <!-- eof --> |