feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: replace deprecated QDoc commands

Browse Source 
The \i and \o commands were replaced with \li and
\bold was replaced with \b in QDoc for Qt 5.

The \input command was replaced with \include in the docs.

Change-Id: I257d1bebb8ebc739ca20e0d29fcf0406ecb14534
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
This commit is contained in:
Leena Miettinen
2013-02-06 08:50:23 +01:00
committed by Oswald Buddenhagen
parent 276320caac
commit 419c6de735
133 changed files with 2773 additions and 2773 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
doc/src/overview/creator-acknowledgements.qdoc
View File

@@ -35,30 +35,30 @@
\list
\o \bold{Open Source front-end for C++ (license MIT)}, enhanced for use
\li \b{Open Source front-end for C++ (license MIT)}, enhanced for use
in \QC.\br
Roberto Raggi <roberto.raggi@gmail.com>\br
QtCreator/src/shared/cplusplus\br\br
\o \bold{Botan, a C++ crypto library. Version 1.8.8}\br
\li \b{Botan, a C++ crypto library. Version 1.8.8}\br
\list
\o Copyright (C) 1999-2004 The Botan Project. All rights
\li Copyright (C) 1999-2004 The Botan Project. All rights
reserved.
\o Copyright (C) 1999-2009 Jack Lloyd
\o 2001 Peter J Jones
\o 2004-2007 Justin Karneges
\o 2005 Matthew Gregan
\o 2005-2006 Matt Johnston
\o 2006 Luca Piccarreta
\o 2007 Yves Jerschow
\o 2007-2008 FlexSecure GmbH
\o 2007-2008 Technische Universitat Darmstadt
\o 2007-2008 Falko Strenzke
\o 2007-2008 Martin Doering
\o 2007 Manuel Hartl
\o 2007 Christoph Ludwig
\o 2007 Patrick Sona
\li Copyright (C) 1999-2009 Jack Lloyd
\li 2001 Peter J Jones
\li 2004-2007 Justin Karneges
\li 2005 Matthew Gregan
\li 2005-2006 Matt Johnston
\li 2006 Luca Piccarreta
\li 2007 Yves Jerschow
\li 2007-2008 FlexSecure GmbH
\li 2007-2008 Technische Universitat Darmstadt
\li 2007-2008 Falko Strenzke
\li 2007-2008 Martin Doering
\li 2007 Manuel Hartl
\li 2007 Christoph Ludwig
\li 2007 Patrick Sona
\endlist
All rights reserved.\br\br
@@ -89,8 +89,8 @@
The source code of Botan C++ crypto library can be found
here:
\list
\o QtCreator/src/libs/3rdparty
\o \l{http://qt.gitorious.org/qt-creator/qt-creator/trees/master/src/libs/3rdparty}
\li QtCreator/src/libs/3rdparty
\li \l{http://qt.gitorious.org/qt-creator/qt-creator/trees/master/src/libs/3rdparty}
\endlist
\br\br

12
doc/src/overview/creator-advanced.qdoc
View File

@@ -45,30 +45,30 @@
\list
\o \l{Supported Platforms}
\li \l{Supported Platforms}
You can install and run \QC on several operating systems to create
applications for multiple desktop and mobile device platforms.
\o \l{Using Other Build Systems}
\li \l{Using Other Build Systems}
\QC is integrated with cross-platform systems for build automation:
qmake and CMake. In addition, you can import generic projects that
do not use qmake or CMake, and specify that \QC ignores your build
system.
\o \l{Using Command Line Options}
\li \l{Using Command Line Options}
You can start \QC and specify some options for running it from the
command line.
\o \l{Keyboard Shortcuts}
\li \l{Keyboard Shortcuts}
\QC provides various keyboard shortcuts to speed up your development
process. You can change the keyboard shortcuts, as well as import
and export keyboard shortcut mapping schemes.
\o \l{Using External Tools}
\li \l{Using External Tools}
You can use external tools directly from \QC. Qt Linguist,
QML preview tools (QML Viewer and QML Scene), the default text
@@ -82,7 +82,7 @@
\list
\o \l{Showing Task List Files in Issues Pane}
\li \l{Showing Task List Files in Issues Pane}
You can load report files created by code scanning and analysis
tools to the \gui Issues output pane. You can navigate to the

8
doc/src/overview/creator-deployment-overview.qdoc
View File

@@ -37,12 +37,12 @@
\list
\o \l{Deploying Applications to Android Devices}
\li \l{Deploying Applications to Android Devices}
When you deploy the application on an Android device, \QC copies
the application files to the device. In addition, you can determine
the Qt libraries to use.
\o \l{Deploying Applications to Linux-Based Devices}
\li \l{Deploying Applications to Linux-Based Devices}
When you deploy the application on a Linux-based device, such
as embedded Linux, MeeGo 1.2 Harmattan, or Maemo 5/Fremantle, \QC
@@ -50,7 +50,7 @@
can test and debug the application on the device.
You can create Debian installation packages for MeeGo Harmattan and
Maemo 5/Fremantle devices.
\o \l{Deploying Applications to QNX Devices}
\li \l{Deploying Applications to QNX Devices}
When you deploy the application on a BlackBerry, \QC generates a
BAR package in the build directory and deploys it to the connected
@@ -62,7 +62,7 @@
\section1 Related Topics
\list
\o \l{Publishing}
\li \l{Publishing}
When you are ready to publish the application on a publishing
channel, you must make sure that the installation file meets the

6
doc/src/overview/creator-deployment-ovi.qdoc
View File

@@ -44,19 +44,19 @@
\list
\o \l{Publishing Qt Content for MeeGo Harmattan Devices}
\li \l{Publishing Qt Content for MeeGo Harmattan Devices}
\QC generates installation packages that you can publish to
Nokia Store. However, you must make sure that the packages meet
the requirements of the Nokia Store.
\o \l{Publishing Qt Content for Maemo Devices}
\li \l{Publishing Qt Content for Maemo Devices}
\QC generates installation packages that you can publish to
Nokia Store. However, you must make sure that the packages meet
the requirements of the Nokia Store.
\o \l{Publishing Maemo Applications to Extras-devel}
\li \l{Publishing Maemo Applications to Extras-devel}
You can use the \gui {Publish for Fremantle Extras-devel Free
Repository} wizard to create a source archive and, optionally,

8
doc/src/overview/creator-design-overview.qdoc
View File

@@ -37,7 +37,7 @@
\list
\o \l{Developing Qt Quick Applications}
\li \l{Developing Qt Quick Applications}
You can either create Qt Quick projects from scratch or import
existing projects to \QC. You can use the code editor (Edit mode)
@@ -45,7 +45,7 @@
However, the visual editor only supports Qt Quick 1, which is
offered in Qt 5 only for compatibility with Qt 4. We recommend that
you use Qt Quick 2 for new Qt 5 applications.
\o \l{Developing Widget Based Applications}
\li \l{Developing Widget Based Applications}
Widgets and forms created with \QD are integrated seamlessly with
programmed code by using the Qt signals and slots mechanism that
@@ -53,7 +53,7 @@
properties set in \QD can be changed dynamically within the code.
Furthermore, features such as widget promotion and custom
plugins allow you to use your own widgets with \QD.
\o \l{Optimizing Applications for Mobile Devices}
\li \l{Optimizing Applications for Mobile Devices}
Mobile devices have been designed for use when mobile. Keep the
characteristics of mobile devices in mind when you create
@@ -65,7 +65,7 @@
\list
\o \l{Adding Qt Designer Plugins}
\li \l{Adding Qt Designer Plugins}
You can use Qt APIs to create plugins that extend Qt applications.
This enables you to add your own widgets to \QD.

16
doc/src/overview/creator-getting-started.qdoc
View File

@@ -32,27 +32,27 @@
\table
\row
\o \inlineimage creator-gs-01.png
\o \inlineimage creator-gs-02.png
\o \inlineimage creator-gs-03.png
\o \inlineimage creator-gs-04.png
\li \inlineimage creator-gs-01.png
\li \inlineimage creator-gs-02.png
\li \inlineimage creator-gs-03.png
\li \inlineimage creator-gs-04.png
\row
\o \bold {\l{IDE Overview}}
\li \b {\l{IDE Overview}}
If you have not used an integrated development environment (IDE)
before, or want to know what kind of IDE \QC is, go to
\l{IDE Overview}.
\o \bold {\l{User Interface}}
\li \b {\l{User Interface}}
If you have not used \QC before, and want to become familiar
with the parts of the user interface, go to \l{User Interface}.
\o \bold {\l{Building and Running an Example}}
\li \b {\l{Building and Running an Example}}
To check that \l{glossary-buildandrun-kit}{kits} for building and running were
successfully installed as part of the \QSDK installation, open
an example application and run it. If you have not done so
before, go to \l{Building and Running an Example}.
\o \bold {\l{Tutorials}}
\li \b {\l{Tutorials}}
Now you are ready to start developing your own applications.
Pick a tutorial to follow in \l{Tutorials}

44
doc/src/overview/creator-glossary.qdoc
View File

@@ -32,13 +32,13 @@
\table
\header
\o Term
\o Meaning
\li Term
\li Meaning
\row
\o Build configuration
\li Build configuration
\target glossary-build-config
\o Contains all the information you need to compile the sources
\li Contains all the information you need to compile the sources
into binaries. Different build configurations allow you to
quickly build the project for different purposes.
By default, \QC creates \e {debug build} and \e {release build}
@@ -50,9 +50,9 @@
release configuration for creating the final installation file.
\row
\o Build step
\li Build step
\target glossary-build-step
\o A command that \QC executes to accomplish a basic step in a
\li A command that \QC executes to accomplish a basic step in a
complex task such as cleaning, building, or deploying a project.
\QC executes build steps in sequence to complete the task.
The number and type of necessary build steps depends on the
@@ -61,9 +61,9 @@
and \c make.
\row
\o Component
\li Component
\target glossary-component
\o An instantiable QML definition, typically
\li An instantiable QML definition, typically
contained in a .qml file. For instance, a Button component may
be defined in Button.qml. The QML runtime may instantiate this
Button component to create Button objects. Alternatively, a
@@ -72,26 +72,26 @@
{Component} element.
\row
\o Deploy configuration
\li Deploy configuration
\target glossary-deploy-config
\o Handles the packaging and copying of the necessary files to a
\li Handles the packaging and copying of the necessary files to a
location you want to run the executable at. The files can be
copied to a location in the file system of the development PC or
a mobile device.
\row
\o Kit
\li Kit
\target glossary-buildandrun-kit
\o \QC groups build and run specific settings as kits to make
\li \QC groups build and run specific settings as kits to make
cross-platform development easier. Each kit consists of a set
of values that define one environment, such as a device,
tool chain, Qt version, and debugger command to use. Configure kits at
\gui {Tools > Options > Build & Run > Kits}.
\row
\o Mode
\li Mode
\target glossary-mode
\o Adapts the \QC user interface to the different application
\li Adapts the \QC user interface to the different application
development tasks at hand. Each mode has its own view that shows
only the information required for performing a particular task,
and provides only the most relevant features and functions
@@ -99,25 +99,25 @@
is always dedicated to actual application development tasks.
\row
\o Project
\li Project
\target glossary-project
\o Groups together a set of source files, forms, and resource files
\li Groups together a set of source files, forms, and resource files
that you can build, deploy, and run for different desktop and
mobile device platforms, as
specified by a \e {build configuration}, \e {deploy
configuration}, and \e {run configuration}.
\row
\o Qt version
\li Qt version
\target glossary-project-qt
\o \QC allows you to have multiple versions of Qt installed on your
\li \QC allows you to have multiple versions of Qt installed on your
development PC and use different versions to build your projects
for different purposes.
\row
\o Run configuration
\li Run configuration
\target glossary-run-config
\o Starts the application in the location where it was copied by
\li Starts the application in the location where it was copied by
the \e {deploy configuration}. By default, when you run a
project, \QC builds it, deploys it to the device specified in the selected
\l{glossary-buildandrun-kit}{kit},
@@ -126,9 +126,9 @@
runs it again.
\row
\o Shadow build
\li Shadow build
\target glossary-shadow-build
\o Shadow building means building a project in a separate
\li Shadow building means building a project in a separate
directory, the \e{build directory}. The build directory is
different from the \e {source directory}. One of the benefits of
shadow building is that it keeps your source directory clean,

14
doc/src/overview/creator-help-overview.qdoc
View File

@@ -34,7 +34,7 @@
\list
\o \l{Using the Help Mode}
\li \l{Using the Help Mode}
\QC comes fully integrated with Qt documentation and examples using
the Qt Help plugin. You can add external documentation to the
@@ -42,21 +42,21 @@
information faster. In addition, you can add bookmarks to help
pages.
\o \l{FAQ}
\li \l{FAQ}
Contains answers to some frequently asked questions about \QC.
\o \l{Tips and Tricks}
\li \l{Tips and Tricks}
Lists useful \QC features.
\o \l{Known Issues}
\li \l{Known Issues}
Lists known issues in \QC version \qtcversion. The development team
is aware of them, and therefore, you do not need to report them as
bugs.
\o \l{Glossary}
\li \l{Glossary}
Lists special terms used in \QC.
@@ -66,11 +66,11 @@
\list
\o \l{Technical Support}
\li \l{Technical Support}
Lists Qt support sites and other useful sites.
\o \l{Acknowledgements}
\li \l{Acknowledgements}
Lists the third-party components in \QC.

38
doc/src/overview/creator-issues.qdoc
View File

@@ -42,11 +42,11 @@
\list
\o If you change the Input Languages in Windows, \QC might not
\li If you change the Input Languages in Windows, \QC might not
respond for 30 seconds. This is a known issue in the Advanced Text
Service of Microsoft Windows.
\o \QC uses SQLite for storing some of its settings. SQLite is
\li \QC uses SQLite for storing some of its settings. SQLite is
known to have problems with certain NFS servers (most notably the
nfs-user-server 2.2beta), since they can lock up the application
when it tries to lock the database. If your home directory is on an
@@ -54,20 +54,20 @@
switch to the nfs-kernel-server, or create a symlink so that the
settings are stored locally.
\o Qt 4.7.4 is known to contain a bug exposed by g++ 4.6 which triggers
\li Qt 4.7.4 is known to contain a bug exposed by g++ 4.6 which triggers
a crash in \QC. For more information, see
\l{https://bugreports.qt-project.org/browse/QTBUG-21265}{QTBUG-21265}
\o The Okteta KDE custom widget plugin might be installed as part of
\li The Okteta KDE custom widget plugin might be installed as part of
some Linux distributions. It can cause Qt Designer to crash. For
more information, see:
\list
\o \l{https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/662005}
\li \l{https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/662005}
{Ubuntu bug 662005}
\o \l{https://bugreports.qt-project.org/browse/QTBUG-12025}
\li \l{https://bugreports.qt-project.org/browse/QTBUG-12025}
{QTBUG-12025}
\endlist
@@ -86,7 +86,7 @@
\list
\o Code completion does not support typedefs for nested classes.
\li Code completion does not support typedefs for nested classes.
\endlist
@@ -94,7 +94,7 @@
\list
\o Paths or file names containing spaces or special characters
\li Paths or file names containing spaces or special characters
(such as colons, dollar signs, and hash marks) may cause problems.
This is because some of the tools \QC uses in the background have
restrictions on the characters allowed in file and directory names.
@@ -102,15 +102,15 @@
items with names consisting of plain characters, numbers,
underscores, and hyphens.
\o Creating new CMake projects with \QC is not supported.
\li Creating new CMake projects with \QC is not supported.
\if defined(qcmanual)
\o On Windows, you must create projects for Maemo 5 and Harmattan
\li On Windows, you must create projects for Maemo 5 and Harmattan
device types on the same partition where you installed Qt 4 SDK, \QC, and
MADDE.
\endif
\o If error messages displayed in the \gui {Compile Output} pane contain
\li If error messages displayed in the \gui {Compile Output} pane contain
paths where slashes are missing (for example, C:QtSDK),
check your PATH variable. For more information, see
\l{Troubleshooting MinGW Compilation Errors}.
@@ -121,29 +121,29 @@
\list
\o When debugging executables created by the GNU Compiler version 4.5.0
\li When debugging executables created by the GNU Compiler version 4.5.0
(all platforms), some data types will not be displayed in the
\gui{Locals and Expressions} view due to missing debug information.
\o GDB on Windows may not work if the 'Embassy \reg Security Center'
\li GDB on Windows may not work if the 'Embassy \reg Security Center'
software by 'Wave \reg Systems' is installed and active (causing
crashes in \c{vxvault.dll)}).
\o GDB may take long to load debugging symbols, especially from large
\li GDB may take long to load debugging symbols, especially from large
libraries.
\o Setting breakpoints in code that is compiled into the binary more
\li Setting breakpoints in code that is compiled into the binary more
than once does not work.
\o Setting breakpoints in files that do not have unique absolute
\li Setting breakpoints in files that do not have unique absolute
paths may fail. For example, remounting parts of a file system
using the --bind mount option.
\o A regression in GCC 4.5.0 causes return value optimization to
\li A regression in GCC 4.5.0 causes return value optimization to
produce inaccurate debug info that GCC applies also to
non-optimized builds. For more information, see
\l{http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44731}
{GCC Bugzilla <20> Bug 44731}.
{GCC Bugzilla <20> Bug 44731}.
\endlist
@@ -151,7 +151,7 @@
\list
\o \QMLD uses external processes (QML Puppet) to render and preview
\li \QMLD uses external processes (QML Puppet) to render and preview
images and to collect data. Executing C++ code might cause the QML
Puppet to crash. If it crashes, an error message is displayed and
you can continue editing the QML file in the code editor.

10
doc/src/overview/creator-mobile-targets.qdoc
View File

@@ -42,7 +42,7 @@
\list
\o \l{Connecting Android Devices}
\li \l{Connecting Android Devices}
Qt applications for Android are compiled as \c {shared objects} that
are loaded by a Java launcher generated by the Qt for Android SDK.
@@ -51,20 +51,20 @@
Android version 1.6, or later. You must install the Qt for Android
SDK to develop for Android devices.
\o \l{Connecting Embedded Linux Devices}
\li \l{Connecting Embedded Linux Devices}
If you have a tool chain for building applications for embedded
Linux devices (with no MADDE support) installed on the development
PC, you can add it and the device to \QC.
\o \l{Connecting Maemo Devices}
\li \l{Connecting Maemo Devices}
Maemo 5 (Fremantle) is a Linux-based software platform developed by
Nokia and delivered on the Nokia N900. Use a connectivity tool (Mad
Developer) to create the device-side end point for USB and WLAN
connections.
\o \l{Connecting MeeGo Harmattan Devices}
\li \l{Connecting MeeGo Harmattan Devices}
MeeGo Harmattan is a Linux-based software platform developed by
Nokia and preinstalled on Nokia N950 and Nokia N9. It enables
@@ -72,7 +72,7 @@
Use the SDK Connectivity tool that is preinstalled on the device to
create the device-side end point for USB and WLAN connections.
\o \l{Connecting QNX Devices}
\li \l{Connecting QNX Devices}
You can connect QNX devices to the development PC to deploy, run and
debug applications on them from within \QC. This is currently only

24
doc/src/overview/creator-overview.qdoc
View File

@@ -40,11 +40,11 @@
\table
\row
\o \inlineimage creator_managingprojects.png
\o \inlineimage creator_designinguserinterface.png
\o \inlineimage creator_coding.png
\li \inlineimage creator_managingprojects.png
\li \inlineimage creator_designinguserinterface.png
\li \inlineimage creator_coding.png
\row
\o \bold {\l{Managing Projects}}
\li \b {\l{Managing Projects}}
To be able to build and run applications, \QC needs the same
information as a compiler would need. This information is
@@ -55,7 +55,7 @@
the necessary files, and specifies settings depending on the
choices you make. For more information, see
\l{Managing Projects}.
\o \bold {\l{Designing User Interfaces}}
\li \b {\l{Designing User Interfaces}}
\QC provides two integrated visual editors, \QMLD and \QD.
To create intuitive, modern-looking, fluid user interfaces, you
@@ -65,7 +65,7 @@
structured and enforces a platform look and feel, you can use
the integrated \QD. For more information, see
\l{Designing User Interfaces}.
\o \bold {\l{Coding}}
\li \b {\l{Coding}}
As an IDE, \QC differs from a text editor in that it knows how
to build and run applications. It understands the C++ and QML
@@ -74,11 +74,11 @@
checking code syntax, code completion, and refactoring actions.
For more information, see \l{Coding}.
\row
\o \inlineimage creator_buildingrunning.png
\o \inlineimage creator_testing.png
\o \inlineimage creator_publishing.png
\li \inlineimage creator_buildingrunning.png
\li \inlineimage creator_testing.png
\li \inlineimage creator_publishing.png
\row
\o \bold {\l{Building and Running}}
\li \b {\l{Building and Running}}
\QC is integrated with cross-platform systems for build
automation: qmake and CMake. In addition, you can import
@@ -92,7 +92,7 @@
different setups and target platforms.
For more information, see \l{Building and Running}.
\o \bold {\l{Debugging and Analyzing}}
\li \b {\l{Debugging and Analyzing}}
\QC is integrated to several external native debuggers: GNU
Symbolic Debugger (GDB), Microsoft Console Debugger (CDB), and
@@ -106,7 +106,7 @@
Qt Quick applications.
For more information, see \l{Debugging and Analyzing}.
\o \bold {\l{Publishing}}
\li \b {\l{Publishing}}
\QC allows you to create installation packages for mobile
devices that are suitable for publishing to application stores

44
doc/src/overview/creator-supported-platforms.qdoc
View File

@@ -40,54 +40,54 @@
\list
\o Windows 7
\li Windows 7
\o Windows XP Service Pack 2
\li Windows XP Service Pack 2
\o Windows Vista
\li Windows Vista
\o (K)Ubuntu Linux 10.04 (32-bit and 64-bit) or later, with the
\li (K)Ubuntu Linux 10.04 (32-bit and 64-bit) or later, with the
following:
\list
\o g++
\li g++
\o make
\li make
\o libglib2.0-dev
\li libglib2.0-dev
\o libSM-dev
\li libSM-dev
\o libxrender-dev
\li libxrender-dev
\o libfontconfig1-dev
\li libfontconfig1-dev
\o libxext-dev
\li libxext-dev
\o libfreetype6-dev
\li libfreetype6-dev
\o libx11-dev
\li libx11-dev
\o libxcursor-dev
\li libxcursor-dev
\o libxfixes-dev
\li libxfixes-dev
\o libxft-dev
\li libxft-dev
\o libxi-dev
\li libxi-dev
\o libxrandr-dev
\li libxrandr-dev
\o If you are using QtOpenGL, libgl-dev and libglu-dev
\li If you are using QtOpenGL, libgl-dev and libglu-dev
\endlist
\o Mac OS 10.5 or later with the following:
\li Mac OS 10.5 or later with the following:
\list
\o Xcode tools for your Mac OS X version available from your
\li Xcode tools for your Mac OS X version available from your
Mac OS X installation DVDs or at
\l http://developer.apple.com.
@@ -100,5 +100,5 @@
To build \QC from the source, see the requirements and instructions in the
readme file that is located in the source repository.
\input overview/creator-target-platforms.qdocinc
\include overview/creator-target-platforms.qdocinc
*/

80
doc/src/overview/creator-target-platforms.qdocinc
View File

@@ -4,19 +4,19 @@
\list
\o Desktop
\li Desktop
\o \QS
\li \QS
\o Maemo 5
\li Maemo 5
\o MeeGo Harmattan
\li MeeGo Harmattan
\o Generic remote Linux
\li Generic remote Linux
\o QNX
\li QNX
\o Android
\li Android
\endlist
@@ -25,45 +25,45 @@
\table
\header
\o {1,8} Operating system
\o {8,1} Platform
\li {1,8} Operating system
\li {8,1} Platform
\header
\o Desktop
\o \QS
\o Maemo 5
\o MeeGo Harmattan
\o Generic Remote Linux
\o QNX
\o Android
\li Desktop
\li \QS
\li Maemo 5
\li MeeGo Harmattan
\li Generic Remote Linux
\li QNX
\li Android
\row
\o Windows
\o Yes
\o Yes
\o Yes
\o Yes
\o Yes
\o Yes (see \l{Running on QNX Devices} for limitations)
\o Yes
\li Windows
\li Yes
\li Yes
\li Yes
\li Yes
\li Yes
\li Yes (see \l{Running on QNX Devices} for limitations)
\li Yes
\row
\o Linux
\o Yes
\o Yes
\o Yes
\o Yes
\o Yes
\o Yes
\o Yes
\li Linux
\li Yes
\li Yes
\li Yes
\li Yes
\li Yes
\li Yes
\li Yes
\row
\o Mac OS X
\o Yes
\o Yes
\o Yes
\o Yes
\o Yes
\o Yes
\o Yes
\li Mac OS X
\li Yes
\li Yes
\li Yes
\li Yes
\li Yes
\li Yes
\li Yes
\endtable
\note Symbian support has been removed from \QC 2.6. To develop for Symbian,

28
doc/src/overview/creator-tech-support.qdoc
View File

@@ -36,37 +36,37 @@
\table
\header
\o What Do You Want to Do
\o Where to Go
\li What Do You Want to Do
\li Where to Go
\row
\o Learn more about Qt
\o \l{http://qt.digia.com/product/learning/}{Learning}
\li Learn more about Qt
\li \l{http://qt.digia.com/product/learning/}{Learning}
from Digia
\l{http://qt-project.org/wiki/developer-guides}
{Qt Developer Guides} from Qt Project
\row
\o Develop Qt applications for desktop and mobile devices
\o \l{http://qt-project.org}{Qt Developer Network}
\li Develop Qt applications for desktop and mobile devices
\li \l{http://qt-project.org}{Qt Developer Network}
\row
\o Develop Qt applications for Nokia mobile devices
\o \l{http://www.developer.nokia.com/Develop/Qt/}
\li Develop Qt applications for Nokia mobile devices
\li \l{http://www.developer.nokia.com/Develop/Qt/}
{Nokia Developer - Qt}
\row
\o Participate in Qt development
\o \l{http://qt-project.org/contribute}{Contribute to Qt}
\li Participate in Qt development
\li \l{http://qt-project.org/contribute}{Contribute to Qt}
\row
\o Find free Qt-based applications
\o \l{http://qt-apps.org/}{Qt Apps}
\li Find free Qt-based applications
\li \l{http://qt-apps.org/}{Qt Apps}
\row
\o Develop with a commercial Qt license and support - Qt by Digia
\o \l{http://qt.digia.com/Product/Licensing/}{Qt Licensing}
\li Develop with a commercial Qt license and support - Qt by Digia
\li \l{http://qt.digia.com/Product/Licensing/}{Qt Licensing}
\endtable
*/

4
doc/src/overview/creator-testing.qdoc
View File

@@ -34,7 +34,7 @@
\list
\o \l{Debugging}
\li \l{Debugging}
If you install \QC as part of \QSDK, the GNU Symbolic Debugger
is installed automatically and you should be ready to start
@@ -43,7 +43,7 @@
example. You can connect mobile devices to your development PC
and debug processes running on the devices.
\o \l{Analyzing Code}
\li \l{Analyzing Code}
\QC integrates Valgrind code analysis tools for detecting memory
leaks and profiling function execution. You must download and

4
doc/src/overview/creator-tutorials.qdoc
View File

@@ -38,11 +38,11 @@
\list
\o \l{Creating a Qt Quick 1 Application}
\li \l{Creating a Qt Quick 1 Application}
Learn how to use \QMLD to create a Qt Quick 1 application.
\o \l{Creating a Qt Widget Based Application}
\li \l{Creating a Qt Widget Based Application}
Learn how to create a Qt widget based application for the desktop.

20
doc/src/overview/mobile-app-design.qdoc
View File

@@ -41,13 +41,13 @@
\list
\o Know your users
\li Know your users
Find out who will use the application, what they will use it for,
and which mobile devices they have. Then design the application to
fit a specific context of use.
\o Design for small screens
\li Design for small screens
The screen size of mobile devices is significantly smaller than that
available on desktop devices. Carefully consider what is the most
@@ -55,21 +55,21 @@
be reasonable to try and fit as much content into the screen as you
might have in a desktop application.
\o Design for multiple screen sizes
\li Design for multiple screen sizes
Relate the position and size of each control to the dimensions of
the display. This enables the same set of information to be
presented on the screen in all resolutions; higher resolution
devices just display finer graphics.
\o Design for changing screen orientation
\li Design for changing screen orientation
Some devices support screen rotation. On these devices, applications
can be displayed in portrait or landscape orientation. Account for
orientation and dynamically adjust the display when the screen is
rotated.
\o Design intuitive ways of moving within applications
\li Design intuitive ways of moving within applications
Mobile devices lack a mouse and full-size keyboard, so users must
use the touch screen or five way navigation pad to move within
@@ -77,7 +77,7 @@
hand. To create an optimized user experience, allow users to access
information with one click; do not make them scroll and type.
\o Design for limited input methods
\li Design for limited input methods
Applications collect information from users on the task at hand. In
addition to touch screen input, some devices contain physical keys
@@ -85,27 +85,27 @@
enter information by using screen controls, such as lists, check
boxes, radio buttons, and text fields.
\o Keep response times short
\li Keep response times short
Latency can cause delays in user interaction. If users perceive
an application as being slow, they are likely to get frustrated and
stop using it.
\o Save battery time
\li Save battery time
Mobile devices are not constantly connected to a power source but
run on battery power. Optimize power consumption to keep the total
consumption at an acceptable level and to prevent users from running
out of battery time.
\o Consider network issues
\li Consider network issues
If users do not have a flat-rate data plan or WLAN support, mobile
network connections cost them money. Also, when users move around
with the devices, the networks available for connections constantly
change.
\o Remember the processing limits of the device
\li Remember the processing limits of the device
The memory available on devices is limited and you should use it
carefully. Although all mobile devices have common functionality,