Add a Help option to the Go Bible menu, with reminder of which keys do what

[GoogleCodeExporter]

New users may find it helpful to have a Help option in the Menu, so that
they can easily learn which numeric keys do what.

Key Action
1 = Previous book
4 = Next book

2 = Previous chapter
5 = Next chapter

3 = Previous verse
6 = Next page
8 = Next page

Original issue reported on code.google.com by DFH...@gmail.com on 11 Dec 2009 at 7:18

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Implementing such an enhancement would require some additional items in the
UI.properties and its  translations (localizations).

Original comment by DFH...@gmail.com on 11 Dec 2009 at 7:24

[GoogleCodeExporter]

To jump to a verse the Go to screen requires that a phone have left and right 
arrows.
Most Java phones have left and right arrows however some cheaper Nokias only 
have up
and down arrows. If your phone doesn't have left and right arrows then the * 
and #
keys can be used instead.

* = Left
# = Right

Original comment by DFH...@gmail.com on 14 Dec 2009 at 7:40

[GoogleCodeExporter]

Currently these keys on the 12-pad are not mapped in any state of the 
application:

0
9

I don't know why two keys (6,8) are both mapped to "Next page".

Original comment by DFH...@gmail.com on 14 Dec 2009 at 7:42

[GoogleCodeExporter]

I discovered something new today about Go Bible, the first time I ever noticed 
it
since March 2007 !  Isn't that amazing? 
You'd think that I would know nearly every quirk of the way the program works, 
even
though I haven't studied the source code.
I think it's an "undocumented feature" (cf. the old adage that a software bug is
such).  Here's what I found:

While you are in "Go to", and with either the chapter or verse selected - you 
can key
in up to three digits!
Providing the resulting reference is valid for the collection, this works when 
you
then click "Go to".
If the reference is outside any verse in the collection, it just reverts to 
where you
were before (still in "Go to").

One thing puzzles me about the keypad mapping during normal navigation - two 
keys do
the same thing.
Both the "8" and the "6" key scroll down by a screen full. I don't know the 
reason
for this duplication.
Is there a remark line in the source code that explains why?

Normal navigation uses the top two rows of the typical 12-key small keypad.

Row 1 = UP
Row 2 = DOWN

Column 1 = Book
Column 2 = Chapter
Column 3 = Verse (albeit key 6 = DOWN is a whole screen's worth, which makes 
good sense)

Thus duplicate key "8" is an exception to this mapping as it's in row 3. 
Do we need it?  Would anyone suffer if it were removed?

NB. While in "Go to", because some phones have no LEFT/RIGHT, Jolon assigned 
these
alternatives:
"*" = LEFT
"#" = RIGHT

Also, while in "Go to", with the "Book" selected, some numeric keys also work, 
thus:
"2" = UP (Previous book)
"8" = DOWN (Next book)
"4" = LEFT (cursor goes to verse)
"6" = RIGHT (cursor goes to chapter)
"5" = Go to
"9" = Cancel

Were these ever documented? No - I don't think so, see
http://gobible.jolon.org/about.html

Original comment by DFH...@gmail.com on 6 Jan 2010 at 5:21

[GoogleCodeExporter]

Dan replied (by email).

On my phone the '8' has no function, but the down on my joystick does. The code 
calls
this a 'game action'. On some devices it's taking the '8' and making it a
'gameAction' value of 'Down'. And indeed, in the code, the 'DOWN' and 'KEY_NUM6'
codes have the same actions. 

The device that you are using is converting the numeric keys into arrow keys 
like up,
down, left and right. These keys are handled in the code and that's why you are
seeing the behavior that you are seeing. 

So what I observed is a quirk of some Sony Ericsson phones - mine being a K750i.

Original comment by DFH...@gmail.com on 6 Jan 2010 at 9:22

[GoogleCodeExporter]

It's not really a 'quirk' of your phone, but rather a feature: it's trying to 
help 
you have the functionality of a joystick when you only have a number pad to 
work 
with.

Other phones with limited input also support this behavior. It's a 'nice' thing.

Original comment by dhinton...@gmail.com on 6 Jan 2010 at 10:25