Mobile apps are mainly registered as 'capp'.
But as I said , Minibrowser do not use *appcore-common* libraries.
This is not the case for the Minibrowser.
For example, see the code of the EFL mobile browser
(review.tizen.org:apps/web/browser):
int main(int argc, char *argv[])
{
__br_set_env();
app_event_callback_s ops;
memset(&ops, 0x0, sizeof(app_event_callback_s));
ops.create = __br_app_create;
ops.terminate = __br_app_terminate;
ops.pause = __br_app_pause;
ops.resume = __br_app_resume;
ops.service = __br_app_reset;
ops.low_memory = __br_low_memory_cb;
ops.low_battery = __br_low_battery_cb;
#if defined(HORIZONTAL_UI)
ops.device_orientation = __br_rotate_cb;
#endif
ops.language_changed = __br_lang_changed_cb;
ops.region_format_changed = __br_region_changed_cb;
struct browser_data ad;
memset(&ad, 0x0, sizeof(struct browser_data));
* int ret = app_efl_main(&argc, &argv, &ops, &ad);*
return ret;
}
app_efl_main function permits to manage all arguments given through the
bundle.
Thanks for your feedback.
Le 18/11/2013 16:28, Rusty Lynch a écrit :
Mobile already has a set of efl apps. How are these apps registered?
On Mon, 2013-11-18 at 14:59 +0100, Baptiste DURAND wrote:
Hello all,
I'm working on TIVI-1491:This defect is not IVI specific.
The goal to fix it is to start a Minibrowser of webkit through the
current Application Framework.
But, Minibrowser of Webkit is not an OSP application neither a WGT
application, just a "classic" application.
I added some applications services in the browser manifest.
cat /usr/share/packages/browser.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns="http://tizen.org/ns/packages"; package="MiniBrowser"
version="0.1.3" install-location="internal-only">
<label>MiniBrowser</label>
<description>Sample Webkit Browser</description>
<ui-application appid="MiniBrowser" exec="/usr/bin/browser"
nodisplay="false" multiple="false" type="capp" taskmanage="true">
<icon>browser.png</icon>
<label>MiniBrowser</label>
<label xml:lang="en-gb">MiniBrowser</label>
<label xml:lang="en-us">MiniBrowser</label>
<application-service>
<operation name="http://tizen.org/appcontrol/operation/view"/>
<uri name="http"/>
<uri name="https"/>
<uri name="rtsp"/>
<uri name="rtp"/>
</application-service>
</ui-application>
What I saw after the modification of the manifest is :
app 681 0.0 0.7 250168 60940 ? SLsl nov.18
0:00 /usr/bin/MiniBrowser `zaybxcwdveuftgsh`
Minibrowser is launched with a wrong argument :
/usr/bin/MiniBrowser `zaybxcwdveuftgsh` instead
of /usr/bin/MiniBrowser 123.com
I tried to change the app type by "c++app" but I had the same result.
I see that the main arguments of the bundle are used to launch the
app. (this arguments are used only by Tizen specific applications)
(example of argument `zaybxcwdveuftgsh` __AUL_STARTTIME__
NAAAAAEEAAASAAAAX19BVUxfU1RBUlRUSU1FX18AEgAAADEzODQ3NzAxNjIvODI0MTQ5AA==
__AUL_CALLER_PID__ JwAAAAEEAAATAAAAX19 )
As having OSP Framework is not mandatory for all TIZEN profiles,
What I propose is to add a new application Type 'stdapp' wich
associated to an other AMD Application Type 'stdapp'.
This type will be checked before the real launch in
__launchpad_main_loop() function.
At this step we can adjust the bundle before real_launch function. (=>
remove the useless argument for stdapp application type only).
By this way, we use the same launchpad for OSP and "classic"
applications.
What do you think about this proposition ?
Thanks
--
Baptiste DURAND
Intel OTC - Vannes/FR
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
