Toolkit) and an easy way of deploying/managing/scaling our application
(GAE - Google App Engine). These technologies are combined for ease of
use in the Google Plug-in for Eclipse (Eclipse is an Integrated
Development Environment).
Google Web Toolkit:
http://code.google.com/webtoolkit/
Google App engine:
http://code.google.com/appengine/
http://googleappengine.blogspot.com/2009/04/seriously-this-time-new-lang
uage-on-app.html
The main question we have to answer at the moment is a question of
priority and focus.
{
Is STEP a web application that can have an offline mode or is STEP a
software suite connected together for easy distribution on USB stick?
}
If it is the latter then we should focus our energies on analysis of the
CrossWire Software CD and then link the relevant tools in a consistent
manner.
If it is the former then we have to resolve the issue of what happens
when we have no internet connection at all. We could use Jetty in three
ways:
1) As the server to run our application (the same application that will
be hosted on App Engine) ( http://localhost:8080/ )
2) As a bootstrap installation server that initialises our Gears
database so we can sync with the online app (
http://tyndale-step.appspot.com/ )
3) Or a hybrid of the above.
Gears:
No "online validation" is required; it just needs a server to
initialise.
David.
-----Original Message-----
From: Tyndale STEP Project [mailto:TyndaleSTEP@gmail.com]
Sent: Thursday, August 06, 2009 10:13 AM
To: Hollands, David
Subject: [Tyndale STEP - Programming] Re: [Tyndale STEP - Programming]
Re: [Tyndale ST...
Does David mean that "online validation" as in validation against a
server, ie. Jetty?
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.
No comments:
Post a Comment