As of version 0.4, Ruboto Core offers to share the JRuby jars between apps. ruboto-irb should utilize this.
@rscottm What is the status of this?
@rscottm I have now done a "ruboto update app" on my fork on ruboto-irb and gotten the tests to run. I have also manually tested a few of the scripts, and they all seems to run OK.
Could you review and merge if it is OK?
The next step is then to remove jruby-*.jar from libs .
* Issue #6 Port to Ruboto Core
* Did 'ruboto update app' and tweaked tests to run green
* Added tasks for callbacks in rakelib so it survives project updates.
I added the Rake tasks for callbacks in rakelib/callbacks.rake so they are automatically loaded into the Rakefile and survive project updates.
I think we should postpone moving IRB to Ruby code until after this release, which I am hoping we do next monday (2012-01-09).
Ok, I compiled your version (had to switch systems because one is already on SDK 16...build failed). Most scripts run as expected. I'm getting failure from a few of the scripts in the API demo. Those failures seem to have been there before. The difference is in how they fail. The 0.6 version fails with a backtrace in the IRB tab console. The new one fails, prints the backtrace to the logcat, and terminates the script engine (restarts it in IRB without killing the app). My guess is that this is what I changed in Script.java. I'll look into what I change. I'm sure it was just a line or two in how the exception is caught and handled.
Here's the commit I had added to better handle the exceptions in IRB"
It basically prints the bactrace to an output stream (specified at startup). I used it for exec and for callMethod. The reason I loop through the backtrace is because I kept seeing an error because there was no backtrace. Anyway, this works for IRB, but we need to figure out the best way to handle exceptions for regular ruboto apps and IRB. You put a lot of time into the exception code in Script.java, so let me know you thoughts. I'll take a pass at it when I get a chance, and fix those error in the API script.
* Changed exception handling to log the exception to the given output stream rather than throw a RuntimeException.
I added better exception logging to ruboto and my ruboto-irb fork.
Can you test it and merge if it looks OK?
@rscottm Does it look OK now? Can we merge?
Thanks for the merge!
The "p $:" can be removed.
I have removed the output in both ruboto and ruboto-irb.
* Removed the jruby-jars
* Added WriterOutputStream since it is not available form the jruby jars
* Started using EntryPointActivity
Single instance and handle orientation/screenSize changes (Issue #6 P…
…ort to Ruboto Core)
Allow output to be set separate from initialize (Issue #6 Port to Rub…
Expose appStarted and fireRubotoActivity to subclasses (Issue #6 Port…
… to Ruboto Core)
Allow startup without a script or bundle; added rubotoAttachable to b…
…e tested from script (Issue #6 Port to Ruboto Core)
Removed empty irb.rb (Issue #6 Port to Ruboto Core)
Removed ruboto scripts from demo...remains in apk at root (Issue #6 P…
Multiple changes to start up for Issue #6 (Port to Ruboto Core)
Check new rubotoAttachable because IRB is now a subclass of RubotoAct…
…ivity (Issue #6 Port to Ruboto Core)