diff options
| author | Mitch Curtis <mitch.curtis@theqtcompany.com> | 2015-02-19 14:52:04 +0100 |
|---|---|---|
| committer | Mitch Curtis <mitch.curtis@digia.com> | 2015-02-19 15:03:39 +0000 |
| commit | 41f794795d9e4d76ad541d0358708dc2f4af91ef (patch) | |
| tree | f63d33860cb417156573db9ed1a08f1a1e01da16 | |
| parent | 702f38506d6649ec1b94dd1c3f8f11b98543eb71 (diff) | |
Improve QML performance documentation.
Change-Id: Iceb2e38cf2f7064ff5409fcc75d3a58842a28623
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
| -rw-r--r-- | doc/src/qmlapp/performance.qdoc | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/src/qmlapp/performance.qdoc b/doc/src/qmlapp/performance.qdoc index 4dfcdde30..c82eefcd4 100644 --- a/doc/src/qmlapp/performance.qdoc +++ b/doc/src/qmlapp/performance.qdoc @@ -40,10 +40,10 @@ the draw primitives to the graphics hardware. In practice, this means that the application developer should: \list - \li use asynchronous,event driven programming wherever possible + \li use asynchronous, event-driven programming wherever possible \li use worker threads to do significant processing \li never manually spin the event loop - \li never spend more than a couple of milliseconds per frame within blocking functions. + \li never spend more than a couple of milliseconds per frame within blocking functions \endlist Failure to do so will result in skipped frames, which has a drastic effect on the @@ -51,7 +51,7 @@ user experience. \note A pattern which is tempting, but should \e never be used, is creating your own QEventLoop or calling QCoreApplication::processEvents() in order to avoid -blocking within a C++ code block invoked from QML. This is dangerous because +blocking within a C++ code block invoked from QML. This is dangerous, because when an event loop is entered in a signal handler or binding, the QML engine continues to run other bindings, animations, transitions, etc. Those bindings can then cause side effects which, for example, destroy the hierarchy containing @@ -76,9 +76,9 @@ improvements. Most QML applications will have a large amount of JavaScript code in them, in the form of dynamic functions, signal handlers, and property binding expressions. This is generally not a problem. Thanks to some optimizations in the QML engine, -such as to the bindings compiler, it can for some use-cases be faster than calling a C++ -function. However, care must be taken to ensure that unnecessary processing isn't -triggered accidentally. +such as those done to the bindings compiler, it can (in some use-cases) be faster +than calling a C++ function. However, care must be taken to ensure that unnecessary +processing isn't triggered accidentally. \section2 Bindings |