There aren't any inherent issues in 10.2 that I'm aware of. Any chance yo can send me the BAR file (eoros@blackberry.com) and I will give it a test here?

What sort of troubles were you seeing? How far did it actually get? Did it crash or freeze? etc.

I'm not sure the plugin will play well if tested on anything but a physical device. I will take a look though to see if that can be smoothed out. The main issue is that Ripple does not itself support BlackBerry Messenger or In-App Payment WebWorks APIs; nor would a standard browser.

At the same time, if there is anything you would like me to test on a physical device, feel free to email it to me (eoros@blackberry.com).

Cheers

Correct, we're working to implement the HTML5 Gamepad API which would open this up; it's one of the three major asks I have submitted in relation to HTML5 Gaming (others being Web Audio API and Scoreloop for WebWorks.)

I don't have a timeline on Gamepad API support just yet, but once it's available it would be great to see some next-gen control integration.

Hi there, you should still be able to receive keys in the original manner. The BBID signature keys do not apply to our HTML5 (WebWorks) platform yet, and you should actually still be using the previous method there.

On the code signing request form, there is a checkbox for WebWorks. Specifically:

For BlackBerry PlayBook apps developed using BlackBerry WebWorks, BlackBerry NDK, or AIR - AND - For BlackBerry 10 apps developed using BlackBerry WebWorks, or the BlackBerry 10.2 Beta SDK or earlier.

This can be found here:

blackberry.com/SignedKeys/codesigning.html

Which part isn't working avinashizhere? Are you testing on a physical device or within the browser? If you have a BAR file, I'm happy to give it a go here to see if I can narrow down any issues.

A little more information would help, and I'm happy to help resolve any issues you're seeing.

Cheers!

Hm, odd behaviour. Would you be willing to fire me the BAR file so I can test it on a device here?

I haven't tried with such a large world (30000-50000) but in theory that shouldn't really be an issue.

I'm also not *totally* understanding that "one object causes the game to flash back". Does it happen immediately when you try to load the game or during game play?

You indicated that one object seems to be causing the break (fixed if that object is removed), but the object can vary? How do you identify the object?

Would love to get this sorted as it seems like a rather solid title you've put together. Just need a bit more information to make sure I'm understanding correctly.

Hello all,

I just wanted to start a thread for some "official" discussion for this plugin:

github.com/blackberry/Construct2Plugins

Currently the supported functionality includes:

BlackBerry Messenger

• Invite To Download
• Update Personal Status Message

In-App Payments

• Purchase Digital Good
• Get Existing Purchases
• Get Digital Good Price
• Check If Digital Good Is Purchased

If you are developing for BlackBerry 10 and end up using this plugin, it would be great to get feedback on your experience.

That being said, what else would you like to see added?

Woo!

Release 1 of the BlackBerry 10 plugin for Construct 2 is now live!

github.com/blackberry/Construct2Plugins

Thank you again for everyone's patience. Let me know if you have any feedback!

A blog post on devblog.blackberry.com will show up soon with some more information, but hopefully the repo is a good starting point.

If anyone else comes along to this thread, just wanted to share this so you can see my final implementation:

github.com/blackberry/Construct2Plugins

Ah, I assumed accessing those Expressions worked the same way as accessing a Condition to be triggered. But can see the flaw in that now. I will give this a try and will let you know. Thanks again for the insight!

Edit: I took a look at the WebSocket plugin and I have been misusing Extensions. It's all coming together now...

Solved: I was using Expressions as variables instead of functions that return values based on variables; if that makes sense. Looking at some of the other plugins made it clear and (pending final testing) stay tuned for BlackBerry Messenger (Register, Set Status, and Invite Others To Download) and In-App Payment (Purchase Good, Check Good Price, and Get Existing Purchases List) being made available in the coming days.

Thanks again!

It's taken a little longer than expected and I really appreciate everyone's patience. I'm in the final stages; I've managed to make the purchases usable now, just having a slight issue with the sequence of actions. Will let everyone know as soon as it's up.

Edit: All remaining functionality has been implemented. Barring any issues during my final testing, I should have a Github pull request and documentation ready to go this week! Stay tuned!

Edit: Initial testing looks good! Github pull request going in today. Will post the direct link once it's up.

Thanks Ashley, I've managed to make some good progress and am just short of being complete. I have one last issue in the sample I am creating. You can see my defined event flow here.

On loader layout completion, I...

Log the progress.

Call GetExistingPurchases.

Call RegisterBBM.

This part seems to work fine, and GetExistingPurchases will either trigger success or failure as follows.

<pre 100="">...

blackberry.payment.getExistingPurchases(

     true,

     function onSuccess(data) {

          cr.plugins_.blackberry10.prototype.exps.existingPurchases = JSON.stringify(data);

          _this.runtime.trigger(cr.plugins_.blackberry10.prototype.cnds.onGetPurchasesSuccess, _this);

     },

     function onFailure(error) {

          cr.plugins_.blackberry10.prototype.exps.PaymentError = error.errorText + ' (' + error.errorID + ')';

          _this.runtime.trigger(cr.plugins_.blackberry10.prototype.cnds.onGetPurchasesFailure, _this);

     }

);

...</pre>So far, we're good. The request actually fails (since I've been side-loading and there is no connection to the Payment servers yet.) So, in the diagram, BlackBerry10.onGetPurchasesFailure is triggered as expected.

However, my output is only:

Payment (Failure): Get existing purchases.

Where I would expect two additional lines to be logged as well. Specifically:

1) A newline and the contents of PaymentError.

2) A new line and "Shazam2!"

But neither of those two actually show; it's as if something stops execution, but Web Inspector logs no errors.

If I need to clarify anything at all, please just let me know. I'll continue hammering away here, but if anybody has any insight, again I'm happy to hear it.

Cheers!