<br>My recollection is that I needed to do that for the IE/FF version anyway - just because the demands of web display are different from desktop display.<br><br>Joe.<br><br><div class="gmail_quote">On Sat, Apr 19, 2008 at 4:09 PM, DM Smith <<a href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="">Joe,<div><br><div><div><div>I think it'll help. It gives me a starting point.</div>
<div><br></div>I tried javeline's xpath/xslt and it does not work with something in the xslt derived from BibleDesktop's simple.xsl. But there is no diagnostics.</div><div><br></div><div>From a comment on Google's ajaxslt they indicate it is incomplete. But, I'm going to give that a shot. At least it has alerts for unsupported constructs.</div>
<div><br></div><div>Either way, I'll need to simplify the xslt to get it to work on Safari.</div><div><br></div><div>Thanks,</div><div><span style="white-space: pre;"> </span>DM<font color="#888888"><br></font></div><div>
<div></div><div class="Wj3C7c"><div><br></div><div>On Apr 19, 2008, at 3:25 AM, Joe Walker wrote:</div><br><blockquote type="cite"><br><a href="http://ajaxian.com/archives/xpathxslt-support-in-safari" target="_blank">http://ajaxian.com/archives/xpathxslt-support-in-safari</a><br>
Might help.</blockquote></div></div></div><div><div></div><div class="Wj3C7c"><div><blockquote type="cite"><br><br>Joe.<br><br><div class="gmail_quote">On Sat, Apr 19, 2008 at 4:13 AM, DM Smith <<a href="mailto:dmsmith555@yahoo.com" target="_blank">dmsmith555@yahoo.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I found out that this does not work on the Mac. I've narrowed down the<br> problem to Safari not having an XSLT processor. I'm looking into<br>
alternatives.<br> <font color="#888888"><br> -- DM<br> </font><div><div></div><div><br> On Apr 18, 2008, at 1:42 PM, DM Smith wrote:<br> <br> > I have worked up an example, demo, starting point of how to use JSword<br>
> in a servlet using DWR - Direct Web Remoting.<br> ><br> > Here is a tutorial on how to do it:<br> > <a href="http://www.crosswire.org/jsword/tutorial.html" target="_blank">http://www.crosswire.org/jsword/tutorial.html</a><br>
><br> > Here is a somewhat working version of it.<br> > (I don't have any of these indexed, so search does not work.)<br> > <a href="http://www.crosswire.org:8080/jsword/iBD.html" target="_blank">http://www.crosswire.org:8080/jsword/iBD.html</a><br>
><br> > This doesn't follow the tutorial exactly. I had to tweak the dwr<br> > javascript inclusions.<br> ><br> > There are some shortcomings in this example:<br> > 1) Because all the links are handled via java script, it never leaves<br>
> the page. Hitting the brower's back button does not take you to the<br> > prior verse. It would be really nice to have history.<br> > 2) There are no options, e.g. show/hide notes/Strong's/xrefs/verse<br>
> numbers/verse per line, .... There should be.<br> > 3) This does no caching at all.<br> > a) It should cache the XSLT processor. During development, you<br> > don't<br> > want caching.<br> > b) In doing options, we should cache the dom for the current view.<br>
> No sense in getting it again.<br> > c) It may make sense to cache the dom for some items in history.<br> > 4) It does not make good use of JavaScript. These are pretty trivial.<br> > a) Rather than notes in a sidebar, it would be good to have a hover<br>
> enabled popup of the note body.<br> > b) Implement Strong's and Robinson's morphology lookup into a<br> > popup.<br> > Currently, it does these are not handled at all.<br> > c) Perhaps highlight all words on the page having the same Strong's<br>
> number.<br> > d) The javascript constrains the return to 100 verses to prevent<br> > overloading the server with a request like: Gen-Rev. It would be<br> > good to<br> > be able to get the next "n" verses.<br>
> e) Allow dictionary lookup of a displayed word.<br> > f) The search input box and button should be disabled when a book<br> > is<br> > not indexed.<br> > 5) It makes no use of Cookies:<br> > a) It would be good to have it remember current state<br>
> - Current Bible.<br> > - Current passage.<br> > - Last lookup<br> > - History<br> > - Settings, e.g. show hide<br> > b) Allow the user to prune the Bible list to only those that they<br>
> care about.<br> > 6) Handle right-to-left languages.<br> > 7) Allow for the specification of where to look for modules and an<br> > alternate location ~/.jsword. (This is a shortcoming in JSword that<br> > should be fixed.)<br>
> Right now it looks at every conceivable location for SWORD modules<br> > and it will let you specify additional locations. There is no way to<br> > prune the list or to specify that it should only look in a given<br>
> location.<br> > Right now it will only look at ~/.jsword, which must be writable.<br> > In<br> > a Tomcat installation, this might not be a desirable location. Today<br> > this can be changed by changing the jsword.home property. There should<br>
> be an easier way to override this.<br> > 8) It is not internationalized. It'd be cool to grab the text from<br> > BibleDesktop.<br> > 9) The UI is merely functional. That is, it is ugly. Make it look much<br>
> nicer.<br> > ......<br> ><br> > I'd also like to add a menu and toolbar. Perhaps, with the toolbar<br> > hiding the locate and search text inputs behind icons.<br> ><br> > I'm sure you can add to this list. Feedback welcomed.<br>
><br> > In Him,<br> > DM<br> ><br> ><br> ><br> ><br> ><br> ><br> ><br> > _______________________________________________<br> > jsword-devel mailing list<br> > <a href="mailto:jsword-devel@crosswire.org" target="_blank">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> <br> <br> <br> _______________________________________________<br> jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org" target="_blank">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>
</div></div></blockquote></div><br> _______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org" target="_blank">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></div></div></div></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" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
<br></blockquote></div><br>