[sword-devel] Android SWORD
bburton at mail.com
Tue Aug 31 15:50:45 MST 2010
With the discussion on which back end to use, would it make sense to write a
JSword adapter to the interface described by Troy below? This would enable
the back ends to be swapped out with minimal effort (maybe even at runtime).
On Wed, Oct 21, 2009 at 4:05 AM, Troy A. Griffitts <scribe at crosswire.org>wrote:
> A quick update on Android progress.
> o Basic Bible navigation and display are working, albeit not pretty.
> o Text-to-Speech functionality is added.
> o All methods from the engine are now completely wrapped to the same
> swordorb.idl interface we use for SWORDWeb's Java<-CORBA->C++ bridge, so
> a full-featured Android client should now be possible with the current
> engine exposure.
> Everything is still at the same location (below).
> Troy A. Griffitts wrote:
> > There is now a preliminary Android NDK / Java binding available in SVN.
> > This is very very early and should just be considered a proof of
> > There is a package available to show things working, but doesn't really
> > do much:
> > http://crosswire.org/~scribe/bishop.apk<http://crosswire.org/%7Escribe/bishop.apk>
> > the JNI libsword.so should be placed in your project/libs directory,
> > ~/workspace/bishop/libs/armeabi/libsword.so
> > and can be obtained from the above package-- believe me, you don't want
> > to try to compile it yourself as the NDK does not have STL support out
> > of the box. The Java classes can be obtained from the
> > sword/bindings/java-jni/src directory, e.g.
> > Module library must exist on your SD card under a 'sword' directory to
> > be found, e.g., unzip KJV.zip to /sdcard/sword/
> > Have fun, let me know if anyone else is interested in developing an
> > Android frontend.
> > -Troy.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel