[sword-devel] ESV Study Bible

[Daniel Owens]

As a user/advocate/module developer not a front-end developer...

Looking over the way the ESV Study Bible is displayed online and considering how the various front-ends handle the same module now (a diversity which is valuable), I would think that there are lots of conceivable ways the content could be delivered to users. However, my vote would be that at least one front-end display content in a fashion similar to the online interface. In addition to the Bible window (with xrefs, which are excellent--I checked most of the OT when I was working at Crossway) and verse-by-verse notes, include hyperlinks to other content, such as book introductions, maps, topical articles, etc. within the verse-by-verse notes that open in a new window (such as BPBible's tooltip or BibleTime's mag window or something similar) and can then be closed. The verse-by-verse notes should open automatically, but to keep from overwhelming the user not all content should be displayed at once by default. 

The idea of giving the user options for customization sounds very good too.

Just my thoughts... This module is an exciting possibility.

Daniel 

-----Original Message-----
From: "Greg Hellings" <greg.hellings at gmail.com>
To: "SWORD Developers' Collaboration Forum" <sword-devel at crosswire.org>
Sent: 11/14/08 6:00 AM
Subject: Re: [sword-devel] ESV Study Bible

On Thu, Nov 13, 2008 at 4:45 PM, Troy A. Griffitts <scribe at crosswire.org> wrote:
> Dear all,
>
> My initial comments on this.
>
> I'm not so sure the programming interface would be much different than
> accessing the parts of the study Bible as 5 different modules.  Our
> installers already allow datapaths to be grouped however we want; we
> just use a standard directory path like:
>
> modules/texts/ztext/esvstudy/
>
> I wonder if we had 5 modules with config something like:

The idea of that much display is pretty intense in my opinion.  I
can't really think of a clean method of navigating a screen with that
much information being pushed at me - is there no better way to encode
it?  Would a simple General Book of the commentaries with tree
structures like
GroupOfBooks
   Book
      Section
          Subsection
which would then allow the user to peruse all of the presented
information by selecting which level they want to be at?  Or the front
end could choose to concatenate all of the pertinent sections together
by walking up the key structure and pasting together several sections
of text all relative to the current passage?

>
> esvstudy.conf
> [ESVStudy]
> ModDrv=zText
> DataPath=modules/texts/ztext/esvstudy/
> Compantion=ESVStudy.ShortCommentary
> Compantion=ESVStudy.MediumCommentary
> Compantion=ESVStudy.LongCommentary
>
> [ESVStudy.ShortCommentary]
> ModDrv=zCom
> DataPath=modules/texts/ztext/esvstudy/commentary1
> [ESVStudy.MediumCommentary]
> ModDrv=zCom
> DataPath=modules/texts/ztext/esvstudy/commentary2
> [ESVStudy.LongCommentary]
> ModDrv=zCom
> DataPath=modules/texts/ztext/esvstudy/commentary3
>
>
> InstallMgr will already install everything is [ESVStudy] is installed
> because it installs DataPath and all subdirs.
>
> The only issue I see is:
> Frontends need to impl the Companion concept
> InstalMgr needs some marker that these companion modules should not be
> offered by themselves. (probably)

As a feature for the next release, adding support for some sort of
"relies on" and "recommends," the way that many Linux distributions
work, and then providing feedback to the user that "relies on" will be
automatically grabbed and asking them if they want "recommends"
modules also.  Thinking of which, what is the plan for the next
release?  Are you anticipating that these will continue to be 1.5.x?
Adding support for the alternate versification, companion modules, etc
is a pretty drastic step beyond 1.5.11.

--Greg

>
> Thoughts?
>
>        -Troy.
>
>
>
>
> Ben Morgan wrote:
>> Even if we got permission (which would be great), there is still the
>> question of how to encode it. As I noted in a previous email (on
>> companion modules), we would currently need at least 5 modules if we
>> weren't duplicating data throughout. And that wouldn't be nice for the user.
>>
>> It would be nice to have a module type which allows multiple entries per
>> key - with ranges (i.e. an entry for Matthew 1, one for Matthew 1:1-17,
>> one for Matthew 1:2-6, and one for Matthew 1:3. Currently, if using 1
>> module, the entry for Matthew 1 would need to be duplicated in lots of
>> places - as linked verses can't link part of the content.
>>
>> These concerns apply in part to many study bibles, I think, so it is
>> worth thinking about.
>>
>> God Bless,
>> Ben
>> -------------------------------------------------------------------------------------------
>> The grace of the Lord Jesus Christ be with your spirit.
>> Philippians 4:23 (ESV)
>>
>>
>>
>>
>> On Fri, Nov 14, 2008 at 1:30 AM, Karl Kleinpaste <karl at kleinpaste.org
>> <mailto:karl at kleinpaste.org>> wrote:
>>
>>     Seen in bsreview.org <http://bsreview.org>:
>>
>>     | The electronic edition of the English Standard Version Study Bible
>>     | will soon become available for a number of Bible software
>>     | applications.  To that effect,
>>
>>     || Crossway has partnered with the leading digital software providers,
>>     || including Accordance, Biblesoft, Laridian, Olive Tree, and
>>     || WORDsearch, to make the ESV Study Bible available with all of its
>>     || notes, articles, and features.
>>
>>     Sword already has the basic ESV module.  Would it be possible for us to
>>     get this as well?
>>
>>     _______________________________________________
>>     sword-devel mailing list: sword-devel at crosswire.org
>>     <mailto:sword-devel at crosswire.org>
>>     http://www.crosswire.org/mailman/listinfo/sword-devel
>>     Instructions to unsubscribe/change your settings at above page
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>

_______________________________________________
sword-devel mailing list: sword-devel at crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page