RE: [Tyndale STEP - Programming] GWT version of JSword

Well at the moment I'm not planning on using JSword - maybe just using
it as a reference (to see how they've done it) for parsing OSIS XML and
to see how they have chosen to model the data object-orientedly. We may
be able to re-use some of their code.

At the moment, I'm envisioning storing chunks/fragments of OSIS XML in
an indexed database (GAE Datastore/SQLite) then sending these chunks of
scripture/book to the GWT client which then parses them (GWT Java ->
JavaScript) for display.

I might use JSword or the more powerful C++ SWORD to produce stuff for
the writes to the database. "Shift processing from read to writes".
That's the data migration step which will be significant in size and
thought.

If any new data is produced by Tyndale it should be in OSIS XML so we
can give something back to the SWORD community.

In this research phase I see no need for total consensus before
producing any prototypes. So Chris, keep digging around... Jetty is what
is used by the Google Plugin for Eclipse, which enables us to edit our
Java and see its effect in a browser immediately - so that's a good
thing to look into.

The first iteration (outlined on the google group) is just a speculative
dive into a promising technology. It may not work or be the best
solution.

David.

-----Original Message-----
From: Tyndale STEP Project [mailto:TyndaleSTEP@gmail.com]
Sent: Tuesday, August 18, 2009 1:57 PM
To: Hollands, David
Subject: [Tyndale STEP - Programming] GWT version of JSword

Yes, Chris, I agree that this would seem to be the way to go,
(ie Jetty, GWT, JSword, Java database)
but I'm uneasy till I see something working.

In particular I don't yet 'get it' about how JavaScript can send a
request to a Java API in JSword,
but I'm hoping that I missed something and David will show us how to do
it.

David IB