Changes: Documentation updated.

RevBy: Olli Leppanen

doc/mainpage.dox

@@ -58,38 +58,6 @@ MDeclarativeCache.
 This section gives a quick introduction on \c invoker usage and
 boosting applications.
 
-\subsection gettingstartedebooster Splash screen and single instance
-
-The \c invoker can be used to get a splash screen for the application
-and to implement single instance behaviour. If the \a exec \a booster
-is used, no modifications to the application source code are needed. Simply
-specify the name of the splash image on the invoker command line as
-follows. For more details, see \ref eboost "Using the exec booster" and
-\ref splash "Enabling a splash screen for an application".
-
-\code 
-invoker --type=e --splash=/usr/share/images/myAppSplash.jpg /usr/bin/myApp
-\endcode
-
-To request single instance behaviour, use the following command line option:
-
-\code
-invoker --type=e --single-instance /usr/bin/myApp
-\endcode
-
-This causes \c invoker to look for a running instance of the application using a 
-simple lock file based mechanism. If an already running instance is found, 
-it is brought to the foreground instead of launching a new instance of the 
-application. See \ref singleinstance 
-"Enabling single instance support for an application" for more information.
-
-The options can also be combined, in which case the splash screen is
-only shown when a new instance of the application is started:
-
-\code 
-invoker --type=e --single-instance --splash=/usr/share/images/myAppSplash.jpg /usr/bin/myApp
-\endcode
-
 \subsection boostingqtquick Boosting Qt Quick applications
 
 In order to boost Qt Quick applications with \c invoker, some changes
@@ -141,6 +109,41 @@ application binary to speed up opening it in the booster. For instructions,
 see \ref qmlboost "Using the QML booster"
 and \ref libmeegotouchboost "Using the MeeGo Touch booster".
 
+\subsection gettingstartedebooster Splash screen and single instance
+
+The \c invoker can be used to get a splash screen for the application
+and to implement single instance behaviour. If the \a exec \a booster
+is used, no modifications to the application source code are needed. 
+(Note that \a exec \a booster is meant to make splash screen and single 
+instance usage easier. If you need to reduce application startup time 
+significantly, use other boosters instead.)
+Simply specify the name of the splash image on the invoker command line as
+follows. For more details, see \ref eboost "Using the exec booster" and
+\ref splash "Enabling a splash screen for an application".
+
+\code 
+invoker --type=e --splash=/usr/share/images/myAppSplash.jpg /usr/bin/myApp
+\endcode
+
+To request single instance behaviour, use the following command line option:
+
+\code
+invoker --type=e --single-instance /usr/bin/myApp
+\endcode
+
+This causes \c invoker to look for a running instance of the application using a 
+simple lock file based mechanism. If an already running instance is found, 
+it is brought to the foreground instead of launching a new instance of the 
+application. See \ref singleinstance 
+"Enabling single instance support for an application" for more information.
+
+The options can also be combined, in which case the splash screen is
+only shown when a new instance of the application is started:
+
+\code 
+invoker --type=e --single-instance --splash=/usr/share/images/myAppSplash.jpg /usr/bin/myApp
+\endcode
+
 \section reference Further information
 
 - How to enable boosted startup for different types of applications: