Hi Marc,
Sorry for my delay - we had talked about merging the iOS/Android source a few months ago. As you say, this may be a good time to do it as I bring the Android version up to match the latest iOS version. I appear to be just about there.
The changes I make in Gambit code are restricted to the files
program.scm intf.scm
and are actually pretty minimal.
I'll take a look at Sencha's toolkit - I take it that it is HTML5-based.
I followed the work you guys did on the health hackathon - congratulations, very interesting stuff. I'm a physician in the SF Bay area and occasionally muse about some robust software support for healthcare and research:
http://apps.keithflower.org/?p=238 http://apps.keithflower.org/?p=265 http://apps.keithflower.org/?p=361
I'll make time to get this new version of Android for Gambit out the door, and structure the source so it's as painless as possible to merge. I'd be glad to get it into your git repo.
Regards,
Keith
On Mar 12, 2012, at 12:10 PM, Marc Feeley wrote:
On 2012-03-12, at 2:38 PM, Keith Flower wrote:
For my little Gambit for Android app
https://play.google.com/store/apps/details?id=org.keithflower.gambit
the GUI is Java, Gambit is compiled with the Android Native Development Kit, and JNI is the bridge.
I'm testing to release a new version that incorporates all of Marc's nice recent iOS changes.
That's nice to hear.
I've has several inquiries about using Gambit to develop iOS apps, and some people are attracted by the possibility of easily porting Gambit apps between mobile platforms. I also looked into this in the context of the Hacking Health hackathon, and even got the Sencha Touch toolkit (http://www.sencha.com/products/touch) working with Gambit REPL. It is a simple way of developing native-looking mobile applications. Rewriting the Gambit REPL user-interface with Sencha Touch would make the UI identical on iOS and Android, and allow other developers to eaily build nice UIs with it, without using native methods.
It would be nice if we could find a way to merge the source codes so that we can keep the iOS and Android versions in sync more easily. Perhaps Gambit REPL has grown too much in complexity to qualify as an iOS "example" and it should be in a separate category (app? product? software? contrib?) and then it would make sense to support more than iOS.
I'm open to the idea of giving write access to the git repository to motivated contributors. So if you are motivated please let me know.
Marc