scruffian / javascripture Goto Github PK

In version 4 actually the Strict Search checkbox is not working at all (not disabled, but not accepting checkmark ...?).

Maybe there should be a rollover or subtext to explain in what way it's stricter?

If it's meant to switch between searching for sub-strings and whole words it would also be better to place it into the advanced search options, because you'd want to change that on a per-search basis (unlike the search speed)

If you click on the "Go to" field in the top left corner, anywhere except on the book symbol, the text jumps to the previous chapter. I would expect this to be either a part of the button that opens the "Go to" dialog or a non-clickable heading for the column underneath.

In Firefox the behaviour also creates an inconsistency, as it jumps back to a few pixels above the heading of the previous chapter (other chapter links usually jump to verse 1), which causes the chapter selection input field at the top to display the chapter before the one now visible in the main reading area.

The whole button should probably stay in place rather than scrolling out of sight when the user scrolls the chapter navigation.

Having said all that, maybe the whole "Go to" link and dialog are redundant! Since you have two other (and probably faster) mechanisms to pick a chapter, perhaps the space at the top left would be better used to add an NT/OT toggle that quickly scrolls the appropriate chapters of the left hand chapter navigation into view.

You probably want to maximize the use of the screen estate for content, but I think a tad more padding would make the overall impression a lot more pleasing

Once you've checked the Reading Mode option, there is no obvious way to get out of it again (Chrome, Win7)

(Win7)

alignment, spacing, font sizes ...

Search returns any occurance of the search string, which in many cases is useful, but turning on Strict Search in the Settings doesn't seem to change it:

Example: Search for "ice" returns "voice", "artificer" etc.

(I also noticed that a leading or trailing space gets ignored, but using both returns no results at all, i.e. " ice" or "ice " = "ice", but " ice " not found.)

I can use the tool off-line in Chrome, but not in Firefox.

When I uncheck "Show original" in the Settings, only the Hebrew text disappears. Greek is shown in line with the English. And in both cases the verse numbering remains in the center, instead of appearing to the left of the text.

Shortcut tips in Help and under Settings should be consolidated under Help.

Not working in either Chrome or Firefox (Win7)

• advancing through chapters with left/right curser keys
• next/prev reference with n/p

Not working in Firefox (Win7)

• next/prev reference with -/=

Help:

"To find out about a work ..." / should be "word"

Settings:

"Slow devices crash if you try to search to ..." / should be "too"

The message you get when going to javascripture.org "Loading JavaScripture. Once it's loaded it will be installed into your browser, so it will also work offline. Even if you close the tab." sounds almost like a threat! Maybe this should not be right in the domain root - rather have an information page first that allows newcomers to find out about the tool and then choose if they want to try it. This should include some information about what it is (i.e. a Bible study tool, not the definitive source of JavaScript info) and what the installation entails (How much space does it take? How do I get rid of it, if I don't want it anymore?)

(at some point I actually had two versions installed: typing the URL would open the latest (with the new large-print feature), but clicking on a Firefox bookmark to a specific passage loaded the older version. I can't reproduce that now, but it made me wonder how exactly updates are taken care of)

On my BlackBerry PlayBook the site manages to crash not only the Browser (as on the BlackBerry Z10) but all running applications - which is a spectacular feat I haven't seen before! :-) Not that you'd necessarily need to cater to a niche platform like the PlayBook, but you want people to at least be able to visit your site, even if it's only to find out that they need a better device)

It would be nice if the word info could include an English transliteration
(however inadequat they may be (?), for those who can't read Hebrew they still provide a useful mental handle - and it's certainly easier to discuss 'ruach' and 'neshama' than having to constantly refer to 5397 vs 7307 or the blue vs the pink spirit ;-) ... )