<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Don,<br>
The pulling up of the entire chapter when clicking on a verse in the
side bar is a bug that has been fixed. Now what you click on is what
you see. You can multiselect to show several verse ranges at the same
time.<br>
You can get the nightly build or wait for 0.9.8 to be released (which
will be very soon)<br>
<br>
I hope to figure out how to do highlighting in the passage display
area. I have done it in several different programming languages and
even in Java, but not w/ a HTML document. I am thinking that search
terms should be highlighted as well as the verse at the center of a
"blur".<br>
<br>
The notion of context being part of the translation is an interesting
problem. The greatest problem is that the translations are inconsistent
in their markup, even when they use the same standard. Finding context
markers is difficult. Finding inconsistent ones is not likely.<br>
<br>
Writing help would be greatly appreciated!<br>
<br>
Don Parris wrote:<br>
<blockquote cite="mid20040826002753.8CD4C4151E@mail01.powweb.com"
type="cite">
<pre wrap="">---------- Original Message -------------
Subject: Re: [jsword-devel] Usability testing ...
Date: Wed, 25 Aug 2004 23:48:38 +0100
From: Joe Walker <a class="moz-txt-link-rfc2396E" href="mailto:joseph.walker@gmail.com"><joseph.walker@gmail.com></a>
To: Java SWORD Developers Mailing List <a class="moz-txt-link-rfc2396E" href="mailto:jsword-devel@crosswire.org"><jsword-devel@crosswire.org></a>
Don Parris wrote:
..
</pre>
<blockquote type="cite">
<pre wrap="">I might add that it would be useful for users to see in the Books dialogue
just how big a module is before they decide to download it. Not a big deal
if you have broadband, but a lot of folks - like me - still use dial-up.
Imagine my surprise when I discover that module I want is 8MB, rather than
the more typical 1-4MB.
</pre>
</blockquote>
<pre wrap=""><!---->
I'll add it to bugs.txt
</pre>
<blockquote type="cite">
<pre wrap="">I agree with Mark on the sidebar. As a minister, I think it's really nice -
I can select the verses that I think are most relevant to my search (I may
already have some idea of what I'm looking for). The problem I have is that
clicking on a verse does not produce what I would have expected.
For example, searching on the word neighbor brought up Acts 7:27. Clicking
on Acts 7:27 pulled up the whole of Chapter 7. I would have expected to see
v. 27 at the top of the result pane. It would even be useful to see it in
its context in the result pane - i.e., within the passage it belongs to.
</pre>
</blockquote>
<pre wrap=""><!---->
I assume you mean within the sidebar? Could be tricky but it might fit
in with the updated reference panel that I've been pondering for a
while.
-----
NOTE: I'm using the RSV for my example. Also, consider - for simplicity's sake - context and passage to be the same thing. Every verse exists within a passage, thereby giving it "context".
The verse list shows up in the side bar (Acts 7:27 being among those listed). When I click the verse in the verse list, it pulls up the whole of Ch. 7 in the result pane. Ideally, v. 27 would show up at the top of the result pane (not within the side bar, but where the biblical text is displayed), or at least within its context (passage).
In other words, I like the side bar like it is - and with grippies, I can turn it off temporarily if I need to. But when I click on a verse listed in the side bar, it needs to "show up" at or near the top of the text (what I'm calling the 'result') pane. You could add highlighting for glitz, but it's not necessary.
Ideally, when I click on Acts 7:27 in the verse side bar, it would produce (for the RSV, at least) Acts 7:17-29 - which is the RSV context within which 7:27 occurs.
That will present a challenge for you as developers, as different versions will show a verse in different contexts, much depending on theological perspective and whims. If you don't strive to show the verse in its proper cntext, though, you'll need alternatively to either (a) highlight it for ease of spotting it, or (b) have the verse show up at the top of the text/result pane.
You could decide on a "standard context", based on a particular translation, and apply it to all translations for the purpose of making it easier to code. I'm guessing that OSIS has addressed the "passage" issue, but perhaps it hasn't.
---------
Did you know you can select several verses to see them all at the same
time by pressing ctrl while clicking?
----------
I was unaware of that. I'm not sure I have the time, but perhaps I could work with you guys to produce a simple help file (to do such and such ,step1, step2, etc.)? Once it's begun, one will only need to keep it up to date.
----------
Thanks for all the comments,
----------
Just hope it's actually helpful.
Joe.
_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
</body>
</html>