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
