Fwd: Re: Scripture Tools for Every Pastor

>
>I've been looking at all this stuff on and off. On further inspection
>the normal way of using Google Gears requires the user to have to
>visit the site (via a request to a server) first and then it would
>download all that was needed in the background then the user wouldn't
>need an internet connection... which might not be what we want. Most
>of the tools Gears provides require some form of a server for
>initialisation.
>
>However, Google Gears makes use of database technology called SQLite,
>which is serverless. Accessing a SQLite database via JavaScript could
>be a possible solution. (
>http://code.google.com/apis/gears/samples/hello_world_database.html )
>
>It all depends on how you're planning on storing the bible texts and
>the other contents. If they are large XML files they will have to be
>parsed and processed and I'm not sure if that is viable (performance
>wise) using simply client-side JavaScript. In one of my wanderings I
>did find this tiny little conceptual JavaScript SAX parser (
>http://blogs.sun.com/greimer/entry/a_sax_parser_built_on ). If we come
>up with a relational model for storing our texts we could make use of
>the full-text-search (fts2) that comes with the Google Gears SQLite (
>http://code.google.com/apis/gears/api_database.html#sqlite_fts ).
>
>I've also been looking at the source code for the SWORD project of
>that crosswire guy you mentioned. People have put in a lot of good
>work and I've only just begun thinking on how we could make use of
>their software. What exactly are they donating to us?
>
>Best wishes,
>David