| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
doc/src/declarative/propertybinding.qdoc
doc/src/overviews.qdoc
src/declarative/util/qdeclarativeanimation.cpp
src/declarative/util/qdeclarativeview.cpp
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
doc/src/declarative/elements.qdoc
doc/src/declarative/extending.qdoc
src/declarative/qml/qdeclarativecomponent.cpp
|
| | |
| | |
| | |
| | | |
Task-number: QTBUG-16071
|
| |\ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Tidy up that section a little, while I'm at it.
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the context of QML, they are not officially supported as public API
unless otherwise documented in QDeclarativeItem. This commit mentions
that somewhere.
Task-number: QTBUG-15797
Reviewed-by: Martin Jones
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| |/
|/| |
|
|/ |
|
|
|
|
|
|
|
|
| |
The 'Writing QML Components' is mainly a restructuring of the
'Extending types from QML' page. It also documents the signal
connect() function that was previously undocumented.
Task-number: QTBUG-15718, QTBUG-15138
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* '4.7' of scm.dev.nokia.troll.no:qt/doc-staging:
Doc: Documented that border width does not affect rectangle geometry.
Doc: Minor fixes to style.
Doc: Updated the DirectFB documentation to reflect version changes.
Doc: correcting heading - Beginning Qt Quick - into - Intro to Qt Quick
Doc: Correcting references to Qt Declarative module.
doc: Stated that the destructor does not call close().
|
| | |
|
|/
|
|
| |
Task-number: QTBUG-15456
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
now has an overview of different approaches to QML/C++ integration
and demonstrates how to pass data between QML and C++ through
properties/functions/signals. The part in the old docs that focused
on QDeclarativeContext has been merged into the QDeclarativeContext
class docs (although most of the info was largely covered in there
already) and the part that covered Network Components has been
moved to the QDeclarativeComponent class docs. The custom enum
types example previously in extending-tutorial.qdoc has been
moved to these new docs.
Task-number: QTBUG-14923
|
|\ |
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-13799
Reviewed-by: Martin Jones
|
|/
|
|
|
|
| |
In the repository, we should always use the No Commercial license
alongside the GNU Free Documentation License for documentation
files.
|
|
|
|
|
| |
Reviewed-by: Trust Me
Requested-by: Legal
|
| |
|
| |
|
|
|
|
| |
and work standalone
|
| |
|
| |
|
| |
|
|
|
|
| |
QDeclarativeXXX.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
master-integration
* 'master' of scm.dev.nokia.troll.no:qt/qt-qml:
Replace QmlList* and QList* support with a single QmlListProperty type
Rename MouseRegion -> MouseArea
Update QmlChanges with animation API changes.
Document the default velocity of EaseFollow
Remove use of unexprted private classes.
Fix compile error on Solaris
Increase durations when testing Behaviors.
Add cached path rounded rect painting benchmark.
Remove use of direct event posting. Use QTest::keyClick() for keys.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
mkspecs/linux-g++-x11egl/qplatformdefs.h
src/declarative/qml/qmldom.h
src/declarative/util/qmlview.cpp
src/declarative/util/qmlview.h
tools/qdoc3/cppcodemarker.cpp
tools/qmldebugger/standalone/canvasframerate.cpp
tools/qmldebugger/standalone/engine.cpp
tools/qmldebugger/standalone/expressionquerywidget.cpp
tools/qmldebugger/standalone/expressionquerywidget.h
tools/qmldebugger/standalone/objectpropertiesview.cpp
tools/qmldebugger/standalone/objectpropertiesview.h
tools/qmldebugger/standalone/objecttree.cpp
tools/qmldebugger/standalone/qmldebugger.cpp
tools/qmldebugger/standalone/watchtable.cpp
tools/qmldebugger/standalone/watchtable.h
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
Task-number: QTBUG-7720
|
|
|
|
|
| |
Extend documentation on dynamically created objects and on integrating
with existing applications. And make those pages more discoverable.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|