Application management

Managing the application life cycle (starting and stopping applications) is achieved by communicating with the launcher service through the Persistent Publish/Subscribe (PPS) service.

Your window manager implementation must, at a minimum, do the following:

have access to the list of applications to be managed
publish to the /pps/services/launcher/control object
subscribe to the /pps/services/launcher/control object
handle state changes appropriately

Your window manager needs to access the application ID and any data associated with each application. This application information is required to interact with the PPS control object for starting and stopping applications.

Application information can be retrieved from various means and depends on the design of your window manager. You can use anything from a simple configuration file to setting up your own PPS objects to track application information.

Note:

The examples in this guide illustrate the system calls required to open the launcher control object, read PPS messages to react to the object's creation or deletion or to changes in its attributes, and write commands to start and stop applications.

For information about Application Launcher and the PPS control object it uses, see launcher in the System Services Reference and /pps/services/launcher/control in the PPS Objects Reference.