Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development

Reply
Developer
Posts: 27
Registered: ‎05-12-2011
My Device: Playbook 2.0, Dev Alpha A
My Carrier: Waiting for BB 10

Installing standalone or extension Ripple Emulator

I'm re-submitting my 2nd playbook app because of  *new*  config.xml requirements.

 

Could some kind person explain how to download the standalone Ripple Emulator?

All I can find is the chrome extension emulator which I downloaded anyway.

 

The instructions mention a ripple_ui.crx file.

Where exactly is this file in the  Ripple 0.9.4.1 installation directory/subdirectories?

Windows-7-Search can't find it.

 

Yes, I uninstalled the previous emulator which sadly *stopped running*.

Contributor
Posts: 41
Registered: ‎04-27-2010
My Device: Z10
My Carrier: VIettel

Re: Installing standalone or extension Ripple Emulator

[ Edited ]

It's here:

 

Windows 7: C:\Program Files(x86)\Research In Motion\Ripple [version]

 

And I suggest using Chrome Extension since it allows you quickly switching between devices/platforms or just disable it.

 

Cheers.


---
More applications/games here: http://appworld.blackberry.com/webstore/vendor/14299/
louis.keeper@gmail.com
haitt@viethop.net
http://blackberryvietnam.net
http://viethop.com
Developer
Posts: 27
Registered: ‎05-12-2011
My Device: Playbook 2.0, Dev Alpha A
My Carrier: Waiting for BB 10

Re: Installing standalone or extension Ripple Emulator

Thank you, but *where* does it come from?
Never mind, I'll use the command line as I don't really need an emulator for basic HTML.
Retired
Posts: 856
Registered: ‎07-15-2008
My Device: Passport
My Carrier: Bell

Re: Installing standalone or extension Ripple Emulator

The Chrome extension version is the way that Ripple will be working in the future, so I recommend using it over the older Standalone version.

 

It's definitely not the only way to build though.

Tim Windsor
Open Source Technical Lead