<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-flowed"
style="font-family: -moz-fixed; font-size: 13px;" lang="x-western">I
asked my son, who does user interface development, to go through the
application and provide feedback. His basic approach was to see how
intuitive the application was. Here is a summary of his input:
<br>
<br>
1) When the application comes up for the first time, it presents a
modal dialog for the Installer. The problem with this is that this is
not in the context of a parent window. There is no way to minimize the
window, which he wanted to do because he had to momentarily do
something else on his computer.
<br>
<br>
2) The number of Bibles, Commentaries and Dictionaries is overwhelming.
He did not know what are some good choices to pick. He spent some time
looking for NIV, Da Jesus Book, New King James and a few other Bibles
that were not present. He is currently studying Romans so he looked for
a commentary on Romans, without success. It was not clear to him why he
would want a dictionary. We have Daily Devotions in with the
glossaries, which seemed out of place.
<br>
<br>
3) For Bibles there is an option to download an index, but there are
none. It always fails. It was not clear to him what an index was and
why he would want one.
<br>
<br>
4) He wanted to have a default setup that he could start with right
away and not have to go through the install.
<br>
<br>
5) The Installer window has some redraw problems. The window was active
but had kept part of an image of what had obscured it.
<br>
<br>
6) He was puzzled by the Readings. He was not sure why the three
passages were selected.
<br>
<br>
7) He is learning some Chinese so he had loaded a Chinese bible, but
the font only showed boxes. He would like the program to figure out
what he needs and do it for him.
<br>
<br>
8) He had pulled down two different KJV and was surprised by the
difference in the spacing between the two of them.
<br>
<br>
9) He wanted to view the differences side by side, but MDI didn't quite
do it for him.
<br>
<br>
10) Footnotes are too small. He suggests zooming them when the cursor
is over them.
<br>
<br>
11) He strongly recommends using full book names rather than
abbreviations.
<br>
<br>
12) The whole notion of blur is unclear. He would not have known what
the KeySidebar buttons were for except for the tooltip. He still has no
idea what it means.
<br>
<br>
13) He did not like the implications of deleting a passage of the
Bible.
<br>
<br>
14) The split tab was surprising to him and he felt that it made
navigation more difficult.
<br>
<br>
15) For lists of the books of the bible (e.g. in the commentary
dropdown) he felt that it might be more accessible to people new to the
Bible to have it in alphabetical order. (I note that there is a benefit
in having it alphabetical in that it is much easier to do keyboard
navigation)
<br>
<br>
16) He really did not like the reading jumping to the Chinese bible
(the first one he installed, thus the default). He wanted it to stay
with the current bible, which he could read.
<br>
<br>
There were a few other things that I have to ask him about.
<br>
<br>
<br>
</div>
</body>
</html>