Hi Shiliu, still a question on this:
Shiliu: Totally agree with you. With the new structure. If a developer wants to directly develop based on Crosswalk, he needs to 1. Download xwalk_app_template.tar.gz directly. 2. Unzip the tarball 3. Cd xwalk_app_template 4. Create manifest if he wants to. 5. Run make_apk.py according to wiki 6. Publish the generated apk. Doesn't the user need to download also the xwalk arch-specific binaries? Francesco From: Wang, Shiliu Sent: Friday, March 14, 2014 7:37 AM To: Balestrieri, Francesco; Kubo Da Costa, Raphael; Hu, Ningxin; Zhu, Yongsheng Cc: Yu, Zhiqiang; [email protected] Subject: RE: Proposal on how to organize our download binaries for public users Hi, Francesco Thanks for the comments. See my answer below. - somewhere else we are discussing the need for a single tool/package for both ARM and IA. So eventually would the ARM and x86 folders merge into one? Shiliu: For xwalk_app_template, yes. But for cordova.tar.gz and other apks, arm and x86 will still be separated. - I didn't understand the purpose of "Canary1", "Canary2" etc Shiliu: "Canary1" and "Canary2" are just short for different versions. I was just using 1,2,3 to replace real version number like 5.34.99.0. Sorry for the confusing. - In my opinion we should bake Cordova support in the main crosswalk archive as well Shiliu: yes, that's cordova.tar.gz. for. You might take the first two colored structures as my proposal, they are the current status. My proposal is the last one. I should use some different color, sorry for the misleading. Android/ Canary/ Canary1/ Xwalk_app_tempalte.tar.gz X86/ Cordova.tar.gz Xwalk.zip (including runtimelib and helloworld) Xwalk_tests.zip (including tests apk and shell apk) arm/ Cordova.tar.gz Xwalk.zip (including runtimelib and helloworld) Xwalk_tests.zip (including tests apk and shell apk) Canary2/ Similar to canary1 Beta/ Similar to Canary What I think we should aim for is that a developer who wants to use Crosswalk needs to follow something like these steps: - download and unzip package - if needed, give one install command - cd to their web or Cordova app - if needed, create a manifest - run package script - Publish to app store Shiliu: Totally agree with you. With the new structure. If a developer wants to directly develop based on Crosswalk, he needs to 1. Download xwalk_app_template.tar.gz directly. 2. Unzip the tarball 3. Cd xwalk_app_template 4. Create manifest if he wants to. 5. Run make_apk.py according to wiki 6. Publish the generated apk. Exactly like what you suggest. :) If he wants to adopt cordova container, steps are probably the same, just he needs to download different package for arm/x86. The main idea is to host each tool separately instead of merge them in a super large zip. The pros is to have less download size for end user and less steps to extract the super zip. Thanks, Shiliu. From: Balestrieri, Francesco Sent: Friday, March 14, 2014 1:09 PM To: Wang, Shiliu; Kubo Da Costa, Raphael; Hu, Ningxin; Zhu, Yongsheng Cc: Yu, Zhiqiang; [email protected]<mailto:[email protected]> Subject: RE: Proposal on how to organize our download binaries for public users Hi, a few comments: - somewhere else we are discussing the need for a single tool/package for both ARM and IA. So eventually would the ARM and x86 folders merge into one? - I didn't understand the purpose of "Canary1", "Canary2" etc - In my opinion we should bake Cordova support in the main crosswalk archive as well What I think we should aim for is that a developer who wants to use Crosswalk needs to follow something like these steps: - download and unzip package - if needed, give one install command - cd to their web or Cordova app - if needed, create a manifest - run package script - Publish to app store From: Wang, Shiliu Sent: Friday, March 14, 2014 4:45 AM To: Balestrieri, Francesco; Kubo Da Costa, Raphael; Hu, Ningxin; Zhu, Yongsheng Cc: Yu, Zhiqiang; [email protected]<mailto:[email protected]> Subject: Proposal on how to organize our download binaries for public users Hi, All Per https://crosswalk-project.org/jira/browse/XWALK-898 , https://crosswalk-project.org/jira/browse/XWALK-1013, https://crosswalk-project.org/jira/browse/XWALK-670 . They are all about the requirement for the binaries we deliver to public. Currently our binaries are organized like Android_arm/ Canary/ Canary1.zip Canary2.zip Beta/ Beta1.zip Android_x86/ Canary/ Canary1.zip Beta/ Beta1.zip And within the zip it will be: Crosswalk-version-arch.zip/ Apks/ Bunch of apks. Xwalk_app_template.tar.gz Xwalk_core_library.tar.gz >From the Jira issues, the requirement is to: 1. Provide cordova.tar.gz for download, which is basically crosswalk_cordova_android code + xwalk_core_library.tar.gz . 2. Provide one xwalk_app_template.tar.gz for both x86 and arm. Based on following facts: 1. Xwalk_app_template.tar.gz is enough for web developer to use xwalk. 2. Cordova.tar.gz is also functional independent itself. I propose to organize our release to public following way Android/ Canary/ Canary1/ Xwalk_app_tempalte.tar.gz X86/ Cordova.tar.gz Xwalk.zip (including runtimelib and helloworld) Xwalk_debug.zip (including tests apk and shell apk) arm/ Cordova.tar.gz Xwalk.zip (including runtimelib and helloworld) Xwalk_debug.zip (including tests apk and shell apk) Canary2/ Similar to canary1 Beta/ Similar to Canary The gaps from current status will be 1. Generate cordova.tar.gz 2. Generate one xwalk_app_template.tar.gz including both archs native libraries. 3. Reorganize the folder structure. Thanks, Shiliu. --------------------------------------------------------------------- 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
