<p> The virtual framebuffer allows Qt/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>$QTDIR/tools/qvfb</tt>.
<p><h2> Using the Virtual Framebuffer
</h2>
<aname="1"></a><p><oltype=1>
<li> Configure Qt/Embedded with the <tt>-tqvfb</tt> argument and compile the library:
<li> Configure Qt/Embedded with the <tt>-qvfb</tt> argument and compile the library:
<pre>
./configure -tqvfb
./configure -qvfb
make
</pre>
<li> Compile <tt>tqvfb</tt> as a normal Qt/X11 application and run it. Do <em>not</em>
<li> Compile <tt>qvfb</tt> as a normal Qt/X11 application and run it. Do <em>not</em>
compile it as a Qt/Embedded application.
<li> Start a Qt/Embedded master application (i.e., construct
<ahref="qapplication.html">QApplication</a> with the QApplication::GuiServer flag or use the <tt>-qws</tt> command line parameter). You can specify to the server that
@ -53,13 +53,13 @@ you wish to use the virtual framebuffer driver, e.g.:
masterapp -qws -display QVFb:0
</pre>
<li> Qt/Embedded will autodetect tqvfb, so you can omit the <tt>-display</tt>
command line parameter if you know that tqvfb is running, and that
the Qt/Embedded library supports tqvfb. (If this is not the case,
<li> Qt/Embedded will autodetect qvfb, so you can omit the <tt>-display</tt>
command line parameter if you know that qvfb is running, and that
the Qt/Embedded library supports qvfb. (If this is not the case,
Qt/Embedded will write to the real framebuffer, and your X11
display will be corrupted.)
<p></ol>
<p><tt>tqvfb</tt> supports the following command line options:
<p><tt>qvfb</tt> supports the following command line options:
@ -347,7 +347,7 @@ file for <em>lupdate</em>; your <tt>qmake</tt> project file will work fine once
you add the <tt>TRANSLATIONS</tt> entry.
<p> In your application, you must <ahref="qtranslator.html#load">QTranslator::load</a>() the translation
files appropriate for the user's language, and install them using <ahref="qapplication.html#installTranslator">QApplication::installTranslator</a>().
<p> If you have been using the old Qt tools (<tt>tqtfindtr</tt>, <tt>msg2tqm</tt> and <tt>tqtmergetr</tt>), you can use <em>tqm2ts</em> to convert your old <tt>.qm</tt> files.
<p> If you have been using the old Qt tools (<tt>findtr</tt>, <tt>msg2qm</tt> and <tt>mergetr</tt>), you can use <em>qm2ts</em> to convert your old <tt>.qm</tt> files.
<p><em>linguist</em>, <em>lupdate</em> and <em>lrelease</em> are installed in the <tt>bin</tt>
subdirectory of the base directory Qt is installed into. Click Help|Manual
in <em>Qt Linguist</em> to access the user's manual; it contains a tutorial
<!-- index Release Manager --><p>Two tools are provided for the release manager, <ahref="linguist-manual-2.html#2">lupdate</a> and <ahref="linguist-manual-2.html#3">lrelease</a>. These tools depend on <em>qmake</em> project files. You don't have to use <em>qmake</em>, though.</p>
<p>A third tool, <tt>tqm2ts</tt>, can be used for converting Qt 2.x message files to <tt>.ts</tt> files.</p>
<p>A third tool, <tt>qm2ts</tt>, can be used for converting Qt 2.x message files to <tt>.ts</tt> files.</p>
<h3><aname="1"></a>Qt Project Files</h3>
<!-- index .pro Files --><!-- index Project Files --><!-- index qmake!Project Files --><p><ahref="linguist-manual-2.html#2">lupdate</a> and <ahref="linguist-manual-2.html#3">lrelease</a> depend on information in the application's <tt>.pro</tt> Qt project file. There must be an entry in the <tt>TRANSLATIONS</tt> section of the project file for each language that is additional to the native language. A typical entry looks like this:</p>
<!-- index TRANSLATIONS!in Project Files --><pre> TRANSLATIONS = tt2_fr.ts \
<string><b>Load Descriptions</b><p>Loads a file which contains descriptions of custom widgets, so that these custom widgets can be used in the Qt Designer.</p>
<p>Since it is a lot of work to type in all the information for custom widgets, you should consider using the tqtcreatecw tool which is in $QTDIR/tools/designer/tools/tqtcreatecw. Using tqtcreatecw you can create custom widget description files for your custom widgets without the need to type in all the information manually. For more information about the README file in the tqtcreatecw directory</p></string>
<p>Since it is a lot of work to type in all the information for custom widgets, you should consider using the createcw tool which is in $QTDIR/tools/designer/tools/createcw. Using createcw you can create custom widget description files for your custom widgets without the need to type in all the information manually. For more information about the README file in the createcw directory</p></string>