But then you would need 5 commentary windows open.<br><br>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.<br><br>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). <br>
<br>As to why 5, quoting from my previous email:<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">If you have a look at <a href="http://www.esvstudybible.org/search?q=Matthew+1" target="_blank">http://www.esvstudybible.org/search?q=Matthew+1</a>,
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! <br><br>In addition to this, the print <span class="nfakPe">ESV</span> <span class="nfakPe">study</span> <span class="nfakPe">bible</span>
has diagrams and maps in the notes section, which don't specifically
refer to a range of verses.<br></blockquote>
<br>I have since found a spot in Ezra where there is one more than that needed :)<br>
<br clear="all">God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>The grace of the Lord Jesus Christ be with your spirit.<br>Philippians 4:23 (ESV)<br><br>
<br>
<br><br><div class="gmail_quote">On Fri, Nov 14, 2008 at 9:45 AM, Troy A. Griffitts <span dir="ltr"><<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear all,<br>
<br>
My initial comments on this.<br>
<br>
I'm not so sure the programming interface would be much different than<br>
accessing the parts of the study Bible as 5 different modules. Our<br>
installers already allow datapaths to be grouped however we want; we<br>
just use a standard directory path like:<br>
<br>
modules/texts/ztext/esvstudy/<br>
<br>
I wonder if we had 5 modules with config something like:<br>
<br>
esvstudy.conf<br>
[ESVStudy]<br>
ModDrv=zText<br>
DataPath=modules/texts/ztext/esvstudy/<br>
Compantion=ESVStudy.ShortCommentary<br>
Compantion=ESVStudy.MediumCommentary<br>
Compantion=ESVStudy.LongCommentary<br>
<br>
[ESVStudy.ShortCommentary]<br>
ModDrv=zCom<br>
DataPath=modules/texts/ztext/esvstudy/commentary1<br>
[ESVStudy.MediumCommentary]<br>
ModDrv=zCom<br>
DataPath=modules/texts/ztext/esvstudy/commentary2<br>
[ESVStudy.LongCommentary]<br>
ModDrv=zCom<br>
DataPath=modules/texts/ztext/esvstudy/commentary3<br>
<br>
<br>
InstallMgr will already install everything is [ESVStudy] is installed<br>
because it installs DataPath and all subdirs.<br>
<br>
The only issue I see is:<br>
Frontends need to impl the Companion concept<br>
InstalMgr needs some marker that these companion modules should not be<br>
offered by themselves. (probably)<br>
<br>
Thoughts?<br>
<br>
-Troy.<br>
<div class="Ih2E3d"><br>
<br>
<br>
<br>
Ben Morgan wrote:<br>
> Even if we got permission (which would be great), there is still the<br>
> question of how to encode it. As I noted in a previous email (on<br>
> companion modules), we would currently need at least 5 modules if we<br>
> weren't duplicating data throughout. And that wouldn't be nice for the user.<br>
><br>
> It would be nice to have a module type which allows multiple entries per<br>
> key - with ranges (i.e. an entry for Matthew 1, one for Matthew 1:1-17,<br>
> one for Matthew 1:2-6, and one for Matthew 1:3. Currently, if using 1<br>
> module, the entry for Matthew 1 would need to be duplicated in lots of<br>
> places - as linked verses can't link part of the content.<br>
><br>
> These concerns apply in part to many study bibles, I think, so it is<br>
> worth thinking about.<br>
><br>
> God Bless,<br>
> Ben<br>
> -------------------------------------------------------------------------------------------<br>
> The grace of the Lord Jesus Christ be with your spirit.<br>
> Philippians 4:23 (ESV)<br>
><br>
><br>
><br>
><br>
> On Fri, Nov 14, 2008 at 1:30 AM, Karl Kleinpaste <<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a><br>
</div>> <mailto:<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>>> wrote:<br>
><br>
> Seen in <a href="http://bsreview.org" target="_blank">bsreview.org</a> <<a href="http://bsreview.org" target="_blank">http://bsreview.org</a>>:<br>
<div class="Ih2E3d">><br>
> | The electronic edition of the English Standard Version Study Bible<br>
> | will soon become available for a number of Bible software<br>
> | applications. To that effect,<br>
><br>
> || Crossway has partnered with the leading digital software providers,<br>
> || including Accordance, Biblesoft, Laridian, Olive Tree, and<br>
> || WORDsearch, to make the ESV Study Bible available with all of its<br>
> || notes, articles, and features.<br>
><br>
> Sword already has the basic ESV module. Would it be possible for us to<br>
> get this as well?<br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
</div>> <mailto:<a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>><br>
<div class="Ih2E3d">> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="Wj3C7c">><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br>