<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 13, 2009, at 3:16 AM, Stephen Denne wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 13 July 2009 4:08 a.m. DM Smith wrote:<br><blockquote type="cite">On Jul 12, 2009, at 4:36 AM, Stephen Denne wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">I've started work on creating a GoBible creator that uses <br></blockquote></blockquote><blockquote type="cite">jsword for <br></blockquote><blockquote type="cite"><blockquote type="cite">its bible source.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I've got it working as an eclipse project in a workspace that also <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">has the jsword & bibletime projects.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cool. Do you use both BibleTime and JSword for this?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">How is Eclipse for C++ development of BibleTime?<br></blockquote><br>Sorry, I made a mistake, as I meant to say BibleDesktop, not BibleTime.<br>i.e. Java<br><br>It only uses the jsword API.<br><br>However I've done a bit a c programming in the past for PalmOS, using Metrowerks CodeWarrior. Palm switched their supported IDE to<br>eclipse, and it is a much much nicer IDE than the Metrowerks CodeWarrior family.<br><br><blockquote type="cite"><blockquote type="cite">My test modules have been ESV & NETfree.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I disabled most of the GoBibleCreator "Collections" concept, <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">thinking that they could be added back in later on once I <br></blockquote></blockquote><blockquote type="cite">got things <br></blockquote><blockquote type="cite"><blockquote type="cite">working.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">By adapting a stylesheet to produce text output instead of HTML, <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">most of the format transformation work comes very easily.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">ESV has red-letters for Christ's words, which I've managed to get <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">working (for ESV) too.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We need to be a bit careful here. The ESV and NET Bibles are <br></blockquote><blockquote type="cite">copyrighted and need to have permission to be used as a GoBible <br></blockquote><blockquote type="cite">module. This might already be the case. As we (both CrossWire and <br></blockquote><blockquote type="cite">GoBible) negotiate copyright permissions we are trying to obtain <br></blockquote><blockquote type="cite">permissions for both platforms. If these are currently <br></blockquote><blockquote type="cite">available as a <br></blockquote><blockquote type="cite">GoBible modules then there shouldn't be any copyright issues.<br></blockquote><br>One reason I mentioned them was to find out what the answer was.<br>On one hand its format shifting, on the other, is GoBible now a supported CrossWire front end for viewing the sword modules?<br></div></blockquote><div><br></div>As I understand it:</div><div><br></div><div>The relationship between GoBible and CrossWire is more recent than than some of the permissions from publishers that we have obtained. Each agreement is in writing and Troy keeps the correspondence. We try to get the most liberal permissions. In the conf you might see: "Copyrighted; Freely distributable" or "Copyrighted; Free non-commercial distribution"</div><div><br></div><div>Understandably, some publishers want more control.</div><div><br></div><div>In this case, our request originally was for distribution by CrossWire as a SWORD module (i.e. downloaded from the CrossWire servers) either manually, by installer or on an official CrossWire CD. In the conf such permissions are summarized as "Copyrighted; Permission to distribute granted to CrossWire"</div><div><br></div><div>Since then we've been seeking broader permission. For those, we are asking that others are free to redistribute SWORD modules in that format. This will be noted with: "Copyrighted; Permission granted to distribute non-commercially in SWORD format" The motivation for this has been to create custom CDs for non-English speaking peoples where internet connectivity is not available or is highly monitored.</div><div><br></div><div>In the most recent past the CrossWire/GoBible relationship has gotten tighter. The details are in the sword-devel mailing list. If I recall correctly, when we work with a publisher for permission for either GoBible or for CrossWire, we are also asking for the other. That way we get explicit permission for each.</div><div><br></div><div><br><blockquote type="cite"><div>Do the conf files have an entry that can be used to determine what is allowed with them?<br></div></blockquote><div><br></div>Look for DistributionLicense. See <a href="http://www.crosswire.org/wiki/DevTools:confFiles">http://www.crosswire.org/wiki/DevTools:confFiles</a> for details.<br><div><br></div><div>I think Troy's suggestion of adding it to the current download pages indicates that if a module for GoBible is built and distributed by CrossWire, it should be OK under current agreements.</div><div><br></div><div>I'll go into this a bit more in another e-mail.</div><div><br></div><div><br></div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">What next steps do you think I should work on?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I definitely think a GUI is required to select a module, chose <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">various options, select output destination.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I have not used GoBible (my phone does not support Java :( ) so I'm <br></blockquote><blockquote type="cite">not sure. A gui would be a good thing. Better would be a <br></blockquote><blockquote type="cite">simple class <br></blockquote><blockquote type="cite">that would represent what a GUI would need to present. Then <br></blockquote><blockquote type="cite">any JSword <br></blockquote><blockquote type="cite">frontend could provide a face to the builder.<br></blockquote><br>That's how I'd structure it.<br><br>The "Collections" files which GoBibleCreator used are a mixture of specifying how to break up the text, or produce a JavaME Midlet<br>that contains only a portion of the bible (in order to work on those cellphones with next to no storage space) along with lots of<br>other options for how to produce the midlet.<br><br><blockquote type="cite">I'd be glad to add this as a project under JSword's svn and give you <br></blockquote><blockquote type="cite">ownership of it.<br></blockquote><br>That would be good.<br></div></blockquote><div><br></div>I'll add a "gobible" project to JSword's svn and have Troy grant you full privs there.</div><div><br><blockquote type="cite"><div><br><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I thought perhaps an Alkitab module might be an appropriate simple <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">distribution scheme.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Do you mean plug-in? Alkitab is based on Sun's NetBeans. I'm curious <br></blockquote><blockquote type="cite">if you could develop for it within Eclipse?<br></blockquote><br>Yes, a standard netbeans plug-in, not distributed with Alkitab, but perhaps showing up in its list of installable plug-ins.<br><br>I probably could, but I imagine that developing a netbeans plug-in within netbeans would be easier.<br><br><blockquote type="cite">BTW, I'm blind copying David Haslam on this as he might not <br></blockquote><blockquote type="cite">be on this <br></blockquote><blockquote type="cite">mailing list and I'm sure he'd be interested.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">In Him,<br></blockquote><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>DM<br></blockquote><br>Thanks,<br>Stephen Denne.<br><br><br>_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>http://www.crosswire.org/mailman/listinfo/jsword-devel<br></div></blockquote></div><br></body></html>