<br>
It would be neat to have a module that used BibleGateway (or similar) as a back-end.<br>
I'm sure there are all sorts of *very* complex copyright issues with doing this though!<br>
<br>
Joe.<br><br><div><span class="gmail_quote">On 6/18/05, <b class="gmail_sendername">DM Smith</b> <<a href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</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;">
Now that we are preparing for a 1.0 release, I think that we can look<br>ahead to the next release.<br>There are a lot of ideas in Jira "bugs" Probably too much for a 1.1 release.<br><br>So what do we work on next?
<br><br>I would like to see (not in any particular order):<br>Parallel texts. (Perhaps with a comparison mode where one is shown as<br>the revision of another.)<br>User preferences/state restoration/per module preferences.
<br>Support for the remaining module types.<br>Personal commentary/book marks/robust history.<br>True Daily Devotion support, migrating our "Readings" to it.<br>Full integration of Commentaries and Dictionaries.
<br><br>Internally, I think we need to replace Java's HTML rendering with an<br>embedded browser.<br>(More on this in a separate note.)<br><br>I think that Sword is going to tackle alternate versification, so I<br>think that we may want to include this.
<br>And along with that, I think it would be good to add support for OSIS<br>bibles.<br>By this I mean, that JSword would work against a raw OSIS document that<br>is not a Sword module.<br>_______________________________________________
<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel
</a><br></blockquote></div><br>