10-21-2011 08:25 PM
10-22-2011 11:04 AM
If you download and install the latest release of Ripple, you can build, sign and launch simulators directly from the tool without having to go to the command line.
10-22-2011 01:28 PM
11-15-2012 05:27 PM
Ripple is **bleep** for any serious development outside of just the html, and even that's pretty terrible compared to other editors out there. Just try to implement mobile jquery using it, and very shortly you are pulling out your hair and screaming. Its js capabilities are primitive. Also, for those of us that don't live in google chrome, its a major pain in the **bleep**, as few corporate intranets support it.
Then there is the integration with phonegap. I have to build and maintain phonegap plugins and trying to port them to BB now is a nightmare. No more can I simply move lib files over and rebuild in the editor that I've been using for years and talks fine to all other platforms.
No, now I have to use another editor an manually manage the project from the command line, and keep track of all my builds and versioning and everything else manually.
It adds hours to ever **bleep** update and build.
Frankly, RIM Is loosing the mobile wars, and the descision to drop support for a plugin from the most common editing platform in enterprise development out there is another example of the sorts of descisions that are making the situation worse.
Making barriers to development means that some of us simply won't continue to develop for RIM devices.
Right now, every phonegap / cordova user group on the net posting how tos or lessons uses the plugin examples, which mean that junior coders are LOST. They can't google solutions, or find proper documentation.
I really think that RIM needs to rethink this very poor decision and bring the eclipse plugin back.
Oh, and while they are at it, they need to do something about updating the dev tools to use 64bit java. Its almost 2013, and 64 bit workstations are standard.
I've been a BB user and developer for years, and I'm rapdily running out of patience with how far behind RIM is falling, how crappy the documentation is getting, and decisions like abandoning a well used development platform plugin in exchange for a CLI mess.
Instead of dumping the plugin, if you don't want to support it anymore, why not release the code to the community and let us update it?