WaterlooErik's Forum Posts

  • The piece I'm unsure of is the initial setup. From the docs:

    • On start of layout, use the Add product ID action to add the product IDs you will be using, e.g. "product1,product2,product3".
    • After that (still in the 'Start of layout' event), use the Request store listing action. This starts downloading the names and prices of the given products. Some platforms require this information to be available for the IAP features to work.
    • When On store listing success triggers, the product names and prices are available, and purchases can start being made or checked with the Has product condition.

    With respect to BlackBerry 10; does the Product ID refer to:

    • The numeric, auto-assigned (by Vendor Portal) Product ID
    • The user-defined Product Name
    • The user-defined Product SKU

    I'm assuming we actually want the Product SKU since the majority of BlackBerry Payment APIs are based on the SKU, but was hoping someone could confirm.

    Also, what is the exact function of Request Store Listing? The closest BlackBerry Payment API I can identify would be GetExistingPurchases. And does that mean that this function uses the Product IDs specified in the first step to bring down local information on each of those? Does this create a WebStorage (or other local) object that gets referenced for the Has Product and similar calls?

    Ultimately, I'm hoping someone could elaborate on the specific functionality of configuring the IAP Object and how it applies to the BlackBerry 10 platform.

  • The minifying shouldn't affect FPS that much; most of the time it would be fairly negligible. Minifying has more of a role in script load times, but when packaged on-device with the app, even that isn't affected as much. I have seen audio (when multiple channels are mixed) cause latency issues, or if there are a lot of effects (movement, scaling, particles, etc.) going on.

  • Nope, functionally they should be the same. I'm setting a bit of time aside soon to re-look at the plugin and hopefully streamline some of the steps (it was the first plugin I wrote.)

  • Just as an FYI, I've had a suggestion from the community here as to why minifying isn't working. I am currently using the following signatures:

    blackberry.payment.purchase

    Whereas the recommendation is:

    blackberry['payment']['purchase']

    I'll make these changes in the next round and hopefully address the minifying issue.

  • Ah, good find! I'll make those changes.

  • For reference, updated information on integrating with WebWorks SDK 2.0 can be found here:

    github.com/blackberry/Construct2Plugins/tree/WebWorks-2.0

  • A blank screen is most often due to some Javascript error during startup. Have you tried to connect Web Inspector to the simulator and monitor the console for errors? Once you see the first white screen and connect Web Inspector, pressing ctrl+r in Web Inspector will reload the application, and is a good way of monitoring everything from the start.

    If you email me a ZIP of the HTML5 output, I can give it a try here as well.

  • There is a BlackBerry 10 simulator available for download here:

    developer.blackberry.com/html5/download

    While it is the actual OS, it is rebuilt with an x86 architecture as opposed to the ARM architecture of BlackBerry 10 devices. In addition, performance in the simulator is dependent on the overall performance of your PC. As a result, there may be differences in behaviour between the two, though usually the simulator gives a good representation of what to expect on physical devices.

    If you do not have physical hardware for testing, I am happy to test your applications and provide my detailed feedback. Simply fire me an email (eoros@blackberry.com) with a link to the BAR file and I'll give it a run on physical hardware (BlackBerry Z10/Z30).

    From time to time, we do also have promotions and contests where we offer up devices as rewards. A good way to stay up to date is to monitor our DevBlog (http://devblog.blackberry.com) or just email me from time to time and I'll let you know if anything is coming up. :-)

    Cheers!

  • This new SDK has the same OS compatibility as the previous SDK, so the reach of your applications built with the new SDK does not change, just the manner in which the packaging process takes place.

    In terms of number of users with the latest BlackBerry devices, I don't have those numbers.

    For the most part, device OS updates happen very quickly. The infographic here (from July) shows 23% on 10.0 however most of that was due to the delayed U.S. launch.

    developer.blackberry.com/blackberryworld

    End users are updating quickly once the OS becomes available from their carrier. I recommendation today is targeting 10.2 for new projects as that will cover the 10.2.1 release as well, which should cover the majority of end users.

    I'll see though if I can get more up-to-date figures than those from July.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hello all, I just wanted to pass along this guide for any developers targeting BlackBerry 10 with the new Cordova-based SDK.

    supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Construct-2-Webworks-SDK-2-0/td-p/2704887

    The approach is a little different from before. We're now exporting to "HTML5" instead of "BlackBerry 10", and there is a bit of command-line in there but it's pretty straight-forward. If you do have any questions, don't hesitate to fire me a message.

    Any feedback is also welcome, as the information in that post will eventually make its way to the official documentation and replace the current guide. Hopefully we'll be able to get some tighter integration with the IDE using this new approach as we currently have with the previous SDK.

    Regarding plugins, I still need to explore how this new approach affects everything, but it should be close to what we had before. I'll update the document with information on plugins once I've had a chance to test a little bit.

    Cheers!

  • I've managed to reproduce this and find a workaround.

    First, please ensure that you've modified your config.xml to include the necessary permissions and features.

    BBM

    <rim:permissions>

        ...

        <rim:permit>bbm_connect</rim:permit>

        ...

    </rim:permissions>

    <feature id="blackberry.bbm.platform" />

    Payment

    <feature id="blackberry.payment" />

    Second, there seems to be an issue stemming from minifying the scripts. When minified, I noticed Web Inspector was logging the following error:

    blackberry.bh.platform is undefined

    The API should be blackberry.bbm.platform, but the minification process appears to be changing the API signature to something that does not actually exist.

    When I opted to not minify the scripts, the API executed as blackberry.bbm.platform and proceeded to function.

    No changes were made to the CAPX file or plugin files.

    Can you give this a shot?

  • stroker5: Can you elaborate a little on "minimization behavior"? Would that just be a notification / trigger for when the application gets minimized?

  • 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.