Changes: Corrected page grouping in doxygen

RevBy: Pertti Kellomaki
pull/1/head
Olli Leppanen 15 years ago
parent 5f9cdec12f
commit 377f7096ed

2
debian/changelog vendored

@ -1,7 +1,9 @@
applauncherd (0.29.6) unstable; urgency=low applauncherd (0.29.6) unstable; urgency=low
* Changes: Corrected doxygen grouping in documentation
* Changes: Added a command to run cpu in full speed to perf tests * Changes: Added a command to run cpu in full speed to perf tests
* Fixes: NB#254878 - COREWEB: /usr/bin/camera-ui.launch 'AppData::deleteArgv Booster::launchProcess' * Fixes: NB#254878 - COREWEB: /usr/bin/camera-ui.launch 'AppData::deleteArgv Booster::launchProcess'
* Implemented: SWP#DUI-5313, SWP#DUI-5315
-- Nimika Keshri <nimika.1.keshri@nokia.com> Thu, 12 May 2011 11:34:15 +0300 -- Nimika Keshri <nimika.1.keshri@nokia.com> Thu, 12 May 2011 11:34:15 +0300

@ -8,6 +8,6 @@ applauncherd-dev package, and applications that use the MeeGo Touch
booster should build-depend on the \c libmeegotouch-dev package. booster should build-depend on the \c libmeegotouch-dev package.
When packaging applications for Harmattan, it may also be necessary to When packaging applications for Harmattan, it may also be necessary to
\subpage aegis "modify the Aegis manifest" of the application. \ref aegis "modify the Aegis manifest" of the application.
*/ */

@ -581,7 +581,8 @@ INPUT = mainpage.dox \
dbus.dox \ dbus.dox \
advancedapplauncherd.dox \ advancedapplauncherd.dox \
debianpackaging.dox \ debianpackaging.dox \
../src/qdeclarativebooster/mdeclarativecache.h tipsandtricks.dox \
../src/qdeclarativebooster/mdeclarativecache.h
# This tag can be used to specify the character encoding of the source files # This tag can be used to specify the character encoding of the source files
# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
@ -968,7 +969,7 @@ ENUM_VALUES_PER_LINE = 4
# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE # releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE
# respectively. # respectively.
GENERATE_TREEVIEW = NONE GENERATE_TREEVIEW = YES
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
# used to set the initial width (in pixels) of the frame in which the tree # used to set the initial width (in pixels) of the frame in which the tree

@ -10,11 +10,11 @@ even if the application is not a library.
Applauncherd supports showing of a splash screen for applications. All Applauncherd supports showing of a splash screen for applications. All
those applications which can be boosted using the other boosters can show those applications which can be boosted using the other boosters can show
splash screen as described \subpage splash "here". For those applications splash screen as described \ref splash "here". For those applications
which cannot be boosted and require to have a splash screen can use the which cannot be boosted and require to have a splash screen can use the
Exec Booster. Hence for launching a splash screen for any application the Exec Exec Booster. Hence for launching a splash screen for any application the Exec
Booster can be used. Also the non boosted applications can be launched as a Booster can be used. Also the non boosted applications can be launched as a
\subpage singleinstance "Single Instance" application using the Exec Booster. \ref singleinstance "Single Instance" application using the Exec Booster.
\section runebooster Running application using Exec Booster \section runebooster Running application using Exec Booster

@ -50,8 +50,8 @@ a Debian package, make your package build-depend on \c
libmeegotouch-dev. libmeegotouch-dev.
For details on how to get the compiler and linker flags, see For details on how to get the compiler and linker flags, see
\subpage usingqmake "Using QMake", \subpage usingcmake "Using CMake", or \ref usingqmake "Using QMake", \ref usingcmake "Using CMake", or
\subpage usingpkgconfig "Using pkg-config". \ref usingpkgconfig "Using pkg-config".
\section mtboostcache 2. Utilizing the booster cache' \section mtboostcache 2. Utilizing the booster cache'
@ -91,7 +91,7 @@ the application. However, if the application has explicit calls to \c
exit(), these should be changed to use \c _exit() instead. The brief exit(), these should be changed to use \c _exit() instead. The brief
explanation is that this prevents cleanup actions related to shared explanation is that this prevents cleanup actions related to shared
libraries to be performed multiple times. For more details see libraries to be performed multiple times. For more details see
\subpage limitations "Limitations and known issues". \ref limitations "Limitations and known issues".
\section mtboostinvoker 4. Launching the application \section mtboostinvoker 4. Launching the application
@ -132,8 +132,8 @@ invoker --type=m /usr/bin/myApp
The invoker can also provide single instance behavior and a splash The invoker can also provide single instance behavior and a splash
screen for you application as follows. For more details, see screen for you application as follows. For more details, see
\subpage singleinstance "the single instance documentation" and \ref singleinstance "the single instance documentation" and
\subpage splash "the splash screen documentation." \ref splash "the splash screen documentation."
\code \code
/usr/bin/invoker --single-instance --splash=/usr/share/myApp/splash.jpg --type=m /usr/bin/myApp /usr/bin/invoker --single-instance --splash=/usr/share/myApp/splash.jpg --type=m /usr/bin/myApp

@ -1,6 +1,6 @@
/*! \mainpage Optimizing Application Startup /*! \mainpage Optimizing Application Startup
\section intro Introduction \section introduction Introduction
The \c invoker program and the \c applauncherd daemon help The \c invoker program and the \c applauncherd daemon help
applications launch faster and save memory via shared resources and applications launch faster and save memory via shared resources and
@ -64,8 +64,8 @@ The \c invoker can be used to get a splash screen for the application
and to implement single instance behavior. If the \a exec \a booster and to implement single instance behavior. If the \a exec \a booster
is used, no modifications to the application source code are needed. Simply 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 specify the name of the splash image on the invoker command line as
follows. For more details see \subpage eboost "the exec booster documentation" and follows. For more details see \ref eboost "the exec booster documentation" and
\subpage splash "the splash documentation". \ref splash "the splash documentation".
\code \code
invoker --type=e --splash=/usr/share/images/myAppSplash.jpg /usr/bin/myApp invoker --type=e --splash=/usr/share/images/myAppSplash.jpg /usr/bin/myApp
@ -82,7 +82,7 @@ This causes \c invoker to look for a running instance of the
application using a simple lock file based mechanism. If an already application using a simple lock file based mechanism. If an already
running instance is found, it is brought to the foreground instead of running instance is found, it is brought to the foreground instead of
launching a new instance of the application. See launching a new instance of the application. See
\subpage singleinstance "the single instance documentation" for more \ref singleinstance "the single instance documentation" for more
information. information.
The options can also be combined, in which case the splash screen is The options can also be combined, in which case the splash screen is
@ -135,44 +135,29 @@ invoker --type=d ./qml-helloworld
\endcode \endcode
Normally the compiler and linker flags would be provided automatically Normally the compiler and linker flags would be provided automatically
either by using \subpage usingpkgconfig "pkg-config" directly, or using it either by using \ref usingpkgconfig "pkg-config" directly, or using it
via \subpage usingcmake "cmake" or \subpage usingqmake "qmake". via \ref usingcmake "cmake" or \ref usingqmake "qmake".
It is also a good idea to hide any unnecessary symbols in the It is also a good idea to hide any unnecessary symbols in the
application binary to speed up opening it in the booster. How to do application binary to speed up opening it in the booster. How to do
this is covered in \subpage qmlboost "the QML booster documentation" this is covered in \ref qmlboost "the QML booster documentation"
and \subpage libmeegotouchboost "the MeeGo Touch booster documentation". and \ref libmeegotouchboost "the MeeGo Touch booster documentation".
\section reference Reference documentation \section reference Reference documentation
- How to enable boosted startup for different types of applications: - How to enable boosted startup for different types of applications:
- \ref qmlboost "QML" - \subpage qmlboost "QML"
- \ref qtboost "Qt" - \subpage qtboost "Qt"
- \ref libmeegotouchboost "MeeGo Touch" - \subpage libmeegotouchboost "MeeGo Touch"
- \ref eboost "Generic booster for all applications" - \subpage eboost "Generic booster for all applications"
- \ref splash "How to enable splash screen for the application" - \subpage splash "How to enable splash screen for the application"
- \ref singleinstance "How to enable single instance support for the application" - \subpage singleinstance "How to enable single instance support for the application"
- \ref invokerparameters "Advanced \c invoker command line parameters"
- \ref advancedapplauncherd "Advanced \c applauncherd usage"
\section tipsntricks Tips and tricks \section tipsntricks Tips and tricks
- How to compile and link applications with different build systems: See separate page for \subpage tipsandtricks
- \ref usingcmake "CMake"
- \ref usingqmake "QMake"
- \ref usingpkgconfig "pkg-config"
- \ref debug "How to debug boosted applications"
- \ref dbus "How to use applauncherd with D-Bus"
- \ref aegis "Aegis platform security and applauncherd"
- \ref limitations "Limitations and known issues"
*/ */

@ -45,8 +45,8 @@ a Debian package, make your package build-depend on \c
applauncherd-dev. applauncherd-dev.
For details on how to get the compiler and linker flags, see For details on how to get the compiler and linker flags, see
\subpage usingqmake "Using QMake", \subpage usingcmake "Using CMake", or \ref usingqmake "Using QMake", \ref usingcmake "Using CMake", or
\subpage usingpkgconfig "Using pkg-config". \ref usingpkgconfig "Using pkg-config".
\section qmlboostcache 2. Utilizing the booster cache \section qmlboostcache 2. Utilizing the booster cache
@ -90,7 +90,7 @@ the application. However, if the application has explicit calls to \c
exit(), these should be changed to use \c _exit() instead. The brief exit(), these should be changed to use \c _exit() instead. The brief
explanation is that this prevents cleanup actions related to shared explanation is that this prevents cleanup actions related to shared
libraries to be performed multiple times. For more details see libraries to be performed multiple times. For more details see
\subpage limitations "Limitations and known issues". \ref limitations "Limitations and known issues".
\section qmlboostinvoker 4. Launching the application \section qmlboostinvoker 4. Launching the application
@ -136,8 +136,8 @@ application to use the invoker command.
The invoker can also provide single instance behavior and a splash The invoker can also provide single instance behavior and a splash
screen for you application as follows. For more details, see screen for you application as follows. For more details, see
\subpage singleinstance "the single instance documentation" and \ref singleinstance "the single instance documentation" and
\subpage splash "the splash screen documentation." \ref splash "the splash screen documentation."
\code \code
/usr/bin/invoker --single-instance --splash=/usr/share/myApp/splash.jpg --type=d /usr/bin/myApp /usr/bin/invoker --single-instance --splash=/usr/share/myApp/splash.jpg --type=d /usr/bin/myApp

@ -45,8 +45,8 @@ a Debian package, make your package build-depend on \c
applauncherd-dev. applauncherd-dev.
For details on how to get the compiler and linker flags, see For details on how to get the compiler and linker flags, see
\subpage usingqmake "Using QMake", \subpage usingcmake "Using CMake", or \ref usingqmake "Using QMake", \ref usingcmake "Using CMake", or
\subpage usingpkgconfig "Using pkg-config". \ref usingpkgconfig "Using pkg-config".
\section qtboostexit 2. Adapting application source code \section qtboostexit 2. Adapting application source code
@ -55,7 +55,7 @@ used. However, if the application has explicit calls to \c exit(),
these should be changed to use \c _exit() instead. The brief these should be changed to use \c _exit() instead. The brief
explanation is that this prevents cleanup actions related to shared explanation is that this prevents cleanup actions related to shared
libraries to be performed multiple times. For more details see libraries to be performed multiple times. For more details see
\subpage limitations "Limitations and known issues". \ref limitations "Limitations and known issues".
\section qtboostinvoker 3. Launching the application \section qtboostinvoker 3. Launching the application
@ -72,8 +72,8 @@ invoker --type=q /usr/bin/myApp
The invoker can also provide single instance behavior and a splash The invoker can also provide single instance behavior and a splash
screen for you application as follows. For more details, see screen for you application as follows. For more details, see
\subpage singleinstance "the single instance documentation" and \ref singleinstance "the single instance documentation" and
\subpage splash "the splash screen documentation." \ref splash "the splash screen documentation."
\code \code
/usr/bin/invoker --single-instance --splash=/usr/share/myApp/splash.jpg --type=q /usr/bin/myApp /usr/bin/invoker --single-instance --splash=/usr/share/myApp/splash.jpg --type=q /usr/bin/myApp

@ -1,4 +1,4 @@
/*! \page singleinstance How to enable single instance support for the application /*! \page singleinstance How To Enable Single Instance Support For the Application
Usually user wants his application to be run as a single instance. This means, Usually user wants his application to be run as a single instance. This means,
that if the launched application is already running, the existing application that if the launched application is already running, the existing application

@ -1,4 +1,4 @@
/*! \page splash How To Enable Splash Screen For The Application /*! \page splash How To Enable Splash Screen For the Application
\section splashsec Enabling splash screen \section splashsec Enabling splash screen

@ -0,0 +1,26 @@
/*! \page tipsandtricks Tips and tricks
This page contains miscellaneous tips and triks for using \c invoker and \c applauncherd
- \subpage invokerparameters "Advanced \c invoker command line parameters"
- \subpage advancedapplauncherd "Advanced \c applauncherd usage"
- How to compile and link applications with different build systems:
- \subpage usingcmake "CMake"
- \subpage usingqmake "QMake"
- \subpage usingpkgconfig "pkg-config"
- \subpage debug "How to debug boosted applications"
- \subpage dbus "How to use applauncherd with D-Bus"
- \subpage aegis "Aegis platform security and applauncherd"
- \subpage limitations "Limitations and known issues"
- \subpage debianpackaging "Debian packaging"
*/
Loading…
Cancel
Save