updating moo tools to try to get rid of eval errors in chrome, and added a link to a new file which extracts reaction time from the curent json output so that it can be anlalyzed in excell, spss, or R for  https://github.com/iLanguage/AndroidBilingualAphasiaTest/issues/118
moving bat 1.0 to another folder since the data schema changed in verison 2.0
bringing in sample data.
Fixed workaround for AngularJS route problem on Android.
Merge pull request #6 from senhorzinho/master

bringin in url router fix
not using intents anymore to run services, it was causeing all apps whcih used oprime to listen and trigger eachothers services
fixign typo in langauges
adding a TouchDB listener when the activity starts
Merge branch 'master' of github.com:iLanguage/OPrime
reverting to a formated version of  https://github.com/iLanguage/OPrime/blob/51cae8797165e08876ed859a647bfc8c0549724a/AndroidOPrimeLib/src/ca/ilanguage/oprime/activity/HTML5Activity.java
fixes #7 changed the workaround we are usign for http://code.google.com/p/android/issues/detail?id=17535 to use an shouldInterceptRequest which results in the parameters and anchors to not lead to a file not found page. appears to be working. Also fixes #8 adding abstract to more classes to allow children to override key member variables
making the replicating activity to be abstract
turning off url debugging, the workaround for 17535 seems to be working
tweeking status of getApp method
Android 4.2 requires the annotation  @JavascriptInterface before each method which is intented to be accessible from the javascript in the webview, this reduces security holes but breaks most apps between 4.1 and 4.2 http://stackoverflow.com/questions/13775320/javascript-interface-not-working-with-android-4-2 http://developer.android.com/reference/android/webkit/WebView.html fixes #9
removing old proguard config, adding a new that was generated by android project for #9
for #9 another potential loss of javascript interface functions can come when methods are obfiscated using proguard source https://groups.google.com/forum/?fromgroups=#!topic/android-developers/-InoRvv37D8 http://stackoverflow.com/questions/7424510/uncaught-typeerror-when-using-a-javascriptinterface
for #9 updating project properties ot a generated properties from android sdk17
upgrading to android 4.2 and/or other change from a while ago
Reverted back to simplier structure #10

Hopefully retained all the changes that we want to keep. Namely:
*** Previous values are now being displayed when the pop-up opens.
This works now for New Inspection Date as well as all the other window.prompt
calls.

Officially calls the result.cancel() when the user hits the cancel button
of the DatePickerDialog. Without this, the Javascript side can freeze.

To determine whether a window.prompt call is going to be a DatePickerDialog,
I'm now searching just if the message contains the string "date" rather than
if it ends with it.

Made button labels into proper R.string strings.

** Next Inspection Date dialog is now a date picker on the Android #945.