Ideas for Bible plugin (2.1.6 version)

Bug #1491382 reported by Azaziah
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenLP
New
Wishlist
Unassigned

Bug Description

See the link for better text formatting:
https://docs.google.com/document/d/1S8gHmeo90_pdwaPq7MDhX7Qb2lKO6Ahv3GPyKIZMUUU/edit?usp=sharing

Ideas for the Quick search

The quick search might be really slow if bad search terms are used.
For an example search “And” will take serveral minutes to complete and program becomes unresponsive.

Maybe we could:

Notify user if more than x amount of verses are found and ask if they want to keep searching.
Add search range buttons for OT / NT so you can untick OT if you want to search only NT or vice versa. Atleast one of the two boxes would have to be chosen, unticking OT while NT is unticked would tick NT automatically.
Set a minimum length of 2 characters to prevent accidental searches.
Prompt user if the text search includes only one short word.

Combined scripture and text search

Add combined “search scipture reference or text”
which would first search for scripture referense and if none are found move to text search.
I feel this would be faster than switching between the two.
This would also cause less confusion in case the user is not
 aware that he should change the search mod.

Ignore the missing dots in scripture reference

Atleast in finnish . is used after numbers on booknames,
making the search work even with the missing dot would be great.
Less typos and faster search.

Advanced tab
(Maybe this could be renamed to something like “Pick the passage”)

Book selection

This opens a list of 66 books (and possible apogryphics).
I feel like this might not be the fastest way to pick up the wanted book.
This becomes increasingly problematic if you can’t remember the order of the books.

Ideas:
Split Books to:
Old testament: - Pick from the list -
New testament: - Pick from the list -

Expand the box on click and add 2nd collumn for book names.
Or make a popup which contains buttons for all the booknames.

Grouping advanced search results by default

 If the user chooses the range by himself, he most likely wants to use all of the found verses.
This behaviour could be disabled from settings if so desired or group expanded.

Changing the default verse search range:

When the starting chapter is changed to higher than the ending chapter, the ending chapter automatically changes to the same chapter.
Maybe we could make it so that it automatically changes the last verse for the search to the last verse in the chapter. I think users search the whole chapter more frequently than just 1:1

For both:

 Link last used Bibles together for quick and advanced.

I feel like it would be easier to use if they would follow each other.
So for an example I couldn’t have KJV in quick search and Amplified version in
advanced tab as the selected Bible.

Azaziah (suutari-olli)
description: updated
Revision history for this message
Tim Bentley (trb143) wrote :

Interesting idea but to get the information you need the search needs to be completed.
The search is inside the database and does not leave until complete with no way to communicate to the user.

Some of the restrictions (NT v OT) would help, but then again it would require a re-write of the database structure.

Needs careful though as it could require a major rewrite of the plugin.

Tim Bentley (trb143)
Changed in openlp:
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.