My vote would be to push it into the API. Especially since the front-end code decides how to display it. And those front-ends who do not use this feature aren't really hurt by having it in the API. Not all front-ends in existence use the entire API as it stands anyway, right? (At least in my limited knowledge of the subject). But this is just IMHO. I'm still not familiar with all aspects of The Sword Project. I'm still trying to find where I fit in...that is if God wants me to help...
<br><br>In Christ,<br>Greg M.<br><br><div><span class="gmail_quote">On 1/18/06, <b class="gmail_sendername">Chris Little</b> <<a href="mailto:chrislit@crosswire.org">chrislit@crosswire.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>Greg Hellings wrote:<br>> I think that the plan is a good one. We are dealing with a large amount<br>> of redundant code in the case of parallel displays. However, what if<br>> two different front-ends want to display the parallel text in different
<br>> ways? BibleCS does an internlinear display, but presents that<br>> verse-by-verse. What if one person wants to do them in parallel columns<br>> (doesn't MacSword do that?) and another wants to do interlinear, but by
<br>> lines rather than verse? I think that would be the strongest argument<br>> against pushing the functionality back into the API.<br>><br>> Of course, it might be possible to push some of the parallel function
<br>> back into the API while still allowing that freedom for the front-ends<br>> to maintain freedom of how they display the parallel passages. But all<br>> the ways of doing that that I can think of amount to only a minimal
<br>> saving of code for the front-ends.<br><br>I'm only suggesting collating the data. How it is rendered is still the<br>frontend's responsibility. I would just hand it something like:<br><verse osisID="A:bk.ch.vs
">text</verse><br><verse osisID="B:bk.ch.vs">text</verse><br><verse osisID="C:bk.ch.vs">text</verse><br><br>or potentially:<br><verse osisID="bk.ch.vs">
<br><seg type="x-parallel" subType="x-A">text</seg><br><seg type="x-parallel" subType="x-B">text</seg><br><seg type="x-parallel" subType="x-C">text</seg>
<br></verse><br><br>If that is rendered as a list, in parallel, that's fine. If as a table,<br>in columns, that's fine too.<br><br>--Chris<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">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page
<br></blockquote></div><br><br clear="all"><br>-- <br><br>-------------------------------------------------------<br>Internet Community Church Ministries<br> Because of His Grace We Serve<br><a href="http://www.iccnet.org">
http://www.iccnet.org</a>