diff options
| author | Jerome Pasion <jerome.pasion@nokia.com> | 2011-10-03 10:57:39 +0200 |
|---|---|---|
| committer | Qt by Nokia <qt-info@nokia.com> | 2011-10-04 08:32:33 +0200 |
| commit | eec55d54c99b28953476e452281a8c58bfc4495b (patch) | |
| tree | 14fa45bf859fc182729504a6338d17962a937bda /doc/src/declarative/qmlreusablecomponents.qdoc | |
| parent | 1780033cb259bbb166fe9b4b14c92829a8e1800e (diff) | |
Doc: Converting the overviews' \e commands to \i commands.
\e commands are deprecated and are only supported through an alias.
We should use the official command and not the deprecated command.
Change-Id: Icf88b9cda673f436dd855f22960112d0a37c74eb
Reviewed-on: http://codereview.qt-project.org/5918
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Bea Lam <bea.lam@nokia.com>
Reviewed-by: Alan Alpert <alan.alpert@nokia.com>
Diffstat (limited to 'doc/src/declarative/qmlreusablecomponents.qdoc')
| -rw-r--r-- | doc/src/declarative/qmlreusablecomponents.qdoc | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/declarative/qmlreusablecomponents.qdoc b/doc/src/declarative/qmlreusablecomponents.qdoc index 9860dd4aa2..2c84a7ce53 100644 --- a/doc/src/declarative/qmlreusablecomponents.qdoc +++ b/doc/src/declarative/qmlreusablecomponents.qdoc @@ -34,10 +34,10 @@ \title Importing Reusable Components -A \e component is an instantiable QML definition, typically contained in a -\c .qml file. For instance, a Button \e component may be defined in +A \i component is an instantiable QML definition, typically contained in a +\c .qml file. For instance, a Button \i component may be defined in \c Button.qml. The QML runtime may instantiate this Button component to create -Button \e objects. Alternatively, a component may be defined inside a +Button \i objects. Alternatively, a component may be defined inside a \l Component element. Moreover, the Button definition may also contain other components. A Button @@ -111,7 +111,7 @@ signal handler executes when the component finishes destruction. \keyword qml-top-level \section1 Top-Level Component -Choosing the \e{top-level} or the \e{root} object of components is an important +Choosing the \i{top-level} or the \i{root} object of components is an important design aspect because the top-level object dictates which properties are accessible outside the component. Some elements are not visual elements and will not have visual properties exposed outside the component. Likewise, some |