Mikhail, Can I understand that you will add support to xwalk (instead of xwalkctl) install/launch crosswalk application on desktop? I am confused because user can install crosswalk application using xwalk(not xwalkctl) two month ago. What's the difference between your new intent with original?
Thanks Zhang Xu > -----Original Message----- > From: Pozdnyakov, Mikhail > Sent: Thursday, September 4, 2014 4:10 PM > To: Zhang, Xu U; crosswalk-dev@lists.crosswalk-project.org > Subject: RE: [Crosswalk-dev] [Intent to implement] Better user experience on > desktop > > Hi, > > [Zhang Xu] For widget package, what is the URL? > by 'URL' I mean some external URL, let's say "browser mode". For the widget > package its local path should be used. > > [Zhang Xu] There is no manifest file for unpacked widget file. So how do you > plan to implement it? > Do not quite understand the question, at the moment we're using config.xml > from the .wgt package -- nothing new there. > > BR, > Mikhail > > ________________________________________ > From: Zhang, Xu U > Sent: Thursday, September 04, 2014 10:59 AM > To: Pozdnyakov, Mikhail; crosswalk-dev@lists.crosswalk-project.org > Subject: RE: [Crosswalk-dev] [Intent to implement] Better user experience on > desktop > > I have two questions as below: > 1) Run arbitrary URL (this is already done) -> xwalk http://someurl.com [Zhang > Xu] For widget package, what is the URL? > > 3) Run packed application -> xwalk path/to/my_app.xpk This is not supported > now. Crosswalk could unpack the app to a temporary directory and erase it > after the execution. > [Zhang Xu] There is no manifest file for unpacked widget file. So how do you > plan to implement it? > > Best Regards > Zhang Xu > > > -----Original Message----- > > From: Crosswalk-dev > > [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org] On Behalf > > Of Pozdnyakov, Mikhail > > Sent: Wednesday, September 3, 2014 5:30 PM > > To: crosswalk-dev@lists.crosswalk-project.org > > Subject: [Crosswalk-dev] [Intent to implement] Better user experience > > on desktop > > > > Hi there, > > > > At the moment the Crosswalk desktop user should do the following steps > > to run an xwalk application (.xpk or .wgt) > > 1) "install" it using xwalkctl (means recording it application > > storage) > > 2) obtain the generated app_id > > 3) finally run the app via id > > > > Apparently this logic was designed for Tizen where Crosswalk is used > > as the platform web-runtime. > > This scenario however looks really weird on desktop as it contains > > home-brewed application management (which is apart from the platform > > application management on desktop) and forces the User to be aware of > > some generated app id. > > > > I propose us to drop this scenario on desktop and support the > > following scenarios there: > > > > 1) Run arbitrary URL (this is already done) -> xwalk > > http://someurl.com > > 2) Run the unpacked application -> xwalk local/path/to/manifest.json > > At the moment Crosswalk can run the unpacked app from the path to *the > > directory containing manifest.json* I propose to use instead path to the > manifest file. > > 3) Run packed application -> xwalk path/to/my_app.xpk This is not > > supported now. Crosswalk could unpack the app to a temporary directory > > and erase it after the execution. > > > > Doing this also allows us to move all the application storage & > > application management code to 'tizen' folder and remove the > > unnecessary abstraction code. > > This should significantly simplify our code in 'application' folder. > > > > BR, > > Mikhail > > --------------------------------------------------------------------- > > Intel Finland Oy > > Registered Address: PL 281, 00181 Helsinki Business Identity Code: > > 0357606 - 4 Domiciled in Helsinki > > > > This e-mail and any attachments may contain confidential material for > > the sole use of the intended recipient(s). Any review or distribution > > by others is strictly prohibited. If you are not the intended > > recipient, please contact the sender and delete all copies. > > > > _______________________________________________ > > Crosswalk-dev mailing list > > Crosswalk-dev@lists.crosswalk-project.org > > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
