Hi, Before the wiki update I can write it here
1) The following features are applied to the service process --disable-sysapps --disable-raw-sockets --disable-device-capabilities --enable-dialog --remote-debugging-port So, for un/setting of these features a tester/developer should: a) kill xwalk if it is launched (service process terminates if there are no running apps) b) modify the "/usr/lib/systemd/user/xwalk.service" file (add required cmd line args from the list above) c) launch an application using xwalk-launcher 2) The "--fullscreen" command line option is application-specific, it should not require restarting of service process to enable fullscreen mode tester/developer should launch: xwalk-launcher <app-id> --fullscreen This was reached with https://github.com/crosswalk-project/crosswalk/pull/1719 (recently landed) BR, Mikhail ________________________________________ From: Li, Cici X Sent: Thursday, March 20, 2014 11:28 AM To: Pozdnyakov, Mikhail; [email protected] Subject: RE: Some Crosswalk “Run as service” mode changing influnce points confirm Mikhail, thanks for your notify. Look forward to your wiki update:) -----Original Message----- From: Pozdnyakov, Mikhail Sent: Wednesday, March 19, 2014 6:46 PM To: Li, Cici X; [email protected] Subject: RE: Some Crosswalk “Run as service” mode changing influnce points confirm Hi, I think it is better rather to provide the mentioned cmd line argumentss for xwalk-launcher instead of xwalk service itself, so that there is no need to kill the service process and to resolve interesting situations if more than 1 app is launched - like do we apply the same cmd line arguments to all launched the apps? The patch is on the way, I will update the wiki after it is landed. BR, Mikhail ________________________________________ From: Li, Cici X Sent: Wednesday, March 19, 2014 4:00 AM To: Pozdnyakov, Mikhail; [email protected] Subject: RE: Some Crosswalk “Run as service” mode changing influnce points confirm Hi, Mikhail and all For xwalk command line options which support in old mode, will they also support under run as service mode? If support, what's the detail usage? Do we have a wiki page or feature to describe them? Xwalk detailed command line usage in old mode: https://github.com/crosswalk-project/crosswalk-website/wiki/Crosswalk-Command-Line-Options include --data-path, --fullscreen, --list-features-flags and so on. e.g. Flags for features (JIRA: XWALK-455) Old way: Check flag features: xwalk --list-features-flags, Disable features: e.g. xwalk --disable-device-capabilities Question: will this feature still support under run as service mode? If, use which command? (is "xwalk --run-as-service --list-features-flags" or others?) QA also do some test and result as below, please check: First kill all xwalk service (if xwalk service process is running), then execute the following command: 1. xwalk --list-features-flags (pass, can list all the features flags) 2. xwalk --run-as-service --list-features-flags (pass, can list all the features flags) 3. xwalk --run-as-service --disable-device-capabilities id (fail to launch app) 4. xwalk --run-as-service --fullscreen idxxxxxxxxx (fail to launch app) Thanks cici -----Original Message----- From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Li, Cici X Sent: Monday, March 17, 2014 9:44 AM To: Pozdnyakov, Mikhail; [email protected] Subject: Re: [Crosswalk-dev] Some Crosswalk “Run as service” mode changing influnce points confirm Hi, Mikhail Thanks for your clarify. Per your comments, QA will keep "xwalk url" in our tests, file bug if it have issues. Xwalk --install/uninstall under updating from our tests/tools, and will switch to "run as service" mode according https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2014-January/000954.html. Thanks cici -----Original Message----- From: Pozdnyakov, Mikhail Sent: Friday, March 14, 2014 5:12 PM To: Li, Cici X; [email protected] Subject: RE: Some Crosswalk “Run as service” mode changing influnce points confirm Hi there, I'll try to answer in the same order the points were listed 1., 2. "xwalk url" for arbitrary URLs should work fine - no changes have been made there or planned to be made (at least I'm not aware of such plans :) ). Even though the *installed* apps on Tizen should be invoked using "xwalk-launcher". 3. The application installation on Tizen is now possible only as described at https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2014-January/000954.html xwalk --install (and xwalk --uninstall) is not supported any more on TIzen. BR, Mikhail ________________________________________ From: Crosswalk-dev [[email protected]] on behalf of Li, Cici X [[email protected]] Sent: Friday, March 14, 2014 5:32 AM To: [email protected] Subject: [Crosswalk-dev] Some Crosswalk “Run as service” mode changing influnce points confirm Hi, all QA want to confirm some points about “Run as service” mode changing here. 1. We use “xwalk url” to access some url directly in crosswalk old(non-service) mode, after switch to “Run as service” mode, will this continue support? Ø If still support via command line, how to use it under “Run as service” mode? e.g. Any run as service mode "xwalk-launcher" methods to replace "xwalk http://www.<http://www.hao123.com/>baidu.com" We need the detail command usage here to update relate tests if have. Ø If not support via command line, will Crosswalk support package url via host app way? If have, can you share the schedule? It blocked some tests currently. Below is the host app in Tizen wrt spec, please take as reference: 0020. Hosted Web Application: o Web Application is packaged according to W3C Widget Packaging and XML Configuration, except having an externally hosted document as the start page (see Tizen Configuration Extensions). 0240. Tizen Hosted Web Application Element <tizen:content /> Description In the W3C Widget Packaging and XML Configuration, the Web Application start page is a document contained inside the widget package itself. Tizen WRT allows the start page to be hosted on an external server. The <tizen:content /> element is used to point to the relevant document. If both <content> and <tizen:content> elements are specified, only the <tizen:content> element is considered. Context Child of the <widget> element Occurrence 0 or more; if more than 1, then the first occurrence MUST be considered (and all others ignored). Attributes src (mandatory, URI of an external start page) Example <tizen:content src="https://www.tizen.org/"; /> 2. Bugs block to recheck Some bugs retest blocked by “xwalk url” changing after switch to “run as service” mode (QA try to use run as service mode to retest bugs to replace non-service mode steps like "xwalk url" 3. “Run as service” mode wiki update In the relate JIRA features, XWALK-87<https://crosswalk-project.org/jira/browse/XWALK-87>, it have a page https://lists.crosswalk-project.org/pipermail/crosswalk-dev/2014-January/000954.html to description the detail usage of “Run as service” mode, but no launch command usage in it. We suggest to have a wiki to record the “run as service” full and detail usage. Thanks Cici _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev --------------------------------------------------------------------- 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 [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
