diff options
author | Jerome Pasion <jerome.pasion@digia.com> | 2013-03-25 12:37:22 +0100 |
---|---|---|
committer | The Qt Project <gerrit-noreply@qt-project.org> | 2013-03-26 22:45:31 +0100 |
commit | 363385a549f33b2b0a34ac9cc8149376f456655c (patch) | |
tree | ff7da1b3cbae0f42666a3cc30d26e32781f6dbbd /src/quick/doc/src/appdevguide/usecases/styling.qdoc | |
parent | aaa8fd67a499b75f8ec3dc4eea2b53bbdeff11d2 (diff) |
Doc: Fixed some uses of terminolgies in qdoc files.
-"element" -> "type" or "object" (not in all cases where this change applies)
-some instances of QtQuick. It should be "Qt Quick".
-only in qdoc files. Examples and source code changes will be done later.
Task-number: QTBUG-30180
Change-Id: Ie587461a138e97606f761ad1e90909c91b479303
Reviewed-by: Alan Alpert <aalpert@blackberry.com>
Reviewed-by: Martin Smith <martin.smith@digia.com>
Diffstat (limited to 'src/quick/doc/src/appdevguide/usecases/styling.qdoc')
-rw-r--r-- | src/quick/doc/src/appdevguide/usecases/styling.qdoc | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/src/quick/doc/src/appdevguide/usecases/styling.qdoc b/src/quick/doc/src/appdevguide/usecases/styling.qdoc index 7da230b1a0..68b8d0302c 100644 --- a/src/quick/doc/src/appdevguide/usecases/styling.qdoc +++ b/src/quick/doc/src/appdevguide/usecases/styling.qdoc @@ -27,15 +27,15 @@ /*! \page qtquick-usecase-styling.html \title Use Case - Style And Theme Support -\brief Example of how to style user interface elements in QML +\brief Example of how to style user interface components in QML -The types provided in the QtQuick module are not complete user interface elements on their own. A common use case is to -develop a set of custom styled user interface elements out of the types in the QtQuick module. This is easily +The types provided in the QtQuick module are not complete user interface components on their own. A common use case is to +develop a set of custom styled user interface components out of the types in the QtQuick module. This is easily accomplished by creating your own reusable components. With the reusable components approach, you define your own type with the appearance you want to have in your application and style that type directly. You then use that type in your application instead of the unstyled type. For -example, you could create a MyText.qml which is a Text element with certain properties set by default, and use MyText +example, you could create a MyText.qml which is a Text type with certain properties set by default, and use MyText instead of Text elsewhere in your application. \section1 Example Themed Text @@ -49,8 +49,8 @@ Because the root item in MyText.qml is a Text item it will behave as a Text item, and the properties can be overriden in specific uses. However, the properties will be set to the values specified in MyText when the item is first generated, thus applying your style by default. -For pre-styled user interface elements, see the \c{Qt Components} add-on which provides a set of components. -For accessing the system theme, see the \l{SystemPalette} element documentation. +For pre-styled user interface components, see the \c{Qt Components} add-on which provides a set of components. +For accessing the system theme, see the \l{SystemPalette} type documentation. \section1 Example Themed Button \section2 Button Definition |