diff options
Diffstat (limited to 'doc/src/declarative/qtprogrammers.qdoc')
| -rw-r--r-- | doc/src/declarative/qtprogrammers.qdoc | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/src/declarative/qtprogrammers.qdoc b/doc/src/declarative/qtprogrammers.qdoc index 343359c..ca1d596 100644 --- a/doc/src/declarative/qtprogrammers.qdoc +++ b/doc/src/declarative/qtprogrammers.qdoc @@ -61,7 +61,7 @@ QML provides direct access to the following concepts from Qt: \o QAction - the \l {QML Basic Types}{action} type \o QObject signals and slots - available as functions to call in JavaScript \o QObject properties - available as variables in JavaScript - \o QWidget - QmlView is a QML-displaying widget + \o QWidget - QDeclarativeView is a QML-displaying widget \o Qt models - used directly in data binding (QAbstractItemModel and next generation QListModelInterface) \endlist @@ -84,14 +84,14 @@ QML Items also serve these purposes. Each is considered separately below. \section2 Simple Widgets -The most important rule to remember while implementing a new QmlGraphicsItem in C++ +The most important rule to remember while implementing a new QDeclarativeItem in C++ is that it should not contain any look and feel policies - leave that to the QML usage of the item. As an example, imagine you wanted a reusable Button item. If you therefore -decided to write a QmlGraphicsItem subclass to implement a button, +decided to write a QDeclarativeItem subclass to implement a button, just as QToolButton subclasses QWidget for this purpose, following the rule above, your -\c QmlGraphicsButton would not have any appearance - just the notions of enabled, triggering, etc. +\c QDeclarativeButton would not have any appearance - just the notions of enabled, triggering, etc. But there is already an object in Qt that does this: QAction. @@ -103,13 +103,13 @@ The look and feel of an action - the appearance of the button, the transition be and exactly how it respond to mouse, key, or touch input, should all be left for definition in QML. -It is illustrative to note that QmlGraphicsTextEdit is built upon QTextControl, -QmlGraphicsWebView is built upon QWebPage, and ListView uses QListModelInterface, +It is illustrative to note that QDeclarativeTextEdit is built upon QTextControl, +QDeclarativeWebView is built upon QWebPage, and ListView uses QListModelInterface, just as QTextEdit, QWebView, and QListView are built upon those same UI-agnostic components. The encapsulation of the look and feel that QWidgets gives is important, and for this -the QML concept of \l {qmldocuments.html}{components} serves the same purpose. If you are building a complete +the QML concept of \l {qdeclarativedocuments.html}{components} serves the same purpose. If you are building a complete suite of applications which should have a consistent look and feel, you should build a set of reusable components with the look and feel you desire. |