Re: [Tyndale STEP - Programming] Re: [Tyndale STEP - Programming] Re: [Tyndale ST...

Ah I see what you mean. I guess if you class bible's as JSword modules, then yes. But the debate is still open as to whether we want to put all of the STEP content into a module of itself, or if we want to put that in a separate database, for flexibility, extensibility, etc.

2009/8/18 Tyndale STEP Project <TyndaleSTEP@gmail.com>

>2 - If the ESV (parameterizable) is not installed, it is downloaded from the internet from Crosswire.
>This step I'm sure we could try and bypass by distributing the bibles from Crosswire? Is that right Troy?
>as in distribute them as part of the installation disk (or at least one or two)

That's the ESV Sword module you're talking about. JSword is simply a
way of accessing sword modules I believe - saying that, I haven't
looked at JSword for a few months.

David.

2009/8/18 Tyndale STEP Project <TyndaleSTEP@gmail.com>:

> Won't we need a database to store all the content that Tyndale are going to
> be providing? so that we can show both the passage and the the content we
> have. I'm not using Sword modules in the mock up. I'm using JSword with the
> Bible component.
>
> I think Troy suggested using a Sword Module. Not sure if that would be a
> very flexible format, but I guess we could find out. I still get the
> impression from the various things on the blog posts that I've seen that a
> database seems to be more appropriate... Either way, the DB is available if
> we want one.
>
> Chris

--
Posted By Tyndale STEP Project to Tyndale STEP - Programming on 8/18/2009 02:28:00 PM