Crosswalk Intel XDK experiences

  • Crosswalk has been updated in the build system. Beta is Crosswalk 7 and stable is 6. After the build log completes, you can now see what version of crosswalk was used in the build log. The crosswalk in the debug tab has also been updated to v7.

    We fell behind in updates because of the cordova changes, so I expect we will update to crosswalk 8 soon. I see that gamepad is supported in v8.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • I just did a brief test on Space Blaster. Impressive!

    Question IntelRobert

    Why does it has the "Touch To Start" at the beginning ? how to disable this ?

    Back button does not work and there is no way to exit the game ?

    Can I request that you create a new thread and post the FAQ, tips, guides and everything there on the first page. At least you can post us the updates, progress, release notes, changelogs on the first page. I doubt everyone wants to read the whole 37 pages.

  • tumira

    For exiting via back button, add the Browser object to your game, then put in a code, On back button pressed = Browser > Close

    It should quit the game, and works last I tried it.

  • I think chrome browser does not let you start sound unless responding to a user event so the touch to start was put in. Crosswalk does not have this restriction so the touch to start is not necessary. I am not sure how to get rid of it, but it is coming from the game and not crosswalk so others on the forum should be able to help you.

    We will work on better documentation. I will update Ashley's tutorial for the features and UI.

    I just did a brief test on Space Blaster. Impressive!

    Question IntelRobert

    Why does it has the "Touch To Start" at the beginning ? how to disable this ?

    Back button does not work and there is no way to exit the game ?

    Can I request that you create a new thread and post the FAQ, tips, guides and everything there on the first page. At least you can post us the updates, progress, release notes, changelogs on the first page. I doubt everyone wants to read the whole 37 pages.

  • IntelRobert

    I have used the newest XDK beta. I have an issue with the large number of splash and icon files that are generated in the apk (in RES directory) and most of them we have no way to change in XDK, so we end up with a lot of green snail icons and "cube" splash screens.

    Also the splash screens & icons I can change in XDK need to be saved in the www directory, so these are included 2 times in the apk! On top of that C2 is also creating icons of different sizes on its own, and these too are being included for nothing!

    I think we need to have BETTER control & management over the splash screens and icons, and have the option to be able to change all of them in the options screen.

    apart from that all works perfectly

  • I made a bug tracker for this item. I don't think there will be a fix for this soon since they are focused on ads, payment, expansion files, game services, and general build issues, but hopefully it can be part of a general cleanup of project structure in the future.

    IntelRobert

    I have used the newest XDK beta. I have an issue with the large number of splash and icon files that are generated in the apk (in RES directory) and most of them we have no way to change in XDK, so we end up with a lot of green snail icons and "cube" splash screens.

    Also the splash screens & icons I can change in XDK need to be saved in the www directory, so these are included 2 times in the apk! On top of that C2 is also creating icons of different sizes on its own, and these too are being included for nothing!

    I think we need to have BETTER control & management over the splash screens and icons, and have the option to be able to change all of them in the options screen.

    apart from that all works perfectly

  • Expansion files sound really nice!

  • When you publish your crosswalk app, you have to upload 2 APKs one for ARM and one for x86 to work on the most devices. The build email will have a link to a zip file with both of them. The build email also has a link to page that describes the extra step to publish multiple APKs. It is only a few extra clicks and an additional upload. If you have published with crosswalk, please publish both because when you only publish the ARM APK, it won't work on Intel phones and tablets.

    For those of you who have published just ARM, I am curious about why. Not aware that you need to publish both, don't know how, or some other reason? Please send me PM or post here.

    Recently, google has announced some APIs that might make it possible for us to automate the uploading of APKs to google play. We hope to add this feature to XDK soon so you can skip the download/upload of APK and other assets--there would be a button on XDK that would do most of that for you. But we recognize that some of you prefer to sign yourself so we still need to understand what it will take to get developers to publish ARM & x86

  • I use to do just ARM but now x86 as well, just wasn't aware at first. it's easy and quick to just upload both so.

    Google play store in publishing ARM it supported 5200+ devices, but the x86 it mentions only 120 devices.

  • IntelRobert

    Any idea as to when we can expect IAP to be implemented. I'm sure many are ready to jump to crosswalk if/when it gets a working IAP system.

  • IntelRobert

    Automate uploading to Google play store is a nice feature for new application. But for someone who are from CocoonJS might need to sign and upload manually since we need to sign the apk with our own key. So I hope you still give the option for us to sign the apk manually.

    Most of us would probably jump to crosswalk(arm&x86) when ads,iap, google play services are available.

  • We will look at a workflow where the developer does the signing for the automated publishing. We should just add a step that runs the signing utility on the developer computer using the local keys.

    IntelRobert

    Automate uploading to Google play store is a nice feature for new application. But for someone who are from CocoonJS might need to sign and upload manually since we need to sign the apk with our own key. So I hope you still give the option for us to sign the apk manually.

    Most of us would probably jump to crosswalk(arm&x86) when ads,iap, google play services are available.

  • We will look at a workflow where the developer does the signing for the automated publishing. We should just add a step that runs the signing utility on the developer computer using the local keys.

    > IntelRobert

    >

    > Automate uploading to Google play store is a nice feature for new application. But for someone who are from CocoonJS might need to sign and upload manually since we need to sign the apk with our own key. So I hope you still give the option for us to sign the apk manually.

    >

    > Most of us would probably jump to crosswalk(arm&x86) when ads,iap, google play services are available.

    >

    It's best if its just an option in the workflow, sign or unsigned APKs.

  • can we download and save the key that XDK uses to sign the apk to use it in the future with other sdks etc?

  • guys i need a help to run an app in background, im made a pedometer, but i need the app run when you block the phone...

    im stuck like a month in this.

    I search in the forum, but i can't find something usefull.

    some idea IntelRobert

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)