> Concerning implementation details, if launchpads are separate processes,
> they should communicate with AMD to forward application 'events' to AMD
> (app started with given PID, app has been paused/stopped/killed etc.) so
> that AMD has always the correct vision of the running apps. Is it the
> right approach or am I missing something ?
AMD communicates with launchpad in the followin ways:
- AMD uses synchronous launch request to launchpad to receive the result pid for new process.
- If the application is terminated, launchpad receives SIGCHILD signal and broadcast corresponding DBUS message. Wrt_launchpad has similar logic. AMD updates the running app list when it receives this DBUS message.
Pause/resume event is different. Until TIZEN 2.x, pause/resume is window event and launchpad does not know the state change. App-core, the user client library for handling e-core loop, updates its state to AMD by itself on each window state change. This way, AMD has always the state of all the running app in the platform.
Regards,
Young
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
