<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I don't see it that way. I like the transformation to OSIS as an intermediate form and then to HTML.<div><br></div><div>The only problems I see are the creation of the DOM as objects. If SAX or StAX could be the interface, then we'd be able to have a lighter process.<div><br></div><div>DM</div><div><br><div><div>On Sep 4, 2012, at 5:15 AM, Joe Walker <<a href="mailto:joe@eireneh.com">joe@eireneh.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Sigh - I think the document model in JSword is one of the things I most consistently got wrong. If I remember correctly we started with a standard API, then JAXB then JDOM.</div><div>At the time XML seemed like The Future, however there seems to be more and more that argues against that vision for JSword:</div><div>- Android display works around the JSword API to avoid XML</div><div>- Swing uses the horribly broken JEditorPane (?) and its display is probably the worse for it</div><div>- Even using XML for JSword on the web, which should be a sweet spot, has (had?) problems like getting reliable XSLT in browsers.</div><div><br></div><div>We're going to need some sort of document object model, and given the existence of OSIS, some sort of ability to serialise it to XML makes some sense, but perhaps we should consider an object model that is somewhat closer to the storage model than the display model.</div><div><br></div><div>Joe.</div><br><div><div>On 3 Sep 2012, at 22:20, DM Smith <<a href="mailto:dmsmith@crosswire.org">dmsmith@crosswire.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Looks like from your notes that there is more opportunity than just replacing JDOM, but rather not building a DOM at all. Maybe you and Douglas can collaborate?<div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div><br><div><div>On Sep 3, 2012, at 11:25 AM, Martin Denham <<a href="mailto:mjdenham@gmail.com">mjdenham@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">It would be good to remove JDOM. When working on the first versions of And Bible I had to bypass the JDOM DOM creation to improve performance on low powered Android devices, but my simple workaround only worked for simple, well structured OSIS bibles.<div>
<br></div><div>I made a <a href="http://code.google.com/p/and-bible/wiki/AmendmentsToJSwordForAndroid">few rough notes</a> on it at the time.</div><div><br></div><div>I don't think Android includes a StAX library, but it does include a similar efficient XML Pull library and it would probably be possible to include a StAX library with And Bible. I could do some investigation and experiments if this approach was seriously under consideration.</div>
<div><br></div><div>Martin</div><br><div class="gmail_quote">On 3 September 2012 15:35, Douglas Campos <span dir="ltr"><<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Howdy!<br>
<br>
I was talking with DM wrt removing jdom and using org.w3c.* APIs instead (more portable, less deps), and he asked me to post it here :)<br>
<br>
Any objections? (I'm assuming I'll fix BD too)<br>
<br>
Blessings,<br>
-- qmx<br>
<br>
<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" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</blockquote></div><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></div></div>_______________________________________________<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></div>_______________________________________________<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></blockquote></div><br></div></div></body></html>