From 16bc6950e4736ea7c3ee1f5b2172be1718fade02 Mon Sep 17 00:00:00 2001 From: Bea Lam Date: Mon, 29 Mar 2010 10:59:38 +1000 Subject: Doc fixes --- doc/src/declarative/qmlruntime.qdoc | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/doc/src/declarative/qmlruntime.qdoc b/doc/src/declarative/qmlruntime.qdoc index 827b905..cfef536 100644 --- a/doc/src/declarative/qmlruntime.qdoc +++ b/doc/src/declarative/qmlruntime.qdoc @@ -56,12 +56,20 @@ installed in a production environment, assuming that it is not already present in the system. It is generally packaged alongside Qt. - To deploy an application using the QML runtime, you have two options. You can either write your - own Qt application including a QDeclarative view and deploy it the same as - any other Qt application (not discussed further on this page). Alternatively you can write a main QML file for - your application, and run your application using the \c qml executable. If a qml file - is passed as an argument to the \c qml executable, it will automatically run it. + To deploy an application using the QML runtime, you have two options: + \list + \o Write your own Qt application including a QDeclarative view and deploy it the same as + any other Qt application (not discussed further on this page), or + \o Write a main QML file for your application, and run your application using the included \c qml tool. + \endlist + + To run an application with the \c qml tool, pass the filename as an argument: + + \code + qml myQmlFile.qml + \endcode + Deploying a QML application via the \c qml executable allows for QML only deployments, but can also include custom C++ modules just as easily. Below is an example of how you might structure a complex application deployed via the qml runtime, it is a listing of the files that would -- cgit v0.12