| [190] | 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|---|
| 2 | <!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/changes.doc:36 -->
|
|---|
| 3 | <html>
|
|---|
| 4 | <head>
|
|---|
| 5 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
|---|
| 6 | <title>Key Features in Qt 3.0</title>
|
|---|
| 7 | <style type="text/css"><!--
|
|---|
| 8 | fn { margin-left: 1cm; text-indent: -1cm; }
|
|---|
| 9 | a:link { color: #004faf; text-decoration: none }
|
|---|
| 10 | a:visited { color: #672967; text-decoration: none }
|
|---|
| 11 | body { background: #ffffff; color: black; }
|
|---|
| 12 | --></style>
|
|---|
| 13 | </head>
|
|---|
| 14 | <body>
|
|---|
| 15 |
|
|---|
| 16 | <table border="0" cellpadding="0" cellspacing="0" width="100%">
|
|---|
| 17 | <tr bgcolor="#E5E5E5">
|
|---|
| 18 | <td valign=center>
|
|---|
| 19 | <a href="index.html">
|
|---|
| 20 | <font color="#004faf">Home</font></a>
|
|---|
| 21 | | <a href="classes.html">
|
|---|
| 22 | <font color="#004faf">All Classes</font></a>
|
|---|
| 23 | | <a href="mainclasses.html">
|
|---|
| 24 | <font color="#004faf">Main Classes</font></a>
|
|---|
| 25 | | <a href="annotated.html">
|
|---|
| 26 | <font color="#004faf">Annotated</font></a>
|
|---|
| 27 | | <a href="groups.html">
|
|---|
| 28 | <font color="#004faf">Grouped Classes</font></a>
|
|---|
| 29 | | <a href="functions.html">
|
|---|
| 30 | <font color="#004faf">Functions</font></a>
|
|---|
| 31 | </td>
|
|---|
| 32 | <td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>Key Features in Qt 3.0</h1>
|
|---|
| 33 |
|
|---|
| 34 |
|
|---|
| 35 |
|
|---|
| 36 | <p> Qt 3.0 adds a lot of new features and improvements over the Qt 2.x
|
|---|
| 37 | series. Some internals have undergone major redesign and new classes
|
|---|
| 38 | and methods have been added.
|
|---|
| 39 | <p> We have tried to keep the API of Qt 3.0 as compatible as possible with
|
|---|
| 40 | the Qt 2.x series. For most applications only minor changes will be
|
|---|
| 41 | needed to compile and run them successfully using Qt 3.0.
|
|---|
| 42 | <p> One of the major new features that has been added in the 3.0 release
|
|---|
| 43 | is a module allowing you to easily work with databases. The API is
|
|---|
| 44 | platform independent and database neutral. This module is seamlessly
|
|---|
| 45 | integrated into Qt Designer, greatly simplifying the process of
|
|---|
| 46 | building database applications and using data aware widgets.
|
|---|
| 47 | <p>
|
|---|
| 48 | Other major new features include a plugin architecture. You can use
|
|---|
| 49 | your own and third party plugins your own applications.
|
|---|
| 50 | The Unicode support of Qt 2.x has been greatly enhanced, it now
|
|---|
| 51 | includes full support for scripts written from right to left (e.g.
|
|---|
| 52 | Arabic and Hebrew) and also provides improved support for Asian
|
|---|
| 53 | languages.
|
|---|
| 54 | <p> Many new classes have been added to the Qt Library. Amongst them are
|
|---|
| 55 | classes that provide a docking architecture
|
|---|
| 56 | (<a href="qdockarea.html">QDockArea</a>/<a href="qdockwindow.html">QDockWindow</a>), a powerful rich text editor
|
|---|
| 57 | (<a href="qtextedit.html">QTextEdit</a>), a class to store and access application settings
|
|---|
| 58 | (<a href="qsettings.html">QSettings</a>) and a class to create and communicate with processes
|
|---|
| 59 | (<a href="qprocess.html">QProcess</a>).
|
|---|
| 60 | <p> Apart from the changes in the library itself a lot has been done to
|
|---|
| 61 | make the development of Qt applications with Qt 3.0 even easier than
|
|---|
| 62 | before. Two new applications have been added: Qt Linguist is a tool to
|
|---|
| 63 | help you translate your application into different languages; Qt
|
|---|
| 64 | Assistant is an easy to use help browser for the Qt documentation that
|
|---|
| 65 | supports bookmarks and can search by keyword.
|
|---|
| 66 | <p> Another change concerns the Qt build system, which has been reworked
|
|---|
| 67 | to make it a lot easier to port Qt to new platforms. You can use this
|
|---|
| 68 | platform independent build system for your own applications.
|
|---|
| 69 | <p> <h2> The Qt Library
|
|---|
| 70 | </h2>
|
|---|
| 71 | <a name="1"></a><p> A large number of new features has been added to Qt 3.0. The following
|
|---|
| 72 | list gives an overview of the most important new and changed aspects
|
|---|
| 73 | of the Qt library. A full list of every new method follows the
|
|---|
| 74 | overview.
|
|---|
| 75 | <p> <h3> Database support
|
|---|
| 76 | </h3>
|
|---|
| 77 | <a name="1-1"></a><p> One of the major new features in Qt 3.0 is the <a href="sql.html">SQL
|
|---|
| 78 | module</a> that provides multiplatform access to SQL databases,
|
|---|
| 79 | making database application programming with Qt seamless and portable.
|
|---|
| 80 | The API, built with standard SQL, is database-neutral and software
|
|---|
| 81 | development is independent of the underlying database.
|
|---|
| 82 | <p> A collection of tightly focused C++ classes are provided to give the
|
|---|
| 83 | programmer direct access to SQL databases. Developers can send raw SQL
|
|---|
| 84 | to the database server or have the Qt SQL classes generate SQL queries
|
|---|
| 85 | automatically. Drivers for Oracle, PostgreSQL, MySQL and ODBC are
|
|---|
| 86 | available and writing new drivers is straightforward.
|
|---|
| 87 | <p> Tying the results of SQL queries to GUI components is fully supported
|
|---|
| 88 | by Qt's SQL widgets. These classes include a tabular data widget
|
|---|
| 89 | (for spreadsheet-like data presentation with in-place editing), a
|
|---|
| 90 | form-based data browser (which provides data navigation and edit
|
|---|
| 91 | functions) and a form-based data viewer (which provides read-only
|
|---|
| 92 | forms). This framework can be extended by using custom field editors,
|
|---|
| 93 | allowing for example, a data table to use custom widgets for in-place
|
|---|
| 94 | editing. The SQL module fully supports Qt's signal/slots mechanism,
|
|---|
| 95 | making it easy for developers to include their own data validation and
|
|---|
| 96 | auditing code.
|
|---|
| 97 | <p> Qt Designer fully supports Qt's SQL module. All SQL widgets can be
|
|---|
| 98 | laid out within Qt Designer, and relationships can be established
|
|---|
| 99 | between controls visually. Many interactions can be defined purely in
|
|---|
| 100 | terms of Qt's signals/slots mechanism directly in Qt Designer.
|
|---|
| 101 | <p>
|
|---|
| 102 | <h3> Plugins
|
|---|
| 103 | </h3>
|
|---|
| 104 | <a name="1-2"></a><p> The <a href="qlibrary.html">QLibrary</a> class provides a platform independent wrapper for runtime
|
|---|
| 105 | loading of shared libraries. QPluginManager makes it trivial to implement
|
|---|
| 106 | plugin support in applications. The Qt library is able to load
|
|---|
| 107 | additional styles, database drivers and text codecs from plugins.
|
|---|
| 108 | <p> Qt Designer supports custom widgets in plugins, and will use the
|
|---|
| 109 | widgets both when designing and previewing forms.
|
|---|
| 110 | <p> See the <a href="plugins-howto.html">plugins documentation</a>.
|
|---|
| 111 | <p> <h3> Rich text engine and editor
|
|---|
| 112 | </h3>
|
|---|
| 113 | <a name="1-3"></a><p> The rich text engine originally introduced in Qt 2.0 has been further
|
|---|
| 114 | optimized and extended to support editing. It allows editing formatted
|
|---|
| 115 | text with different fonts, colors, paragraph styles, tables and
|
|---|
| 116 | images. The editor supports different word wrap modes, command-based
|
|---|
| 117 | undo/redo, multiple selections, drag and drop, and many other
|
|---|
| 118 | features. The new <a href="qtextedit.html">QTextEdit</a> engine is highly optimized for proccesing
|
|---|
| 119 | and displaying large documents quickly and efficiently.
|
|---|
| 120 | <p> <h3> Unicode
|
|---|
| 121 | </h3>
|
|---|
| 122 | <a name="1-4"></a><p> Apart from the rich text engine, another new feature of Qt 3.0 that
|
|---|
| 123 | relates to text handling is the greatly improved Unicode support. Qt
|
|---|
| 124 | 3.0 includes an implementation of the bidirectional algorithm (BiDi)
|
|---|
| 125 | as defined in the Unicode standard and a shaping engine for Arabic,
|
|---|
| 126 | which gives full native language support to Arabic and Hebrew speaking
|
|---|
| 127 | people. At the same time the support for Asian languages has been
|
|---|
| 128 | greatly enhanced.
|
|---|
| 129 | <p> The support is almost transparent for the developer using Qt to
|
|---|
| 130 | develop their applications. This means that developers who developed
|
|---|
| 131 | applications using Qt 2.x will automatically gain the full support for
|
|---|
| 132 | these languages when switching to Qt 3.0. Developers can rely on their
|
|---|
| 133 | application to work for people using writing systems different from
|
|---|
| 134 | Latin1, without having to worry about the complexities involved with
|
|---|
| 135 | these scripts, as Qt takes care of this automatically.
|
|---|
| 136 | <p> <h3> Docked and Floating Windows
|
|---|
| 137 | </h3>
|
|---|
| 138 | <a name="1-5"></a><p> Qt 3.0 introduces the concept of Dock Windows and Dock Areas. Dock
|
|---|
| 139 | windows are widgets, that can be attached to, and detached from, dock
|
|---|
| 140 | areas. The commonest kind of dock window is a tool bar. Any number of
|
|---|
| 141 | dock windows may be placed in a dock area. A main window can have dock
|
|---|
| 142 | areas, for example, <a href="qmainwindow.html">QMainWindow</a> provides four dock areas (top, left,
|
|---|
| 143 | bottom, right) by default. The user can freely move dock windows and
|
|---|
| 144 | place them at a convenient place in a dock area, or drag them out of
|
|---|
| 145 | the application and have them float freely as top level windows in
|
|---|
| 146 | their own right. Dock windows can also be minimized or hidden.
|
|---|
| 147 | <p> For developers, dock windows behave just like ordinary widgets. QToolbar
|
|---|
| 148 | for example is now a specialized subclass of a dock window. The API
|
|---|
| 149 | of QMainWindow and <a href="qtoolbar.html">QToolBar</a> is source compatible with Qt 2.x, so
|
|---|
| 150 | existing code which uses these classes will continue to work.
|
|---|
| 151 | <p> <h3> Regular Expressions
|
|---|
| 152 | </h3>
|
|---|
| 153 | <a name="1-6"></a><p> Qt has always provided <a href="qregexp.html#regular-expression">regular expression</a> support, but that support
|
|---|
| 154 | was pretty much limited to what was required in common GUI control
|
|---|
| 155 | elements such as file dialogs. Qt 3.0 introduces a new regular
|
|---|
| 156 | expression engine, <a href="qregexp.html">QRegExp</a>, that supports most of Perl's regex
|
|---|
| 157 | features and is Unicode based. The most useful additions are support
|
|---|
| 158 | for parentheses (capturing and non-capturing) and backreferences.
|
|---|
| 159 | <p> <h3> Storing application settings
|
|---|
| 160 | </h3>
|
|---|
| 161 | <a name="1-7"></a><p> Most programs will need to store some settings between runs, for
|
|---|
| 162 | example, user selected fonts, colors and other preferences, or a list
|
|---|
| 163 | of recently used files. The new <a href="qsettings.html">QSettings</a> class provides a platform
|
|---|
| 164 | independent way to achieve this goal. The API makes it easy to store
|
|---|
| 165 | and retrieve most of the basic data types used in Qt (such as basic
|
|---|
| 166 | C++ types, strings, lists, colors, etc). The class uses the registry
|
|---|
| 167 | on the Windows platform and traditional resource files on Unix.
|
|---|
| 168 | <p> <h3> Creating and controlling other processes
|
|---|
| 169 | </h3>
|
|---|
| 170 | <a name="1-8"></a><p> <a href="qprocess.html">QProcess</a> is a class that allows you to start other programs from
|
|---|
| 171 | within a Qt application in a platform independent manner. It gives you
|
|---|
| 172 | full control over the started program, for example you can redirect
|
|---|
| 173 | the input and output of console applications.
|
|---|
| 174 | <p> <h3> Accessibility
|
|---|
| 175 | </h3>
|
|---|
| 176 | <a name="1-9"></a><p> Accessibility means making software usable and accessible to a wide
|
|---|
| 177 | range of users, including those with disabilities. In Qt 3.0, most
|
|---|
| 178 | widgets provide accessibility information for assistive tools that can
|
|---|
| 179 | be used by a wide range of disabled users. Qt standard widgets like
|
|---|
| 180 | buttons or range controls are fully supported. Support for complex
|
|---|
| 181 | widgets, like e.g. <a href="qlistview.html">QListView</a>, is in development. Existing applications
|
|---|
| 182 | that make use of standard widgets will become accessible just by using
|
|---|
| 183 | Qt 3.0.
|
|---|
| 184 | <p> Qt uses the Active Accessibility infrastructure on Windows, and needs
|
|---|
| 185 | the MSAA SDK, which is part of most platform SDKs. With improving
|
|---|
| 186 | standardization of accessibility on other platforms, Qt will support
|
|---|
| 187 | assistive technologies on other systems, too.
|
|---|
| 188 | <p> <h3> XML Improvements
|
|---|
| 189 | </h3>
|
|---|
| 190 | <a name="1-10"></a><p> The XML framework introduced in Qt 2.2 has been vastly improved. Qt
|
|---|
| 191 | 2.2 already supported level 1 of the Document Object Model (DOM), a
|
|---|
| 192 | W3C standard for accessing and modifying XML documents. Qt 3.0 has
|
|---|
| 193 | added support for DOM Level 2 and XML namespaces.
|
|---|
| 194 | <p> The XML parser has been extended to allow incremental parsing of XML
|
|---|
| 195 | documents. This allows you to start parsing the document directly
|
|---|
| 196 | after the first parts of the data have arrived, and to continue
|
|---|
| 197 | whenever new data is available. This is especially useful if the XML
|
|---|
| 198 | document is read from a slow source, e.g. over the network, as it
|
|---|
| 199 | allows the application to start working on the data at a very early
|
|---|
| 200 | stage.
|
|---|
| 201 | <p> <h3> SVG support
|
|---|
| 202 | </h3>
|
|---|
| 203 | <a name="1-11"></a><p> SVG is a W3C standard for "Scalable Vector Graphics". Qt 3.0's XML
|
|---|
| 204 | support means that <a href="qpicture.html">QPicture</a> can optionally generate and import static
|
|---|
| 205 | SVG documents. All the SVG features that have an equivalent in
|
|---|
| 206 | <a href="qpainter.html">QPainter</a> are supported.
|
|---|
| 207 | <p> <h3> Multihead support
|
|---|
| 208 | </h3>
|
|---|
| 209 | <a name="1-12"></a><p> Many professional applications, such as DTP and CAD software, are able
|
|---|
| 210 | to display data on two or more monitors. In Qt 3.0 the <a href="qdesktopwidget.html">QDesktopWidget</a>
|
|---|
| 211 | class provides the application with runtime information about the
|
|---|
| 212 | number and geometry of the desktops on the different monitors and such
|
|---|
| 213 | allows applications to efficiently use a multi-monitor setup.
|
|---|
| 214 | <p> The virtual desktop of Mac OS X, Windows 98, and 2000 is supported, as well
|
|---|
| 215 | as the traditional multi-screen and the newer Xinerama multihead setups on
|
|---|
| 216 | X11.
|
|---|
| 217 | <p> <h3> X11 specific enhancements
|
|---|
| 218 | </h3>
|
|---|
| 219 | <a name="1-13"></a><p> Qt 3.0 now complies with the NET WM Specification, recently adopted
|
|---|
| 220 | by KDE 2.0. This allows easy integration and proper execution with
|
|---|
| 221 | desktop environments that support the NET WM specification.
|
|---|
| 222 | <p> The font handling on X11 has undergone major changes. <a href="qfont.html">QFont</a> no longer
|
|---|
| 223 | has a one-to-one relation with window system fonts. QFont is now a
|
|---|
| 224 | logical font that can load multiple window system fonts to simplify
|
|---|
| 225 | Unicode text display. This completely removes the burden of
|
|---|
| 226 | changing/setting fonts for a specific locale/language from the
|
|---|
| 227 | programmer. For end-users, any font can be used in any locale. For
|
|---|
| 228 | example, a user in Norway will be able to see Korean text without
|
|---|
| 229 | having to set their locale to Korean.
|
|---|
| 230 | <p> Qt 3.0 also supports the new render extension recently added to
|
|---|
| 231 | XFree86. This adds support for anti aliased text and pixmaps with
|
|---|
| 232 | alpha channel (semi transparency) on the systems that support the
|
|---|
| 233 | rendering extension (at the moment XFree 4.0.3 and later).
|
|---|
| 234 | <p> <h3> Printing
|
|---|
| 235 | </h3>
|
|---|
| 236 | <a name="1-14"></a><p> Printing support has been enhanced on all platforms. The <a href="qprinter.html">QPrinter</a>
|
|---|
| 237 | class now supports setting a virtual resolution for the painting
|
|---|
| 238 | process. This makes WYSIWYG printing trivial, and also allows you to
|
|---|
| 239 | take full advantage of the high resolution of a printer when painting
|
|---|
| 240 | on it.
|
|---|
| 241 | <p> The postscript driver built into Qt and used on Unix has been greatly
|
|---|
| 242 | enhanced. It supports the embedding of true/open type and type1 fonts
|
|---|
| 243 | into the document, and can correctly handle and display Unicode.
|
|---|
| 244 | Support for fonts built into the printer has been enhanced and Qt now
|
|---|
| 245 | knows about the most common printer fonts used for Asian languages.
|
|---|
| 246 | <p> <h3> <a href="qhttp.html">QHttp</a>
|
|---|
| 247 | </h3>
|
|---|
| 248 | <a name="1-15"></a><p> This class provides a simple interface for HTTP downloads and uploads.
|
|---|
| 249 | <p> <h3> Compatibility with the Standard Template Library (STL)
|
|---|
| 250 | </h3>
|
|---|
| 251 | <a name="1-16"></a><p> Support for the C++ Standard Template Library has been added to the
|
|---|
| 252 | <a href="qt-template-lib.html">Qt Template Library (QTL)</a>. The QTL
|
|---|
| 253 | classes now contain appropriate copy constructors and typedefs so that
|
|---|
| 254 | they can be freely mixed with other STL containers and algorithms. In
|
|---|
| 255 | addition, new member functions have been added to QTL template classes
|
|---|
| 256 | which correspond to STL-style naming conventions (e.g., push_back()).
|
|---|
| 257 | <p> <h2> Qt Designer
|
|---|
| 258 | </h2>
|
|---|
| 259 | <a name="2"></a><p> <a href="designer-manual.html">Qt Designer</a> was a pure dialog
|
|---|
| 260 | editor in Qt 2.2 but has now been extended to provide the full
|
|---|
| 261 | functionality of a GUI design tool.
|
|---|
| 262 | <p> This includes the ability to lay out main windows with menus and
|
|---|
| 263 | toolbars. Actions can be edited within Qt Designer and then plugged
|
|---|
| 264 | into toolbars and menu bars via drag and drop. Splitters can now be
|
|---|
| 265 | used in a way similar to layouts to group widgets horizontally or
|
|---|
| 266 | vertically.
|
|---|
| 267 | <p> In Qt 2.2, many of the dialogs created by Qt Designer had to be
|
|---|
| 268 | subclassed to implement functionality beyond the predefined signal and
|
|---|
| 269 | slot connections. Whilst the subclassing approach is still fully supported,
|
|---|
| 270 | Qt Designer now offers an alternative: a plugin for editing
|
|---|
| 271 | slots. The editor offers features such as syntax highlighting,
|
|---|
| 272 | completion, parentheses matching and incremental search.
|
|---|
| 273 | <p> The functionality of Qt Designer can now be extended via plugins.
|
|---|
| 274 | Using Qt Designer's interface or by implementing one of the provided
|
|---|
| 275 | interfaces in a plugin, a two way communication between plugin and Qt
|
|---|
| 276 | Designer can be established. This functionality is used to implement
|
|---|
| 277 | plugins for custom widgets, so that they can be used as real widgets
|
|---|
| 278 | inside the designer.
|
|---|
| 279 | <p> Basic support for project management has been added. This allows you
|
|---|
| 280 | to read and edit *.pro files, add and remove files to/from the project
|
|---|
| 281 | and do some global operations on the project. You can now open the
|
|---|
| 282 | project file and have one-click access to all the *.ui forms in the
|
|---|
| 283 | project.
|
|---|
| 284 | <p> In addition to generating code via uic, Qt Designer now supports the
|
|---|
| 285 | dynamic creation of widgets directly from XML user interface
|
|---|
| 286 | description files (*.ui files) at runtime. This eliminates the need of
|
|---|
| 287 | recompiling your application when the GUI changes, and could be used
|
|---|
| 288 | to enable your customers to do their own customizations. Technically,
|
|---|
| 289 | the feature is provided by a new class, <a href="qwidgetfactory.html">QWidgetFactory</a> in the
|
|---|
| 290 | QResource library.
|
|---|
| 291 | <p> <h2> Qt Linguist
|
|---|
| 292 | </h2>
|
|---|
| 293 | <a name="3"></a><p> <a href="linguist-manual.html">Qt Linguist</a> is a GUI utility to
|
|---|
| 294 | support translating the user-visible text in applications written with
|
|---|
| 295 | Qt. It comes with two command-line tools: lupdate and lrelease.
|
|---|
| 296 | <p> Translation of a Qt application is a three-step process:
|
|---|
| 297 | <p> <ul>
|
|---|
| 298 | <li> Run lupdate to extract user-visible text from the C++ source
|
|---|
| 299 | code of the Qt application, resulting in a translation source file
|
|---|
| 300 | (a *.ts file).
|
|---|
| 301 | <li> Provide translations for the source texts in the *.ts file using
|
|---|
| 302 | Qt Linguist.
|
|---|
| 303 | <li> Run lrelease to obtain a light-weight message file (a *.qm file)
|
|---|
| 304 | from the *.ts file, which provides very fast lookup for released
|
|---|
| 305 | applications.
|
|---|
| 306 | </ul>
|
|---|
| 307 | <p> Qt Linguist is a tool suitable for use by translators. Each
|
|---|
| 308 | user-visible (source) text is characterized by the text itself, a
|
|---|
| 309 | context (usually the name of the C++ class containing the text), and
|
|---|
| 310 | an optional comment to help the translator. The C++ class name will
|
|---|
| 311 | usually be the name of the relevant dialog, and the comment will often
|
|---|
| 312 | contain instructions that describe how to navigate to the relevant
|
|---|
| 313 | dialog.
|
|---|
| 314 | <p> You can create phrase books for Qt Linguist to provide common
|
|---|
| 315 | translations to help ensure consistency and to speed up the
|
|---|
| 316 | translation process. Whenever a translator navigates to a new text to
|
|---|
| 317 | translate, Qt Linguist uses an intelligent algorithm to provide a list
|
|---|
| 318 | of possible translations: the list is composed of relevant text from
|
|---|
| 319 | any open phrase books and also from identical or similar text that has
|
|---|
| 320 | already been translated.
|
|---|
| 321 | <p> Once a translation is complete it can be marked as "done"; such
|
|---|
| 322 | translations are included in the *.qm file. Text that has not been
|
|---|
| 323 | "done" is included in the *.qm file in its original form. Although Qt
|
|---|
| 324 | Linguist is a GUI application with dock windows and mouse control,
|
|---|
| 325 | toolbars, etc., it has a full set of keyboard shortcuts to make
|
|---|
| 326 | translation as fast and efficient as possible.
|
|---|
| 327 | <p> When the Qt application that you're developing evolves (e.g. from
|
|---|
| 328 | version 1.0 to version 1.1), the utility lupdate merges the source
|
|---|
| 329 | texts from the new version with the previous translation source file,
|
|---|
| 330 | reusing existing translations. In some typical cases, lupdate may
|
|---|
| 331 | suggest translations. These translations are marked as unfinished, so
|
|---|
| 332 | you can easily find and check them.
|
|---|
| 333 | <p> <h2> Qt Assistant
|
|---|
| 334 | </h2>
|
|---|
| 335 | <a name="4"></a><p> Thanks to the positive feedback we received about the <a href="helpsystem.html#help-system">help system</a>
|
|---|
| 336 | built into <a href="designer-manual.html">Qt Designer</a>, we decided
|
|---|
| 337 | to offer this part as a separate application called <a href="assistant.html">Qt Assistant</a>. Qt Assistant can be used to
|
|---|
| 338 | browse the Qt class documentation as well as the manuals for Qt
|
|---|
| 339 | Designer and Qt Linguist. It offers index searching, a contents
|
|---|
| 340 | overview, bookmarks history and incremental search. Qt Assistant is
|
|---|
| 341 | used by both Qt Designer and Qt Linguist for browsing their help
|
|---|
| 342 | documentation.
|
|---|
| 343 | <p> <h2> qmake
|
|---|
| 344 | </h2>
|
|---|
| 345 | <a name="5"></a><p> To ease portability we now provide the <a href="qmake-manual.html">qmake</a> utility to replace tmake. QMake is a C++ version of
|
|---|
| 346 | tmake which offers additional functionallity that is difficult to
|
|---|
| 347 | reproduce in tmake. Trolltech uses qmake in its build system for Qt
|
|---|
| 348 | and related products and we have released it as free software.
|
|---|
| 349 | <p>
|
|---|
| 350 | <!-- eof -->
|
|---|
| 351 | <p><address><hr><div align=center>
|
|---|
| 352 | <table width=100% cellspacing=0 border=0><tr>
|
|---|
| 353 | <td>Copyright © 2007
|
|---|
| 354 | <a href="troll.html">Trolltech</a><td align=center><a href="trademarks.html">Trademarks</a>
|
|---|
| 355 | <td align=right><div align=right>Qt 3.3.8</div>
|
|---|
| 356 | </table></div></address></body>
|
|---|
| 357 | </html>
|
|---|
