06-20-2011 11:59 AM
Web Standards and Embracing the Web
As we’ve been pushing forward with BlackBerry® WebWorks™ and embracing the web on the BlackBerry® platform, we’ve made some important moves. First, we brought WebKit to the BlackBerry platform, which now powers our browser on both the BlackBerry® Tablet OS and the BlackBerry smartphone OS with fantastic web standards support and wicked HTML5 capabilities.
07-04-2011 06:38 PM
I've installed Ripple and tried to use it. The greatly improved load time, compared to the existing simulators, could speed up development immensely.
However, I would expect even the beta version to support something as fundamental as WebWorks Java/JS extensions. From what I can tell, it doesn't, and this obviously breaks any application more complicated than a Hello World. Even with the (known-good) extension JARs in the project's /ext folder, the JS namespaces that are supposed to be created by the extensions simply don't exist. Is this normal?
07-11-2011 07:40 AM
07-11-2011 11:16 AM
If Ripple supports JS/Java extensions, I'm assuming that there's some kind of extra compile step required to include my libraries, that isn't specified in the Ripple docs I've seen and that isn't managed by Ripple.
07-11-2011 04:20 PM
07-11-2011 04:36 PM
07-11-2011 04:40 PM
07-11-2011 05:27 PM
Ok.. there seems to be some confusion on the forums about what Ripple is, what role it will play, and what IDE's people will be able to use for WebWorks development
Let me see if I can break it down
- Smartphone : Java
- Tablet OS : ActionScript
What IDE do I use for building my WebWorks App?
You can use any IDE that you desire to build your WebWorks application. Simply make a local website for your WebWorks app using your IDE or tool of choice (mine is Notepad++) and place a config.xml file at the root of your application's website.
Then you simply point Ripple to your local website and you are good to go. Any time you make a change in your application's source code or config.xml, simply press the refresh button in Ripple. No more need to compile/deploy to a simulator as you work through building your application.
What about Packaging and Launching on a Simulator?
Ripple will be enhanced to also support the packaging and building of your application when you want to do your final testing on a simulator or live device. This will provide a similar experience to what you see in the Eclipse & Visual Studio products today where you can detect installed simulators, pick the one you want (likely the one you've been using as a profile in the Ripple Emulator) and then press run.
But what about the config.xml Editor?
We are working on different ways to enable a config.xml editor in Ripple. We understand that this is a valuable feature especially to those using the existing WebWorks Plug-ins.
If I'm not running in the Simulator how will my app look like it does on the device?
This is where we are really adding additional investment in the Ripple tooling. We will doing our absolute best to ensure that the view that see for your application is as accurate as possible compared to what you will see on a real device. Today this is pretty tricky considering Ripple is using an <iframe> in Chrome's rendering engine that doesn't have the same characteristics as a mobile device browser.
Will Ripple be remaining a Chrome Plug-in?
No, Ripple will become a standalone emulator to enable us to do some of the things that WebWorks allows that a standard browser will simply not provide capabilities for. Also, we will be providing mobile webkit emulation in the tool.
But don't worry, Ripple will continue to be able to be updated frequently and minimize large downloads or upgrades. We actually have plans to upgrade the tooling in the background to ensure you have the latest and greatest but still have the ability to work when you're not connected to the Internet.
Will Ripple continue to have cross platform support?
Yes, we will be continuing to provide cross platform support with the Ripple product. We truely believe Ripple is a fantastic tool for any mobile web developer on any mobile platform.
Hopefully that gives a little more insight into where we're going with our tooling. We can't wait to get our updates out there so that you can start using them.