I appreciate the great feedback —

Regarding spaces ( ), hyphens (-), and underscores (_), I ran a quick test on the WebWorks SDK for Tablet OS 2.2.0.5 and BlackBerry 10 WebWorks SDK 1.0.3.8.

WebWorks SDK for Tablet OS 2.2.0.5

* spaces: packaging failed.

* hyphens: packaging succeeded.

* underscores: packaging succeeded

BlackBerry 10 WebWorks SDK 1.0.3.8

* spaces: packaging succeeded.

* hyphens: packaging succeeded.

* underscores: packaging succeeded

The test was done with a ZIP file containing an index.html, config.xml, and three TXT files (this has spaces.txt, this_has_underscores.txt, and this-has-hyphens.txt).

Seems we're in a slightly better state regarding these limitations with BlackBerry 10. Do we feel that spaces are something that should be looked at being permitted? I cringe a little at spaces myself, but if there's a consensus for 'yes', then I'll push it to our WebWorks packager teams.

Regarding WebGL + Text, do you simply mean the Enable WebGL property for a project? I'm assuming so, and will run some tests on that here. I'll also reach out to Mr. Wong (likely Alan Wong?) to see if he has any insight on the files you sent him originally.

And by all means keep the feedback coming. I'm trying to stay on top of everything but if any question's gone un-addressed, don't be afraid to follow-up. I certainly don't mean to avoid any questions, just sometimes things slip past me :-)

gonzdevour

Perhaps that's why I haven't seen the symbols/space issue, I've been building with the BlackBerry 10 SDK. I'll double check on the latest PlayBook SDK, though I can't guarantee an update would be possible as essentially all development efforts are on BlackBerry 10 nowadays. If the fix is small, perhaps it could be added in.

I'll have to take a closer look at the WebGL issue; WebGL as a whole is definitely supported on the PlayBook platform, however if there is a component that is breaking WebGL, that's something that we'd need to escalate to our development teams to have fixed. Have you by chance already submitted a bug report on this to the development teams?

For Ripple, if you're still seeing issues, please fire me an email to eoroscqh@rim.com and we can work together to get it working properly. I can set up a phone call if you like too and we can talk it out. Are you using the standalone Ripple installation? The standalone was EOL'd a while back and isn't maintained anymore. The recommended Ripple currently is the Chrome Extension version 0.9.10. There are a few things we need to double-check to get the default localhost working, which I'd be happy to work with you on. Alternatively, a local web server is what I generally recommend.

While there are two separate SDKs for PlayBook and BlackBerry 10, this is because PlayBook applications exist within an AIR container, and BlackBerry 10 applications are HTML5 that hook directly into native (C/C++). There are some API changes, and some config.xml changes, but overall the process and structure should be very similar.

I agree that screen resolutions can be a nightmare to manage, which is why we've standardized our touch-screen devices to 1280x720 and keyboard devices to 720x720 moving forward. There will still be some adaptation required, but you shouldn't need to make these adjustments with every new device launch as was the case in the past.

Any plugins created will target BlackBerry 10 first, with the potential for PlayBook. Since the PlayBook is going to be upgradable to BlackBerry 10 eventually anyways, the tradeoff between effort and importance comes into play.

ronval: I appreciate the information on that. I'll put together some tests on my end to see if we can produce this with the latest BlackBerry 10 system, and if so will raise it with our development teams for further investigation.

If there's any additional feedback from the community, please don't hesitate in sharing. As noted, I want to ensure as many obstacles as possible are removed for this community.

Regarding the canvas issues, it's something that we became aware of during the Port-A-Thon. I'd created canvas applications in the past and never come across it myself, but I saw the issue in a sample app I created afterwards; haven't identified the difference between the working/not working samples yet. I logged the issue blackberry.com/jira/browse/BBTEN-417 and have seen it fixed on newer builds. Now working to get it into the public builds ASAP.

ronval: Could you please elaborate on the sound issue? I've seen some threads regarding OGG support, and for this I can file a feature request against the actual OS. The quickest workaround in the interim though would be another file format. Or is there more to the issue / any thread you can point me at?

Joannesalfa: Luckily HTML5 is closing the gap in a lot of these places (i.e. file access, camera via getUserMedia, etc.) but I certainly see the value in getting full native API support down. Will keep you posted on this front as we progress.

Thank you for the comments and and certainly do keep the feedback coming. In the meantime, I'm going to keep familiarizing myself with the tools.

Hi Ashley,

I'll double check that it's been fixed, but I have used the '-' and '_' symbols recently in my applications and hadn't noticed any issues. If it is a problem though, I'll raise it with our WebWorks development team.

As for a device, I'll run it past a colleague and will send you an email (eoros@rim.com) once I know more. Many from our team are traveling to our conference in Thailand next week so my response might be just a little delayed, but I'll definitely let you know.

It would be great to get them in your hands and have a proper export option for BlackBerry 10 out-of-the-box.

Cheers!

I appreciate that, will take a look through.

Hello all,

I was hoping to get some community feedback here but first I just want to introduce myself. My name is Erik Oros and I'm an Application Development Consultant with the Developer Relations team at Research In Motion. My area of expertise is in the HTML5 space and my primary focus is on gaming with BlackBerry (Canvas2D, WebGL, etc.)

I've been speaking with a handful of our developers lately and Construct 2 is a common topic that comes up, but I also hear that there is a little bit missing in terms of getting Construct 2 applications built for BlackBerry 10. I also want to admit that I am very new to Construct 2.

I went through the process of creating a very basic Construct 2 application, exporting to HTML5, and then using our BlackBerry 10 tools separately to package it up into a BlackBerry 10 application, and it seemed to run well.

However, I also hear from our developers that there's the potential for creating a plugin that would help simplify this for developers. Another question is how to use WebWorks APIs (our JavaScript APIs for native API access) within a Construct 2 application. I haven't gone this far in my testing yet, but would be happy to hear your feedback on your experience.

And that's what I'm looking for right now. From my initial tests, it seems that Construct 2 to BlackBerry 10 is possible through the HTML5 export, and manually building. But what is it that you (as a Construct 2 developer) would want to see improved and made simpler in order to make that transition easier?

Feel free to overwhelm me with information :-) I can't make any promises for overnight solutions, but I want to do what I can to help.

Thanks for reading! Looking forward to your insight.