[jsword-devel] jsword on android
wes at werxltd.com
Tue Apr 20 10:58:19 MST 2010
I spent some time trimming down jsword and simply including the generated
.jar files in my Android project. I did manage to get my project to build
and deploy on my android device, but any attempts to create an SWMgr object
(per the examples) produces errors related to finding the book drivers
(iirc, my tests on this were from a week or so ago).
I tried changing out how the classes were loaded to no avail. So the last
spot I remember having it in
Oh, and as far as what got trimmed: I think I ended up just removing all of
the lucene function from the jsword core and converting Lucene xml objects
to the bare ocsis (?) objects to get it all to work.
Here are a couple of posts that describe the issues I ran into regarding
lucene (either the 2.x or 3.x builds):
Hope that helps some,
On Tue, Apr 20, 2010 at 12:44 PM, DM Smith <dmsmith at crosswire.org> wrote:
> Hey, it's good to hear from you again!
> Troy has started work on a JNI wrapper for SWORD C++.
> I'd love to see JSword on a mobile phone. In the past mobile Java has been
> to limiting (e.g. not property files) and it would have been a major pain to
> re-write JSword to it. Hopefully things have changed.
> Regarding annotations, JSword does not use any other than @deprecated,
> @since, ... and the standard, been there for a long time Java annotations.
> (Specifically, it does not use those from Java 1.5.) If these are a
> roadblock, they can certainly be removed.
> Regarding Lucene, it has moved to Java 1.5 with the 3.0 release. We are
> still in the 2.x series.
> I'll hold off on any Java 1.5 move until someone can provide some clarity
> on its impact on using JSword on Android.
> In Him,
> On 04/20/2010 10:44 AM, Joe Walker wrote:
> I have no idea about the annotation issues, so I'll take your word for it.
> You can subscribe to jsword-devel here:
> On 20/04/2010 15:33, Wes Widner wrote:
> Hey Joe,
> Thanks for getting back with me on this. I also recently got an Android
> phone and while there are a few good Bible apps for it already I highly
> respect and admire the Sword family of apps and I would love to see it
> supported natively.
> I also have a niche application I want to try and build (flashcards for
> Greek vocab using the Strongs dictionary).
> At any rate, I have done a lot more digging since my email to you and it
> seems that jsword as it stands contains several annotations that cause the
> dex compiler in android's sdk to choke. Lucene also contains the same sort
> of annotation issues. These annotation issues are known by the android core
> team and they are working on a work-around, but no word yet on when it will
> be released.
> In the meantime I've started working with the android native development
> kit using the early work on a project known as 'bishop<http://firstname.lastname@example.org/msg20790.html>'
> which is a JNI wrapper to the C-based sword api.
> So far it compiles and allows for some rudimentary working with the
> While there are some good performance reasons to use JNI, I would still
> love to see a pure java solution and would therefore love to help with a
> jsword fork in any way I can.
> What do I need to do to subscribe to the jsword-devel list?
> On Tue, Apr 20, 2010 at 10:19 AM, Joe Walker <joe at eireneh.com> wrote:
>> On 15/04/2010 20:47, Wes Widner wrote:
>>> Hey Joe,
>>> I've been poking through the jsword source in hopes of trimming it down
>>> somewhat in order to use it in an android application I am writing. I have
>>> two questions I'd like to see if you could help me with:
>>> 1. Have you worked with jsword in relation to the android sdk (or the
>>> dalvik jvm) any?
>> I haven't, however I have just got an android phone, so I've been itching
>> to have a go.
>> 2. Is there a way to pare down the jsword code to a minimal set required
>>> to load local sword modules (instead of attempting to auto-download them)
>>> and read/search through them (lucene has issues at the moment being run
>>> under the android sdk)?
>> There used to be 2 implementations of the search interfaces, although I
>> suspect that we've junked the pre-lucene one by now. It should be trivial to
>> create a stub implementation (so long as you don't want the ability to
>> search ;-)
>> I'm CCing jsword-devel at crosswire.org which is where this conversation
>> should probably take place.
> jsword-devel mailing listjsword-devel at crosswire.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jsword-devel