Hi folks,

This RFC is about bug TC-1691, TC-159...


*(The problem happens with Crosswalk today, but it could happen with any
other application)*
AUL provide somes function calls, like  "aul_app_get_pkgname_bypid ()",
which permit to get the application package name associated with a running
PID.

Under IVI, the ICO Homescreen (profile/ivi/ico-uxf-homescreen) uses these
calls to determine if it should show a window, by getting the PID of its
process, and then comparing it will the package name. If if does not match,
the window stays hidden.

The problem is :

In Crosswalk, the process which creates the window (the GPU process)  is
*not* the same that the one (the browser process) which registers itself as
a Tizen application.
Crosswalk has a dedicated process for UI operations, which is different of
the one that does the application logic.
So, the name is never found, and Web applications never show.

In this respect, we need a way for an application to "pass" its application
identifier to the graphical layer (in this case, ICO).Here are 2 options :

1) in Crosswalk itself, have a package name passed from application layer
to the UI/GPU one (won't probably be upstream). Then, have a Weston plugin
"receive" and store the information. When requested by the
"aul_app_get_pkgname_bypid ()" call, AUL will also request the plugin for
this information and respond.
 Requires modifications in : 3 packages (crosswalk, weston, aul-1)

2) in Crosswalk itself, have a package name passed from application layer
to the UI/GPU one (won't probably be upstream). Then, store this data in a
local database or specific tmpfs.  When requested by the
"aul_app_get_pkgname_bypid ()" call, AUL will also request this base or
tmpfs for this information and respond.
 Requires modification in : 2 packages (crosswalk, aul-1)

The 2nd idea modifies less packages but may be trickier to implement. Any
opinion on this ?


-- 
Regards,



*Manuel BACHMANN Tizen Project VANNES-FR*
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to