<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Karl Kleinpaste wrote:
<blockquote cite="mid:vxky75eiyqm.fsf@mesquite.kleinpaste.org"
type="cite">
<pre wrap="">Daniel Owens <a class="moz-txt-link-rfc2396E" href="mailto:dhowens@pmbx.net"><dhowens@pmbx.net></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">I really like the advanced search dialog (I never knew it was there!),
though a "search all modules" or something like that would be nice to
save time.
</pre>
</blockquote>
<pre wrap=""><!---->
Um. Not necessarily a good idea, for those who keep most everything
installed. Even single-language lists might not help a lot.
$ ls -1 ~/.sword/mods.d|wc -l
298
$ grep -l Lang=en ~/.sword/mods.d/*|wc -l
157
I install all modules but the non-English dictionaries. I have always
tended to work for thoroughly international companies and I like being
able to show what our software can do -- that whole "be prepared in
season and out of season" thing, 2Tim 4:2, and I've impressed more than
a couple people by having Chinese, Filipino, and Farsi Bibles on hand.
I have about 2G under ~/.sword but disc space costs nothing.
</pre>
</blockquote>
I have all modules installed, too. (I don't know how you can stand all
the tabs!) To me searching them all does not make sense.<br>
<br>
Some thoughts for discussion:<br>
1) Searching should be restricted to targeted material. For example, <br>
Don't search German Bibles for English words. An English search
should be targeted to English publications.<br>
Don't search commentaries, dictionaries and other non-bibles when
someone is trying to find verses.<br>
Don't search non-dictionaries when doing word lookup.<br>
<br>
2) Do what the user asks and expects, but offer them more. For example,<br>
Given that the user has just performed a search for "Aaron AND
Moses" to get a verse list.<br>
Offer commentary entries for the same hits.<br>
Offer module entries that reference the hit verses.<br>
Offer related verses for each hit verse (there are a variety of
ways to do this.)<br>
Offer results of a synonym search.<br>
Similarly, a user has done a lookup for a specific verse. The same
kind of extras can be done.<br>
When doing a dictionary search of a word, search all relevant
dictionaries (i.e. not glossaries, devotionals and other LD; not an
inappropriate language), putting the preferred dictionary's results
first.<br>
When looking up a Strong's number in a Strong's lexicon:<br>
Offer verses having that entry (even if the user's selected set
of Bibles does not include one with Strong's numbers, but the user has
one with Strong's numbers installed)<br>
Offer related verses.<br>
Do additional work in the background, in a separate thread, so that
the requested results can be used immediately.<br>
Allow the user to cancel additional work.<br>
<br>
<br>
Basically, when we do Bible study, we go through a process of
discovery. For example, if I am doing a word study, I start by looking
up that word (in its various forms) in the Bible and I note the
different ways it is translated. I also look at the different Strong's
numbers that those words use and the different ways that those Strong's
numbers are translated. I'll also use various dictionaries to further
understand the words. I then prune and expand the list of interesting
verses. Sometimes, I get distracted and go off on a tangent of
serendipitous discovery.<br>
<br>
I think we should allow users the ability to tailor the applications to
enhance their study path. One of my grips about software in general is
that software is inflexible, requiring me to adapt to it.<br>
<br>
</body>
</html>