Hi Mikko


Le 19/11/2013 15:37, Ylinen, Mikko a écrit :
Hi Baptiste,


On Mon, Nov 18, 2013 at 6:49 PM, Baptiste DURAND <[email protected] <mailto:[email protected]>> wrote:


    Minibrowser is a classic application that does NOT use
    appcore-common librairies and does NOT call app_efl_main function.

    That means all arguments passed through the bundle *are
    interpreted as normal **arguments* by the Minibrowser, not as
    Tizen Application Framework specific arguments. (AUL Start Time
    etc...).

    That why I would like to  introduce a new application type to
    manage all application that do NOT use *app_efl_main() function.

    *In this way, we can manage the argument given through the bundle
    before start the classic application.


launch_app MiniBrowser works fine. Do you need the appcore callbacks to be working with MiniBrowser too?

One thing I've noticed with MiniBrowser and app fw is related to browser.xml:

See this line:
<ui-application appid="MiniBrowser" exec="/usr/bin/browser" nodisplay="false" multiple="false" type="capp" taskmanage="true">

on ivi /usr/bin/browser is a shell script to start MiniBrowser. Once started, the process name is MiniBrowser. However, the app fw uses exec="" field and /proc fs to find if the app is running and what's the pid vs appid mapping. It fails because
there's no such process '/usr/bin/browser'.

In user point of view, there is no fails, that works : a Minibrowser is launched and display google web page. In fact, /usr/bin/browser is a script that calls "Minibrowser www.google.com".

root@ivi_box:/usr/share/dbus-1/services# cat /usr/bin/browser
#!/bin/bash

exec /usr/bin/MiniBrowser http://www.google.com


There is a Minibrowser that displays google.com.Seems correct but not perfect for TIVI-1491 <https://bugs.tizen.org/jira/browse/TIVI-1491>. Indeed especially in the case of TIVI 1491 we need to start Minibrowser with 123.com as argument not google.com.


As script override arguments, we need to change it or call Minibrowser binary, but as I said and Young seems to confirm this point, Minibrowser is call with encrypted arguments related to Application Framework.
To have my symptom, I tested this script changes:
cat /usr/bin/browser
#!/bin/bash

exec /usr/bin/MiniBrowser $1

Thanks




-- Mikko


_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to