[jsword-devel] JSword GoBible Creator

DM Smith dmsmith at crosswire.org
Mon Jul 13 06:18:30 MST 2009

On Jul 13, 2009, at 3:58 AM, Stephen Denne wrote:

> On 13 July 2009 6:05 a.m. Troy A. Griffitts wrote:
>> DM Smith wrote:
>>> On Jul 12, 2009, at 4:36 AM, Stephen Denne wrote:
>>>> I've started work on creating a GoBible creator that uses
>> jsword for
>>>> its bible source.
>>>> I've got it working as an eclipse project in a workspace that also
>>>> has the jsword & bibletime projects.
>>> Cool.
>> Hey guys, this is really exciting.
>> I would very much be interested in setting up your tool as a server
>> process to produce GoBible installers for our modules.
>> Currently our server wraps up SWORD modules from our main repository
>> into installers of various flavors (raw .zip file, InstallShield .exe
>> file for windows users, etc.).  When a user selects the
>> download link,
>> it checks to see if the chosen installer does not exists or
>> if any files
>> of the SWORD module in the repository are newer than the
>> installer file,
>> and if so, then it produces the installer automatically.
>> I would love to add GoBible installer automation.  Would
>> either of you
>> be interested in adding this service?
>>    -Troy.
> Yes. That'd be a great thing to add.
> Is the code in jsword-web being used?

Yes. It's purpose is to build the www.crosswire.org/jsword pages.

> It might be better as its own page due to the number of variations  
> which would be nice to offer as standards.

Let's prototype a page (or set of pages) and then figure out how to  
merge them into SWORD's standard download pages.

What are the variations? Are they user friendly?

> If needed, it'd be possible to individually specify modules to  
> exclude for copyright reasons.

I think Troy is suggesting that if it is from the standard download  
pages it is not an issue.

However, there may be some modules that GoBible cannot handle (e.g.  
locked modules, certain module types) or cannot handle well (e.g.  
large dictionaries).

> The code I've got isn't particularly quick at the moment (around 80  
> seconds), since I'm passing each verse through an XSLT
> transformation.

The time it takes is not much of an issue. It won't be anywhere near  
that long on the CrossWire server. We may need to put up a "Please be  
patient" sign.

Here is how the current SWORD download pages work today.
1) The CrossWire server has an expanded repository of modules.
2) When a user clicks on a download (e.g. raw, Windows or Mac) a cache  
is consulted to see if that module is already packaged.
3) If it is not in the cache, it is constructed as requested and then  
put into the cache.
4) It is delivered from the cache.

Another part of the mechanism, is that there is a means to clear the  
cache. This is used when new and updated modules are added to the  
expanded repository.

We may need a mechanism to see which modules are popular for GoBible  
and pre-build.

In Him,

> Regards,
> Stephen Denne.
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel

More information about the jsword-devel mailing list