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?
Yes. I 've sent a zip not only to the development teams,
but also to an Application Development Consultant Mr.Wong in RIM HK.
However, maybe it's hard to discover what happened by the zip,
I think the C2 exported files are not simple enough to debug.
If you are trying C2, just put a text object and turn WebGL on/off to see what happened in .bar.
I am not sure if this issue fixed. It's about a month ago and I found Playbook OS has updated.
For Ripple, if you're still seeing issues, please fire me an email to email@example.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.
Thanks, you are kind.
I am using command line to ensure all things worked and pop out the real reason if error,
It's enough for me right now, but I think a much more friendly Ripple is necessary.
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.
Got it. If there're plugins and exporter to deal config and API integration,
It will be a great inducement for C2ers to try RIM platform.
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.
While iPhone5 and Win8 makes their screen 16:9,
I think 1280x720 is a nice idea. It helps the developers easier to make cross-platform plans.
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.
Playbook is an old guy........but I can understand that RIM has no superiority to join the Arm Race.
As a game constructor, what we need is a platform with 60 fps for all the game genre.
Hope BB10's software acceleration can make it with HTML5.