I haven't looked at Gears at all... What does it offer over a simple java in-process database? Quite keen to learn about Gears though, sounds intriguing, and also keen about the Google Javascript toolkit, although never looked at it...
Chris
2009/8/6 Tyndale STEP Project <TyndaleSTEP@gmail.com>
Dear David
Looks like you are having some very interesting ideas, though I don't really follow them.
Are you suggesting we write our own Sword module? Or even start over with the OSIS data?
It seems to me that Sword have solved a lot of problems along the way,
so it would be useful if we could plug in JSword and use their APIs.
You point out that we don't need a relational database. I agree that our database needs are fairly simple.
We need a database for various functions (dates, places, non-biblical texts etc).
I suspect that the database facilities in JSword are geared to the biblical text, so we need to add a database.
On portability, we want to aim to supply something which can be used offline,
but we can assume that everyone can be online some of the time,
so we could use Gears which (as I understand it) needs a one-time online validation.
Thanks for some great ideas!
Do you think your database ideas could slot in with Chris' working model?
David IB
At 08:52 06/08/2009, you wrote:
I wrote up a few ideas I had a couple days ago and will commence
working on a proof-of-concept in due course. Jetty would be a good way
to initialise a Gears solution. The Google Plugin for Eclipse makes
use of a Jetty server for debugging GWT and GAE code.
http://groups.google.com/group/tyndalestep
--
Posted By Tyndale STEP Project to Tyndale STEP - Programming on 8/06/2009 01:49:00 AM
No comments:
Post a Comment