From e193e0140419d117a52e3756ddd9d2bdf3ab7a4a Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Wed, 6 Nov 2013 16:23:17 -0600 Subject: Automated update from Qt3 --- doc/man/man1/createcw.1 | 57 --------------------------------------- doc/man/man1/findtr.1 | 25 ------------------ doc/man/man1/makeqpf.1 | 26 ------------------ doc/man/man1/maketqpf.1 | 26 ++++++++++++++++++ doc/man/man1/mergetr.1 | 27 ------------------- doc/man/man1/msg2qm.1 | 26 ------------------ doc/man/man1/msg2tqm.1 | 26 ++++++++++++++++++ doc/man/man1/qt20fix.1 | 32 ---------------------- doc/man/man1/qvfb.1 | 66 ---------------------------------------------- doc/man/man1/tqt20fix.1 | 32 ++++++++++++++++++++++ doc/man/man1/tqtcreatecw.1 | 57 +++++++++++++++++++++++++++++++++++++++ doc/man/man1/tqtfindtr.1 | 25 ++++++++++++++++++ doc/man/man1/tqtmergetr.1 | 27 +++++++++++++++++++ doc/man/man1/tqvfb.1 | 66 ++++++++++++++++++++++++++++++++++++++++++++++ 14 files changed, 259 insertions(+), 259 deletions(-) delete mode 100644 doc/man/man1/createcw.1 delete mode 100644 doc/man/man1/findtr.1 delete mode 100644 doc/man/man1/makeqpf.1 create mode 100644 doc/man/man1/maketqpf.1 delete mode 100644 doc/man/man1/mergetr.1 delete mode 100644 doc/man/man1/msg2qm.1 create mode 100644 doc/man/man1/msg2tqm.1 delete mode 100644 doc/man/man1/qt20fix.1 delete mode 100644 doc/man/man1/qvfb.1 create mode 100644 doc/man/man1/tqt20fix.1 create mode 100644 doc/man/man1/tqtcreatecw.1 create mode 100644 doc/man/man1/tqtfindtr.1 create mode 100644 doc/man/man1/tqtmergetr.1 create mode 100644 doc/man/man1/tqvfb.1 (limited to 'doc/man/man1') diff --git a/doc/man/man1/createcw.1 b/doc/man/man1/createcw.1 deleted file mode 100644 index 0959a2df..00000000 --- a/doc/man/man1/createcw.1 +++ /dev/null @@ -1,57 +0,0 @@ -.TH "createcw" "1" "3.0.3" "Troll Tech AS, Norway." "" -.SH "NAME" -.LP -createcw \- custom widget description creater for Qt Designer -.SH "SYNTAX" -.LP -createcw <\fIfilename.cw\fP> -.SH "DESCRIPTION" -.LP -This small application makes it much easier to create -custom widget descriptions for the Qt Designer. Using -them you can use custom widgets in the Qt Designer -including their signals, slots and properties. - -To do that normally you would have to enter all that -information in the custom widget dialog in the Qt -Designer for each widget. But this small tool can create -for you these description files for your custom widgets -which you then can simply import into the Qt Designer. So -you can use your custom widgets without any additional -work in your forms in the Qt Designer then. - -To do that you have to modify the sourcecode (main.cpp) a -bit and recompile it afterwards. - -STEP1: Include header files of the widgets for which a -description should be created here. If you have a widget -which is defined in the file mycustomwidget.h in -/home/joedeveloper/src, write here - -#include "/home/joedeveloper/src/mycustomwidget.h" - -STEP2: Instantiate all widgets for which a description -should be created here and add them to the list wl. If -your custom widget is e.g. called MyCustomWidget you -would write here - - Widget w; - w.w = new MyCustomWidget( 0, 0 ); - w.include = "mycustomwidget.h"; - w.location = "global"; - wl.append( w ); - -After that compile the program, link it with your custom -widget (library or object file) and run it like this: - - (unix): ./createcw mywidgets.cw - (win32): createcw mywidgets.cw - -After that you can import this description file into the -Qt Designer using the Custom\-Widget Dialog (See -Tools\->Custom\->Edit Custom Widgets... in the Qt Designer) -and use these custom widget there in your forms. - -.SH "AUTHORS" -.LP -Troll Tech diff --git a/doc/man/man1/findtr.1 b/doc/man/man1/findtr.1 deleted file mode 100644 index f1d3a87d..00000000 --- a/doc/man/man1/findtr.1 +++ /dev/null @@ -1,25 +0,0 @@ -.TH "findtr" "1" "3.0.3" "Troll Tech AS, Norway." "" -.SH "NAME" -.LP -findtr \- Extracts information about text to be translated -.SH "SYNTAX" -.LP -findtr *.cpp *.h >myapp.po -.SH "DESCRIPTION" -.LP - -Extracts information about text to be translated. It -recognizes the tr() constructs described above and -produces a file in ".po" format, a simple text format -that your translation team will copy and edit. For -example, the base .po file might be myapp.po and -translated versions of the file would then be -myapp_de.po, myapp_fr.po, and myapp_ja.po for -translations in German, French and Japanese respectively. - - findtr *.cpp *.h >myapp.po - copy myapp.po myapp_de.po - edit myapp_de.po -.SH "AUTHORS" -.LP -TrollTech diff --git a/doc/man/man1/makeqpf.1 b/doc/man/man1/makeqpf.1 deleted file mode 100644 index 37ddcfd4..00000000 --- a/doc/man/man1/makeqpf.1 +++ /dev/null @@ -1,26 +0,0 @@ -.TH "makeqpf" "1" "3.0.3" "Troll Tech AS, Norway." "" -.SH "NAME" -.LP -makeqpf \- Create qpf files from TTF and BDF files. -.SH "DESCRIPTION" -.LP -Qt Prerendered Font (QPF) is a light\-weight non\-scalable -font format specific to Qt/Embedded. makeqpf is a tool -that assists producing QPF files from TTF and BDF files. - - -.SH "SYNTAX" -qembed [ \fIgeneral\-files\fP ] <[ \fI\-\-images image\-files \fP]> -.br - -general\-files - These files can be any type of file. -\-\-images image\-files - These files must be in image formats supported by Qt. - -.SH "FILES" -.LP -\fI$(QTDIR)/etc/fonts/fontdir\fP -.SH "AUTHORS" -.LP -TrollTech diff --git a/doc/man/man1/maketqpf.1 b/doc/man/man1/maketqpf.1 new file mode 100644 index 00000000..641639cb --- /dev/null +++ b/doc/man/man1/maketqpf.1 @@ -0,0 +1,26 @@ +.TH "maketqpf" "1" "3.0.3" "Troll Tech AS, Norway." "" +.SH "NAME" +.LP +maketqpf \- Create qpf files from TTF and BDF files. +.SH "DESCRIPTION" +.LP +Qt Prerendered Font (QPF) is a light\-weight non\-scalable +font format specific to Qt/Embedded. maketqpf is a tool +that assists producing QPF files from TTF and BDF files. + + +.SH "SYNTAX" +qembed [ \fIgeneral\-files\fP ] <[ \fI\-\-images image\-files \fP]> +.br + +general\-files + These files can be any type of file. +\-\-images image\-files + These files must be in image formats supported by Qt. + +.SH "FILES" +.LP +\fI$(QTDIR)/etc/fonts/fontdir\fP +.SH "AUTHORS" +.LP +TrollTech diff --git a/doc/man/man1/mergetr.1 b/doc/man/man1/mergetr.1 deleted file mode 100644 index 9ed2a9f2..00000000 --- a/doc/man/man1/mergetr.1 +++ /dev/null @@ -1,27 +0,0 @@ -.TH "mergetr" "1" "3.0.3" "Troll Tech AS, Norway." "" -.SH "NAME" -.LP -mergetr \- Merge changes in translations -.SH "SYNTAX" -.LP -mergetr myapp_de.po myapp.po - -.SH "DESCRIPTION" -.LP -When the texts in your program change as it is developed, -a the base .po file can be regenerated using findtr, -then mergetr can be used to merge the changes into the -other .po files: - - mergetr myapp_de.po myapp.po - mergetr myapp_fr.po myapp.po - mergetr myapp_ja.po myapp.po - - -The translation team then edits the new .po files to -translate the new or changed texts. When texts change, -the old text is included in the .po file as a comment to -guide the new translation (no "fuzzy" matching is done). -.SH "AUTHORS" -.LP -TrollTech diff --git a/doc/man/man1/msg2qm.1 b/doc/man/man1/msg2qm.1 deleted file mode 100644 index 7d22bbb9..00000000 --- a/doc/man/man1/msg2qm.1 +++ /dev/null @@ -1,26 +0,0 @@ -.TH "msg2qm" "1" "3.0.3" "Troll Tech AS, Norway." "" -.SH "NAME" -.LP -msg2qm \- Converts translated .po files to a Qt\-specific binary format. -.SH "SYNTAX" -.LP -msg2qm myapp_de.po myapp_de.qm -.SH "DESCRIPTION" -.LP - -Converts translated .po files to a Qt\-specific binary -format (".qm" Qt message files). The Qt message files -are platform and locale independent, containing -translations in Unicode and various hash tables to -provide fast look\-up. - - msg2qm myapp_de.po myapp_de.qm - msg2qm myapp_fr.po myapp_fr.qm - msg2qm myapp_ja.po myapp_ja.qm - - -In your application, use QTranslator::load() to load -translation files appropriate for the user's language. -.SH "AUTHORS" -.LP -TrollTech diff --git a/doc/man/man1/msg2tqm.1 b/doc/man/man1/msg2tqm.1 new file mode 100644 index 00000000..c3508540 --- /dev/null +++ b/doc/man/man1/msg2tqm.1 @@ -0,0 +1,26 @@ +.TH "msg2tqm" "1" "3.0.3" "Troll Tech AS, Norway." "" +.SH "NAME" +.LP +msg2tqm \- Converts translated .po files to a Qt\-specific binary format. +.SH "SYNTAX" +.LP +msg2tqm myapp_de.po myapp_de.qm +.SH "DESCRIPTION" +.LP + +Converts translated .po files to a Qt\-specific binary +format (".qm" Qt message files). The Qt message files +are platform and locale independent, containing +translations in Unicode and various hash tables to +provide fast look\-up. + + msg2tqm myapp_de.po myapp_de.qm + msg2tqm myapp_fr.po myapp_fr.qm + msg2tqm myapp_ja.po myapp_ja.qm + + +In your application, use QTranslator::load() to load +translation files appropriate for the user's language. +.SH "AUTHORS" +.LP +TrollTech diff --git a/doc/man/man1/qt20fix.1 b/doc/man/man1/qt20fix.1 deleted file mode 100644 index af27905a..00000000 --- a/doc/man/man1/qt20fix.1 +++ /dev/null @@ -1,32 +0,0 @@ -.TH "qt20fix" "1" "3.0.3" "Troll Tech AS, Norway." "" -.SH "NAME" -.LP -qt20fix \- Helps clean namespace when porting an app from Qt1 to Qt2 -.SH "SYNTAX" -.LP -qt20fix myapp.cpp - -.SH "DESCRIPTION" -.LP -Qt 2.x is namespace\-clean, unlike 1.x. Qt now uses very -few global identifiers. Identifiers like red, blue, -LeftButton, AlignRight, Key_Up, Key_Down, NoBrush etc. -are now part of a special class Qt (defined in -ntqnamespace.h), which is inherited by most Qt classes. -Member functions of classes that inherit from QWidget, -etc. are totally unaffected, but code that is not in -functions of classes inherited from Qt, you must qualify -these identifiers like this: Qt::red, Qt::LeftButton, -Qt::AlignRight, etc. - -The qt/bin/qt20fix script helps to fix the code that -needs adaption, though most code does not need changing. - -Compiling with \-DQT1COMPATIBILITY will help you get going -with Qt 2.x \- it allows all the old "dirty namespace" -identifiers from Qt 1.x to continue working. Without it, -you'll get compile errors that can easily be fixed by -searching this page for the clean identifiers. -.SH "AUTHORS" -.LP -TrollTech diff --git a/doc/man/man1/qvfb.1 b/doc/man/man1/qvfb.1 deleted file mode 100644 index 0ae800d3..00000000 --- a/doc/man/man1/qvfb.1 +++ /dev/null @@ -1,66 +0,0 @@ -.TH "qvfb" "1" "3.0.3" "Troll Tech AS, Norway." "" -.SH "NAME" -.LP -qvfb \- Virtual framebuffer for Qt -.SH "DESCRIPTION" -.LP -The virtual framebuffer allows Qt/Embedded programs to be -developed on your desktop machine, without switching -between consoles and X11. - -Start a Qt/Embedded master application (i.e., construct -QApplication with QApplication::GuiServer flag or use the -\-qws command line parameter). You will need to specify to -the server that you wish to use the virtual framebuffer -driver, e.g.: - - widgets \-qws \-display QVFb:0 - -You may prefer to set the QWS_DISPLAY environment -variable to be QVFb:0. - -qvfb supports the following command line options: - - \-width width: the width of the virtual framebuffer - (default: 240). - \-height height: the height of the virtual framebuffer - (default: 320). - \-depth depth: the depth of the virtual framebuffer (1, 8 - or 32; default: 8). - \-nocursor: do not display the X11 cursor in the - framebuffer window. - \-qwsdisplay :id the Qt/Embedded display id to provide - (default: 0). - - Virtual Framebuffer Design - -The virtual framebuffer emulates a framebuffer using a -shared memory region (the virtual frame buffer) and a -utility to display the framebuffer in a window (qvfb). -The regions of the display that have changed are updated -periodically, so you will see discrete snapshots of the -framebuffer rather than each individual drawing -operation. For this reason drawing problems such as -flickering may not be apparent until the program is run -using a real framebuffer. - -The target refresh rate can be set via the "View|Refresh -Rate" menu item. This will cause qvfb to check for -updated regions more quickly. The rate is a target only. -If little drawing is being done, the framebuffer will not -show any updates between drawing events. If an -application is displaying an animation the updates will -be frequent, and the application and qvfb will compete -for processor time. - -Mouse and keyboard events are passed to the Qt/Embedded -master process via named pipes. - -The virtual framebuffer is a development tool only. No -security issues have been considered in the virtual -framebuffer design. It should be avoided in a production -environment; QT_NO_QWS_VFB should always be defined in -production libraries. -.SH "AUTHORS" -.LP -TrollTech diff --git a/doc/man/man1/tqt20fix.1 b/doc/man/man1/tqt20fix.1 new file mode 100644 index 00000000..56a79a18 --- /dev/null +++ b/doc/man/man1/tqt20fix.1 @@ -0,0 +1,32 @@ +.TH "tqt20fix" "1" "3.0.3" "Troll Tech AS, Norway." "" +.SH "NAME" +.LP +tqt20fix \- Helps clean namespace when porting an app from Qt1 to Qt2 +.SH "SYNTAX" +.LP +tqt20fix myapp.cpp + +.SH "DESCRIPTION" +.LP +Qt 2.x is namespace\-clean, unlike 1.x. Qt now uses very +few global identifiers. Identifiers like red, blue, +LeftButton, AlignRight, Key_Up, Key_Down, NoBrush etc. +are now part of a special class Qt (defined in +ntqnamespace.h), which is inherited by most Qt classes. +Member functions of classes that inherit from QWidget, +etc. are totally unaffected, but code that is not in +functions of classes inherited from Qt, you must qualify +these identifiers like this: Qt::red, Qt::LeftButton, +Qt::AlignRight, etc. + +The qt/bin/tqt20fix script helps to fix the code that +needs adaption, though most code does not need changing. + +Compiling with \-DQT1COMPATIBILITY will help you get going +with Qt 2.x \- it allows all the old "dirty namespace" +identifiers from Qt 1.x to continue working. Without it, +you'll get compile errors that can easily be fixed by +searching this page for the clean identifiers. +.SH "AUTHORS" +.LP +TrollTech diff --git a/doc/man/man1/tqtcreatecw.1 b/doc/man/man1/tqtcreatecw.1 new file mode 100644 index 00000000..4567e5f1 --- /dev/null +++ b/doc/man/man1/tqtcreatecw.1 @@ -0,0 +1,57 @@ +.TH "tqtcreatecw" "1" "3.0.3" "Troll Tech AS, Norway." "" +.SH "NAME" +.LP +tqtcreatecw \- custom widget description creater for Qt Designer +.SH "SYNTAX" +.LP +tqtcreatecw <\fIfilename.cw\fP> +.SH "DESCRIPTION" +.LP +This small application makes it much easier to create +custom widget descriptions for the Qt Designer. Using +them you can use custom widgets in the Qt Designer +including their signals, slots and properties. + +To do that normally you would have to enter all that +information in the custom widget dialog in the Qt +Designer for each widget. But this small tool can create +for you these description files for your custom widgets +which you then can simply import into the Qt Designer. So +you can use your custom widgets without any additional +work in your forms in the Qt Designer then. + +To do that you have to modify the sourcecode (main.cpp) a +bit and recompile it afterwards. + +STEP1: Include header files of the widgets for which a +description should be created here. If you have a widget +which is defined in the file mycustomwidget.h in +/home/joedeveloper/src, write here + +#include "/home/joedeveloper/src/mycustomwidget.h" + +STEP2: Instantiate all widgets for which a description +should be created here and add them to the list wl. If +your custom widget is e.g. called MyCustomWidget you +would write here + + Widget w; + w.w = new MyCustomWidget( 0, 0 ); + w.include = "mycustomwidget.h"; + w.location = "global"; + wl.append( w ); + +After that compile the program, link it with your custom +widget (library or object file) and run it like this: + + (unix): ./tqtcreatecw mywidgets.cw + (win32): tqtcreatecw mywidgets.cw + +After that you can import this description file into the +Qt Designer using the Custom\-Widget Dialog (See +Tools\->Custom\->Edit Custom Widgets... in the Qt Designer) +and use these custom widget there in your forms. + +.SH "AUTHORS" +.LP +Troll Tech diff --git a/doc/man/man1/tqtfindtr.1 b/doc/man/man1/tqtfindtr.1 new file mode 100644 index 00000000..163af792 --- /dev/null +++ b/doc/man/man1/tqtfindtr.1 @@ -0,0 +1,25 @@ +.TH "tqtfindtr" "1" "3.0.3" "Troll Tech AS, Norway." "" +.SH "NAME" +.LP +tqtfindtr \- Extracts information about text to be translated +.SH "SYNTAX" +.LP +tqtfindtr *.cpp *.h >myapp.po +.SH "DESCRIPTION" +.LP + +Extracts information about text to be translated. It +recognizes the tr() constructs described above and +produces a file in ".po" format, a simple text format +that your translation team will copy and edit. For +example, the base .po file might be myapp.po and +translated versions of the file would then be +myapp_de.po, myapp_fr.po, and myapp_ja.po for +translations in German, French and Japanese respectively. + + tqtfindtr *.cpp *.h >myapp.po + copy myapp.po myapp_de.po + edit myapp_de.po +.SH "AUTHORS" +.LP +TrollTech diff --git a/doc/man/man1/tqtmergetr.1 b/doc/man/man1/tqtmergetr.1 new file mode 100644 index 00000000..a2c574f8 --- /dev/null +++ b/doc/man/man1/tqtmergetr.1 @@ -0,0 +1,27 @@ +.TH "tqtmergetr" "1" "3.0.3" "Troll Tech AS, Norway." "" +.SH "NAME" +.LP +tqtmergetr \- Merge changes in translations +.SH "SYNTAX" +.LP +tqtmergetr myapp_de.po myapp.po + +.SH "DESCRIPTION" +.LP +When the texts in your program change as it is developed, +a the base .po file can be regenerated using tqtfindtr, +then tqtmergetr can be used to merge the changes into the +other .po files: + + tqtmergetr myapp_de.po myapp.po + tqtmergetr myapp_fr.po myapp.po + tqtmergetr myapp_ja.po myapp.po + + +The translation team then edits the new .po files to +translate the new or changed texts. When texts change, +the old text is included in the .po file as a comment to +guide the new translation (no "fuzzy" matching is done). +.SH "AUTHORS" +.LP +TrollTech diff --git a/doc/man/man1/tqvfb.1 b/doc/man/man1/tqvfb.1 new file mode 100644 index 00000000..acf02e15 --- /dev/null +++ b/doc/man/man1/tqvfb.1 @@ -0,0 +1,66 @@ +.TH "tqvfb" "1" "3.0.3" "Troll Tech AS, Norway." "" +.SH "NAME" +.LP +tqvfb \- Virtual framebuffer for Qt +.SH "DESCRIPTION" +.LP +The virtual framebuffer allows Qt/Embedded programs to be +developed on your desktop machine, without switching +between consoles and X11. + +Start a Qt/Embedded master application (i.e., construct +QApplication with QApplication::GuiServer flag or use the +\-qws command line parameter). You will need to specify to +the server that you wish to use the virtual framebuffer +driver, e.g.: + + widgets \-qws \-display QVFb:0 + +You may prefer to set the QWS_DISPLAY environment +variable to be QVFb:0. + +tqvfb supports the following command line options: + + \-width width: the width of the virtual framebuffer + (default: 240). + \-height height: the height of the virtual framebuffer + (default: 320). + \-depth depth: the depth of the virtual framebuffer (1, 8 + or 32; default: 8). + \-nocursor: do not display the X11 cursor in the + framebuffer window. + \-qwsdisplay :id the Qt/Embedded display id to provide + (default: 0). + + Virtual Framebuffer Design + +The virtual framebuffer emulates a framebuffer using a +shared memory region (the virtual frame buffer) and a +utility to display the framebuffer in a window (tqvfb). +The regions of the display that have changed are updated +periodically, so you will see discrete snapshots of the +framebuffer rather than each individual drawing +operation. For this reason drawing problems such as +flickering may not be apparent until the program is run +using a real framebuffer. + +The target refresh rate can be set via the "View|Refresh +Rate" menu item. This will cause tqvfb to check for +updated regions more quickly. The rate is a target only. +If little drawing is being done, the framebuffer will not +show any updates between drawing events. If an +application is displaying an animation the updates will +be frequent, and the application and tqvfb will compete +for processor time. + +Mouse and keyboard events are passed to the Qt/Embedded +master process via named pipes. + +The virtual framebuffer is a development tool only. No +security issues have been considered in the virtual +framebuffer design. It should be avoided in a production +environment; QT_NO_QWS_VFB should always be defined in +production libraries. +.SH "AUTHORS" +.LP +TrollTech -- cgit v1.2.1