1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
/****************************************************************************
**
** Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies).
** Contact: http://www.qt-project.org/legal
**
** This file is part of the documentation of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:FDL$
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and Digia. For licensing terms and
** conditions see http://qt.digia.com/licensing. For further information
** use the contact form at http://qt.digia.com/contact-us.
**
** GNU Free Documentation License Usage
** Alternatively, this file may be used under the terms of the GNU Free
** Documentation License version 1.3 as published by the Free Software
** Foundation and appearing in the file included in the packaging of
** this file. Please review the following information to ensure
** the GNU Free Documentation License version 1.3 requirements
** will be met: http://www.gnu.org/copyleft/fdl.html.
** $QT_END_LICENSE$
**
****************************************************************************/
/*!
\page portingguide.html
\title Porting Guide
\brief Provides guidance to migrate your Qt 4 application to Qt 5.
Qt 5 is a result of the conscious effort to make this C++ framework more
efficient and easy to use. This release replaces quite a few legacy APIs with
more meaningful ones, such as the newer version of Qt Quick.
We try to maintain binary and source compatibility for all the public APIs in
each release, but some changes were inevitable in an effort to make Qt, a
better UI framework. In this topic, we try to summarize those changes and
provide guidance to handle them.
The following list summarizes the changes in Qt 5:
\list
\li Modularized codebase - This means only Qt essentials and the add-on
modules you're interested in are needed to develop an application.
To know what makes the essentials and add-on modules, refer to the
\l {All Modules}{modules} page.
\li Platform-specific code - Symbian and Meego-specific code is removed
from the codebase.
\li Platform defines - All platform-specific code must be wrapped using the
preprocessor macro, \c{Q_OS_*} instead of \c{Q_WS_*}.
\li Qt Widgets - These are now part of a separate module,
\l{Qt Widgets}{QtWidgets}. They were part of \l{QtGui} earlier.
\li Qt Quick - The older Qt Quick version (1.0) is now part of a separate
\l{http://qt-project.org/doc/qt-4.8/qtdeclarative.html}{Qt Declarative}
add-on module for compatibility purposes. We recommend using the new Qt
Quick (2.0) from now on to avoid binary breaks in the future.
\li Qt3Support - This module is removed in Qt 5, so you must move away from
this module before porting your codebase to Qt 5.
\li Qt WebKit - This module has been split into two, there is now a \l{Qt WebKit}
and a \l{Qt WebKit Widgets} module.
\li Multimedia - In Qt 5, multimedia support is provided by the \l{Qt Multimedia}
module. Phonon framework is no longer part of Qt, but it continues to be
maintained by the Phonon developers and has support for Qt 5. See
\l{http://phonon.kde.org}.
\endlist
\section1 Related Topics
\list
\li \l {C++ API Changes}
\li \l {Porting C++ Applications to Qt 5}
\li \l {Porting QML Applications to Qt 5}
\li \l {Porting QML Applications to Qt 5 Example}
\endlist
*/
|
