[sword-devel] ESV Study Bible

[Ben Morgan]

But then you would need 5 commentary windows open.

I don't want the user to be able to see five or six modules for a single
logical module - that would be up to the frontend, though, I suppose.

Perhaps instead of just using Companion, we need a config option to specify
logical grouping of modules as well (i.e. these 6 modules are one module).

As to why 5, quoting from my previous email:

> If you have a look at http://www.esvstudybible.org/search?q=Matthew+1, you
> can see three different "streams" of commentary. The notes that have a
> completely grey background are large sections, the notes with the heading
> with a grey background are for smaller sections, while there are per-verse
> (or a range of verses) notes as well. All of these can overlap. There is
> also one note from the per-verse stream here (Matthew 1:2-6a) which overlaps
> with another in the per-verse stream (Matthew 1:3). So to encode this well,
> what you really need are at least 4 commentary modules here!
>
> In addition to this, the print ESV study bible has diagrams and maps in
> the notes section, which don't specifically refer to a range of verses.
>

I have since found a spot in Ezra where there is one more than that needed
:)

God Bless,
Ben
-------------------------------------------------------------------------------------------
The grace of the Lord Jesus Christ be with your spirit.
Philippians 4:23 (ESV)




On Fri, Nov 14, 2008 at 9:45 AM, 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:
>
> 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)
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.crosswire.org/pipermail/sword-devel/attachments/20081114/e867803b/attachment.html