S60 3.x Startup List Management API Specification DocumentChanges in S60 3.2 Startup List Management API documentation
Changes in S60 3.0 Startup List Management API documentation
PurposeThis document describes Startup List Management API in S60. Startup List Management API provides means for third party developers to add their native applications into the device’s modifiable startup list in order to launch the application at device boot up. S60 Starter executes the modifiable startup list at the end of the terminal bootup. Startup List Management API is applicable only for native applications delivered inside SIS eXtended packages. API descriptionStartup List Management API defines rules and policies that allow a third party application to make modifications to the device’s startup list during the installation / uninstallation process. The API does not define any classes, but it defines a set of resource file structures and enumerations that each client must declare. This API does not require other SDK APIs. Use casesThe only use case of this API is to offer third-party developers a mean to get their own application started during a device start-up. API class structureThis interface has no classes. A resource file, the structure of which is defined in StartupItem.rh , is needed to define executable(s) started at boot time.
The TStartupExceptionPolicy enumeration, which is defined in StartupItem.hrh , is used to define the recovery policy in case of failure when launching the executable at device boot up. At the moment, only the value EStartupItemExPolicyNone can be used. Using Startup List Management APITo correctly use Startup List Management API the application developer must create a startup control file containing metadata about the application to be added to the startup list. The metadata contains the full path of the application executable and startup recovery policy used in case of an error in application startup. In order to add several executables into the startup list, the application developer can declare several metadata sections in a single startup control file. For detailed description about the metadata, see section API class structure . The metadata is in a resource file format and needs to be compiled by Symbian resource file compiler epocrc. The compiled resource file, i.e. the startup control file, must be installed into the import directory of Software Installer UI private folder in the Phone memory drive ( c:\private\101f875a\import\ ). In addition, the following requirements must be met:
If any of the requirements above is not met, the Software Installer UI ignores the startup control file and no items are added to the startup list. An application is automatically removed from a start-up list during uninstallation. Adding one executable into the start-up listFirst of all, the start-up control file must be created for an executable.
The compiled startup control file is installed into the import directory of Software Installer UI private folder in Phone memory drive ( c:\private\101f875a\import\ ) as follows:
Adding multiple executablesSeveral executables can be added into the startup list by declaring several metadata sections in a single startup control file.
|