Re: [Crosswalk-dev] Intent to implement -- Keyboard detection extension

eyboard is visible. > > Kenneth > > On Tue, Jun 7, 2016 at 2:16 PM Staudinger, Robert > <robert.staudin...@intel.com> wrote: >> >> On 7 June 2016 at 13:41, Kenneth Rohde Christiansen >> <kenneth.christian...@gmail.com> wrote: >> > No, it woul

Re: [Crosswalk-dev] Intent to implement -- Keyboard detection extension

On 7 June 2016 at 13:41, Kenneth Rohde Christiansen wrote: > No, it would return a keyboard with isPhysical being false :-) > > The things is, a primary keyboard can be physical (2 in 1 attached or fixed > physical keyboard) or virtual (tablets, which might have

Re: [Crosswalk-dev] Intent to implement -- Keyboard detection extension

On 7 June 2016 at 11:40, Kenneth Rohde Christiansen wrote: > OK, I see. I had expected something a bit more thought out already. The question is hardware availability vs semantics -- what does it mean to the operating system. On Windows 8/10 you can go into touch

Re: [Crosswalk-dev] Intent to implement -- Keyboard detection extension

On 7 June 2016 at 09:55, Kenneth Rohde Christiansen wrote: > Is there any design document, showing the potential APIs etc? We are providing low level primitives that can be used in conjunction with other APIs (gyro, rotation, ...) The initial API is along the

[Crosswalk-dev] Announcing Crosswalk-app-tools 0.10.4

# Announcing Crosswalk-app-tools 0.10.4 Highlight for this release are much improved Windows support for high-dpi devices, and improvements for the Android crosswalk-lite flavor, which minimizes app download size for use on slow networks, as well as internal improvements for faster builds in

[Crosswalk-dev] Intent to implement -- Keyboard detection extension

== Abstract Crosswalk extension module providing low level primitives for querying whether the host operating system has a physical keyboard attached. This information can be used by app authors to optimise application appearance and behaviour on convertible devices such as laptop/tablet hybrid

Re: [Crosswalk-dev] Intent to Implement : auto start of Crosswalk applications without command line arguments.

Hi Alexis, what if we just used a hard-coded name for the subdirectory that holds the app content? E.g. com.example.foo/ + xwalk.exe + locales/ + pak etc + wwwroot/ (for lack of a better name, maybe approot/ ... you get the idea) + etc ... On startup, xwalk would always

[Crosswalk-dev] Announcing Crosswalk-app-tools 0.9

# Announcing Crosswalk-app-tools 0.9 Highlight for this release is the ability to build Android APK- as well as Windows MSI packages in a single run. Additionally the startup behaviour for Android apps has been improved, showing the app icon as a splash screen while initialising. Finally, various

[Crosswalk-dev] Announcing Crosswalk-app-tools 0.8

# Announcing Crosswalk-app-tools 0.8 Crosswalk-app-tools 0.8 is our first release with fully enabled support for the creation of Windows MSI installers[1]. Another major new feature is support for 64-bit Android devices[2]. Additionally numerous enhancements and refinements have been made to the

[Crosswalk-dev] Announcing Crosswalk-app-tools 0.7

# Announcing Crosswalk-app-tools 0.7 Crosswalk-app-tools 0.7 is a big milestone for our Node.js based tools for Crosswalk application development. We are inviting everyone to start creating the app of your dreams today. ## 0.7 Release Highlights * A new tool that makes packaging as easy as

Re: [Crosswalk-dev] Intent to Implement -- Silent Download Mode for Crosswalk Android

t;, developer's server can > send back 32bit runtime APK as he knows for sure his application only runs in > 32bit process. > 3) the multiple architecture support in Apk download is also missing in > shared mode, this will also apply to shared mode. > > Thanks > Xiaos

[Crosswalk-dev] Crosswalk-app-tools 0.7 branched

Hello, A branch for the upcoming 0.7 release of crosswalk-app-tools has been created: https://github.com/crosswalk-project/crosswalk-app-tools/tree/0.7 This means that master is open for features. I have started to tag issues that can be fixed between coffee and cookies with an "easy-fix" label,

[Crosswalk-dev] Crosswalk-app-tools feature freeze

Hello, After an intense development cycle we are closing the crosswalk-app-tools master branch for feature development. Over the next few days the focus will be on testing and fixing a few remaining issues. If you want to get an early impression of what's coming, or maybe help out with the

Re: [Crosswalk-dev] Intent to implement -- Expansion mode for Android

On 13 August 2015 at 02:36, Xu, Xing xing...@intel.com wrote: LGTM. But I have one question, is it possible to share expansion file among multiple apks? For the name scheme of expansion files, it should be named with package-name: [main|patch].expansion-version.package-name.obb Yes, the

Re: [Crosswalk-dev] Intent to implement -- Expansion mode for Android

Hengzhi, Alexis, anyone -- comments or LGTMs? On 5 August 2015 at 10:04, Staudinger, Robert robert.staudin...@intel.com wrote: On 4 August 2015 at 09:25, Sun, Lin lin@intel.com wrote: Great idea! Could you explain how would you treat XWalkRuntimeLib.apk after downloaded the expansion

[Crosswalk-dev] Announcing Crosswalk-app-tools 0.6

Announcing Crosswalk-app-tools 0.6 == While many of you have hopefully picked up a healthy tan on the beach, we have strictly been limiting our exposure to TCO[1] emission levels, for being able to finish version 0.6 of Crosswalk-app-tools. This is a milestone

Re: [Crosswalk-dev] Intent to implement -- Expansion mode for Android

On 4 August 2015 at 09:25, Sun, Lin lin@intel.com wrote: Great idea! Could you explain how would you treat XWalkRuntimeLib.apk after downloaded the expansion file and extracted the APK file? I’m also interested with the approach of findExpansionCore(). The XWalkRuntimeLib.apk will be

Re: [Crosswalk-dev] Crosswalk Project for Linux Regression Report on 15.44.380.0-BLOCK

[private reply] On 4 August 2015 at 07:41, Jiang, WenhaoX wenhaox.ji...@intel.com wrote: Regression testing on Crosswalk_15.44.380.0 for Deepin and Ubuntu are totally blocked due to fail to build related packages: P1 issue XWALK-4723 [app-tools][REG] Fail to build project on Deepin backend I

[Crosswalk-dev] Crosswalk-app-tools 0.6 branched

Hello, I have branched[1] Crosswalk-app-tools for a new npm release later this week. Please give it a spin and report any issues you encounter. Noteworthy features since the last release are: * Windows is now supported as well as a development platform for Android apps, in addition to OSX and

[Crosswalk-dev] Intent to implement -- Expansion mode for Android

*Intent to implement:Expansion mode for Android* *Description* The size of crosswalk-enable packages has been a concern for a long time. With the 50MB size limit on the Google Play store, rich applications like games are having problems to meet the restriction. To mitigate this, I am proposing

Re: [Crosswalk-dev] Requiring Node.js 12 for Crosswalk-app-tools

On 20 May 2015 at 12:34, Raphael Kubo da Costa raphael.kubo.da.co...@intel.com wrote: I'm not sure about Windows and Mac though. You can download no problem https://nodejs.org/download/ ___ Crosswalk-dev mailing list

[Crosswalk-dev] Requiring Node.js 12 for Crosswalk-app-tools

Hello, any objections to requiring Node.js 12.x for Crosswalk-app-tools? There is some new API for spawning subprocesses that I would like to use. Opinions? - Rob ___ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org

Re: [Crosswalk-dev] Intent to Implement: LZMA support for Crosswalk

On 30 March 2015 at 05:07, Dong, Jun jun.d...@intel.com wrote: OK, we can ship an uncompressed library with make_apk, and this will consume some more time for their first time to enable the ‘use_lzma’ flag. But only for the developer when building the package, right? If there are no

Re: [Crosswalk-dev] Intent to Implement: LZMA support for Crosswalk

Halton, I have two questions about this: On 27 March 2015 at 12:15, Huo, Halton halton@intel.com wrote: +1 for Francesco’s idea about building out lzma and non-lzma support together and let app developer choose which to use. 1. Will the deflated library be stored on disk? That would only

Re: [Crosswalk-dev] [Crosswalk-help] Android Crosswalk and Content

Hello Belem, everyone, I was looking at the question from Kevin below. We have a similar issue in https://crosswalk-project.org/jira/browse/XWALK-2685 and you reference a test case there:

[Crosswalk-dev] Crosswalk-app-tools master moved to Crosswalk 9

tl;dr * Crosswalk-app-tools 0.1.0 works with Crosswalk 8 * Crosswalk-app-tools master works with Crosswalk 9 Reason: Due to changes in the name of Crosswalk application class (8: org.xwalk.app.runtime.XWalkRuntimeApplication / 9: org.xwalk.core.XWalkApplication) the boilerplate code changes. In

Re: [Crosswalk-dev] Announcing Crosswalk-app-tools 0.1.0

On 1 December 2014 at 07:58, Gao, Shawn shawn@intel.com wrote: Hi, Robert, I'm working around the crosswalk x64. Make_apk.py will be changed. Should I apply the changes based on your wok or still keep on make_apk.py? App-tools is in a very early development status, I think it would be

[Crosswalk-dev] Announcing Crosswalk-app-tools 0.1.0

Crosswalk-app-tools 0.1.0 = We are happy to announce Crosswalk-app-tools 0.1.0. This is the first technology preview milestone of our forthcoming Node.js based tools for Android app development. Deployment in a production environment is not encouraged at this time.

Re: [Crosswalk-dev] [Intent to Implement] [Android] Enable shared mode in xwalk core library

On 7 November 2014 04:30, Sun, Lin lin@intel.com wrote: But what if you have one app installed, and one shared crosswalk for it. Then you install another app, which requires an incompatible crosswalk Actually, there's the risk that if the new installed app requires a newer library than

[Crosswalk-dev] Intent to Implement - Javascript based packaging tool for Android

*Description* We have the python-based make-apk and our adopters each have their own set of tools, but they all make compromises in terms of workflow, dependencies, and integration. My plan is to offer a packaging tool written in JavaScript using node.js and distributed via NPM, that is as simple

Re: [Crosswalk-dev] [Intent to Implement] [Android] Enable shared mode in xwalk core library

On 5 November 2014 09:04, Sun, Lin lin@intel.com wrote: 1. Version Check The xwalk app will check the compatibility with the xwalk runtime library on device at startup time. If the version mismatched or the library even not exist, a dialog pops up to prompt users to get the suitable

Re: [Crosswalk-dev] [Intent to Implement] [Android] Enable shared mode in xwalk core library

On 6 November 2014 06:07, Sun, Lin lin@intel.com wrote: Hi Robert, So it will be possible to have several crosswalk lib APKs installed in parallel? No. It's not possible to have more than one crosswalk library apk installed. But what if you have one app installed, and one shared

Re: [Crosswalk-dev] Intent to Implement - Multiarch packages via expansion files

On 11 July 2014 03:33, Wang, Shiliu shiliu.w...@intel.com wrote: Hi, Robert My question is: 1) what will be the behavior if developer still chooses packaging for one CPU arch? Will it fallback to package the native library within the apk? And what’s the startup state flow in such

[Crosswalk-dev] Intent to Implement - Multiarch packages via expansion files

*Summary* Many developers, for various reasons, do not provide both IA and ARM packages for their Crosswalk-based applications. Changing the packaging mode to always deliver both runtimes via an expansion file will solve this problem. *Expansion File Info/Spec*

Re: [Crosswalk-dev] Intent to implement - Shared mode for xwalk core on Android

is able to publish their own library apk as long as changing the package name with little effort (we can provide tool to help). Thanks, Shiliu. -Original Message- From: Staudinger, Robert [mailto:robert.staudin...@intel.com] Sent: Tuesday, June 3, 2014 2:53 PM To: Wang, Shiliu Cc

Re: [Crosswalk-dev] multiple architecture

Hello Xavier, multiple APKs are supported on Android, the documentation can be found here: https://developer.android.com/google/play/publishing/multiple-apks.html We recommend using this approach for supporting both ARM- and IA/x86-based devices. A certain amount of testing can be done in the

Re: [Crosswalk-dev] Intent to implement - Shared mode for xwalk core on Android

Hello Shiliu, I have a few questions about this. * Where will the shared code be stored on the device? * How do you prevent malicious tampering (code injection) on the shared code, if it is accessible to other applications? * Who will publish the shared APK on Google Play? Many thanks, Rob

Re: [Crosswalk-dev] PSA: crosswalk master is now tracking Chromium 35

On 9 April 2014 19:57, Raphael Kubo da Costa raphael.kubo.da.co...@intel.com wrote: Android folks: you may need to wipe out your build directory to avoid getting some build errors. Additionally, the way you select which architecture to build for has changed in Chromium, see

Re: [Crosswalk-dev] C++11 in Tizen extensions code

On 25 March 2014 12:54, Kenneth Rohde Christiansen kenneth.christian...@gmail.com wrote: I think it would be great to document this on the wiki, like a list of which features are allowed with examples on how we can benefit from them. I'll look into that. - Rob