From 09b8632d301ffa865bf717c5497b6b7a17e86b53 Mon Sep 17 00:00:00 2001 From: Kai Koehne Date: Wed, 27 May 2015 09:24:09 +0200 Subject: Doc: Mention what you can do with a control script early on Task-number: QTIFW-166 Change-Id: I42ff186b7f4203b6f29685d10136e25089892c4d Reviewed-by: Karsten Heimrich Reviewed-by: Leena Miettinen Reviewed-by: Jarek Kobus --- doc/noninteractive.qdoc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/noninteractive.qdoc b/doc/noninteractive.qdoc index 6157d9296..5485d2cbd 100644 --- a/doc/noninteractive.qdoc +++ b/doc/noninteractive.qdoc @@ -34,7 +34,11 @@ \title Controller Scripting For each installer, you can specify a control script that interacts with certain parts of - the installer's UI or functionality. The script format has to be compatible with QJSEngine. + the installer's UI or functionality. The control script can add and remove pages to the + wizard, change existing pages, do additional checks, and interact with the UI by + simulating user clicks. This allows for example unattended installations. + + The script format has to be compatible with QJSEngine. This section describes the functions that are called to implement such a control script. It also gives an overview of installer pages and the widgets that are available on each -- cgit v1.2.3