The \l{Qt QML} module is new in Qt 5.0. It provides the QML engine and
implements the QML language supporting infrastructure.
-(Prior to Qt 5, this functionality was provided by the \c QtDeclarative module, which
+(Prior to Qt 5, this functionality was provided by the \l {Qt Quick 1}{QtDeclarative} module, which
has now been replaced by the new \l {Qt QML} and \l {Qt Quick} C++ modules. See the
\l {Porting QML Applications to Qt 5} for more information.)
}
\endcode
- Note that the Qt Quick 1 version is named QDeclarativeComponent.
+ Note that the \l {Qt Quick 1} version is named QDeclarativeComponent.
*/
/*!
In this case, the Text item will be created in the engine's
\l {QQmlEngine::rootContext()}{root context}.
- Note that the Qt Quick 1 version is called QDeclarativeEngine.
+ Note that the \l {Qt Quick 1} version is called QDeclarativeEngine.
\sa QQmlComponent, QQmlContext
*/
^
\endcode
- Note that the Qt Quick 1 version is named QDeclarativeError
+ Note that the \l {Qt Quick 1} version is named QDeclarativeError
\sa QQuickView::errors(), QQmlComponent::errors()
*/
int result = expr->evaluate().toInt(); // result = 400
\endcode
- Note that the Qt Quick 1 version is called QDeclarativeExpression.
+ Note that the \l {Qt Quick 1} version is called QDeclarativeExpression.
*/
/*!
The \l {Writing QML Extensions with C++} tutorial also contains a chapter
on creating QML plugins.
- Note that the Qt Quick 1 version is called QDeclarativeExtensionPlugin.
+ Note that the \l {Qt Quick 1} version is called QDeclarativeExtensionPlugin.
\sa QQmlEngine::importPlugin(), {How to Create Qt Plugins}
*/
Like with normal lists, when accessing a list element by index, it is the callers responsibility to ensure
that it does not request an out of range element using the count() method before calling at().
-The Qt Quick 1 version of this class is named QDeclarativeListReference.
+The \l {Qt Quick 1} version of this class is named QDeclarativeListReference.
*/
/*!
QML list properties are typesafe - in this case \c {Fruit} is a QObject type that
\c {Apple}, \c {Orange} and \c {Banana} all derive from.
-The Qt Quick 1 version of this class is named QDeclarativeListProperty.
+The \l {Qt Quick 1} version of this class is named QDeclarativeListProperty.
\note QQmlListProperty can only be used for lists of QObject-derived object pointers.
*/
For more information about signals and threads, see
\l {Threads and QObjects} and \l {Signals and Slots Across Threads}.
- The Qt Quick 1 version of this class is named QDeclarativeNetworkAccessManagerFactory.
+ The \l {Qt Quick 1} version of this class is named QDeclarativeNetworkAccessManagerFactory.
\sa {qml/networkaccessmanagerfactory}{NetworkAccessManagerFactory example}
*/
}
\endcode
- The Qt Quick 1 version of this class is named QDeclarativeParserStatus.
+ The \l {Qt Quick 1} version of this class is named QDeclarativeParserStatus.
*/
/*! \internal */
qWarning() << "Pixel size should now be 24:" << property.read().toInt();
\endcode
-The Qt Quick 1 version of this class was named QDeclarativeProperty.
+The \l {Qt Quick 1} version of this class was named QDeclarativeProperty.
*/
/*!
\snippet qml/qtBinding.4.qml 0
- Note: in \c {QtQuick 1.x}, all function assignment was treated as
+ \note In \l {Qt Quick 1}, all function assignment was treated as
binding assignment, so the Qt.binding() function is new in
- \c {QtQuick 2.0}.
+ \l {Qt Quick}{Qt Quick 2}.
\since QtQuick 2.0
*/
\e {QtQuick.LocalStorage} instead. See the \l {QtQuick.LocalStorage 2}{QtQuick.LocalStorage} documentation
for examples.
\li The \c LayoutItem type has been removed from the \c QtQuick module as it was specific to the
-Graphics View framework backend used in \c {QtQuick 1}.
+Graphics View framework backend used in \l {Qt Quick 1}.
\endlist
\section2 Behavioral Changes
In Qt 5, all QML applications are rendered with an OpenGL scenegraph architecture rather than the
Graphics View framework used in Qt 4. Due to the scale of this architectural change, the C++ API has
-been extensively restructured and the \c QtDeclarative module has been deprecated in favour of two
+been extensively restructured and the \c QtDeclarative module has been deprecated in favor of two
new modules: \l {Qt QML}, which implements the QML engine and language infrastructure, and \l {Qt Quick},
which implements the visual canvas and scenegraph backend.
\endcode
(The \c QtDeclarative module is still available to developers as the \c {Qt Quick 1} module, as
-discussed in \l{Using the QtDeclarative module in Qt 5}{below}. However, it should not be used for
+discussed \l {Qt Quick 1}{below}. However, it should not be used for
new applications.)
an overview of creating QML plugins in Qt 5.
+\keyword Qt Quick 1
+
\section2 QtDeclarative module in Qt 5
For the purposes of porting older applications, the \c {QtDeclarative} module is still available in Qt
\section1 Qt 5.0 - Qt Quick C++ Module
-The Qt Quick C++ module is new in Qt 5. It provides the visual canvas and scenegraph back-end
-as well as the QtQuick QML module for QML application development.
+The \l {Qt Quick} C++ module is new in Qt 5. It provides the visual canvas and scenegraph back-end
+as well as the \c QtQuick QML module for QML application development.
As of Qt 5, the \l {Qt Quick} module is based on an OpenGL scenegraph. Many of the classes in
-the Qt Quick module have been ported from the \c QtDeclarative module from Qt 4.8 to use
+the \l {Qt Quick} module have been ported from the \l {Qt Quick 1}{QtDeclarative} module from Qt 4.8 to use
the scenegraph architecture; these classes have been renamed to use a \c QQuick* prefix.
(See the \l {Porting QML Applications to Qt 5} for porting information.)
\section2 Property types
Support for various math and geometry-related value types, including QVector2D, QVector3D, QVector4D,
-QMatrix4x4 and QQuaternion, as well as QColor and QFont, are now provided by Qt Quick. Properties of
+QMatrix4x4 and QQuaternion, as well as QColor and QFont, are now provided by \l {Qt Quick}. Properties of
these types can be declared in QML documents via the property syntax where the type name is \c vector2d,
\c vector3d, \c vector4d, \c matrix4x4, \c quaternion, \c color and \c font respectively.
-Qt Quick also provides implementation for the various value type factory or utility functions of the
+\l {Qt Quick} also provides implementation for the various value type factory or utility functions of the
\c Qt object which return or operate on values of the above types. The functions are:
\table
\header
\endtable
The \c Qt.rgba(), \c Qt.hsla(), \c Qt.tint(), \c Qt.lighter(), \c Qt.darker()
-and \c Qt.fontFamilies() functions already existed in \c QtDeclarative prior
-to \c {QtQuick 2.0}; the other functions are all new in \c {QtQuick 2.0}.
+and \c Qt.fontFamilies() functions already existed in \l {Qt Quick 1}{QtDeclarative} prior
+to \l {Qt Quick}{Qt Quick 2}; the other functions are all new in \l {Qt Quick}{Qt Quick 2}.
\section1 Qt 5.0 - Additional QML Modules
cases, these lists will be empty. See the \l ViewTransition documentation for more details
and examples on using these transitions.
- \note In Qt Quick 1, this transition was applied to all items that were part of the
+ \note In \l {Qt Quick 1}, this transition was applied to all items that were part of the
positioner at the time of its creation. From \l {Qt Quick}{Qt Quick 2} onwards, positioners apply the
\l populate transition to these items instead.
cases, these lists will be empty. See the \l ViewTransition documentation for more details
and examples on using these transitions.
- \note In Qt Quick 1, this transition was applied to all items that were part of the
+ \note In \l {Qt Quick 1}, this transition was applied to all items that were part of the
positioner at the time of its creation. From \l {Qt Quick}{QtQuick 2} onwards, positioners apply the
\l populate transition to these items instead.
cases, these lists will be empty. See the \l ViewTransition documentation for more details
and examples on using these transitions.
- \note In Qt Quick 1, this transition was applied to all items that were part of the
+ \note In \l {Qt Quick 1}, this transition was applied to all items that were part of the
positioner at the time of its creation. From \l {Qt Quick}{QtQuick 2} onwards, positioners apply the
\l populate transition to these items instead.
cases, these lists will be empty. See the \l ViewTransition documentation for more details
and examples on using these transitions.
- \note In Qt Quick 1, this transition was applied to all items that were part of the
+ \note In \l {Qt Quick 1}, this transition was applied to all items that were part of the
positioner at the time of its creation. From \l {Qt Quick}{QtQuick 2} onwards, positioners apply the
\l populate transition to these items instead.
<< "loaded has 'import QtQuick 1.0' or 'import Qt 4.7', this error will occur." << endl
<< endl
<< "To load files with 'import QtQuick 1.0' or 'import Qt 4.7', use the" << endl
- << "QDeclarativeView class in the qtquick1 module." << endl;
+ << "QDeclarativeView class in the Qt Quick 1 module." << endl;
delete obj;
root = 0;
}
\c cache property to \c false for the relevant \l Image, \l BorderImage or
\l AnimatedImage object.
- The Qt Quick 1 version of this class is named QDeclarativeImageProvider.
+ The \l {Qt Quick 1} version of this class is named QDeclarativeImageProvider.
\sa QQmlEngine::addImageProvider()
*/