PocketSword
  1. PocketSword
  2. PS-14

search with many word (Loved one) would be equivalent to (Loved AND one)

    Details

    • Type: Improvement Improvement
    • Status: Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.0b1
    • Fix Version/s: 1.4.0b1
    • Component/s: None
    • Labels:
      None

      Description

      search with many words, for instance: (Loved one), would be equivalent to (Loved AND one)
      and if you wanted to search for either one you would need then to type (loved OR one)

      it would seem more natural that if you add more things in the search you get a narrower search result, not the other way around.
      say I remember that a verse has both "loved" and "one", i do not want to type the extra AND there.

        Activity

        Hide
        Nic Carter added a comment -

        just discovered how to do a search for a Strong's Number:

        search for
        lemma:H0430
        to search for the 430 Hebrew (note the leading H and then the extra zero at the start of the number)

        search for
        lemma:G652
        to search for the 652 Greek (note the lack of an extra zero, but need the G).

        Both need to have "lemma:" at the start.

        I'm noting it here, cause I'll do this automagically when you use the "search greek strongs" or "search hebrew strongs" options -> all you'll need to do is input the number to search for (or there may be other ways of searching, too, perhaps straight from the "info pane" that appears when you touch a <S> next to a word in the KJV with Strong's)...

        Show
        Nic Carter added a comment - just discovered how to do a search for a Strong's Number: search for lemma:H0430 to search for the 430 Hebrew (note the leading H and then the extra zero at the start of the number) search for lemma:G652 to search for the 652 Greek (note the lack of an extra zero, but need the G). Both need to have "lemma:" at the start. I'm noting it here, cause I'll do this automagically when you use the "search greek strongs" or "search hebrew strongs" options -> all you'll need to do is input the number to search for (or there may be other ways of searching, too, perhaps straight from the "info pane" that appears when you touch a <S> next to a word in the KJV with Strong's)...
        Hide
        Nic Carter added a comment -

        Another thought: Search for a Bible reference? eg: search for "Phil 4:13" and make that go to Philippians chapter 4?

        Show
        Nic Carter added a comment - Another thought: Search for a Bible reference? eg: search for "Phil 4:13" and make that go to Philippians chapter 4?
        Hide
        Christoffer Björkskog added a comment -

        I would really like to at least be able to set the default search logic. since i want to type as few words as possible, then adding another word should filter the results (i.e using the AND logic by default) to provide less hits the more you type until you have found the verse you are looking for.

        Show
        Christoffer Björkskog added a comment - I would really like to at least be able to set the default search logic. since i want to type as few words as possible, then adding another word should filter the results (i.e using the AND logic by default) to provide less hits the more you type until you have found the verse you are looking for.
        Hide
        Thomas Stuart Bockman added a comment -

        AND definitely needs to be the default search mode, not OR. Beyond that, I think Ishmael's suggestions are good.

        I was trying to find 2 Chronicles 7:14, from which I remembered included the phrase "If my people" and the word "humble", so I searched for
        if my people humble
        It took forever, to the point that I thought the app had crashed. This was, of course, because there are several thousand hits for that combination in OR mode. When it finally came up I took one look at the list and gave up on scrolling through it looking for the verse I wanted.

        On the other hand, searching for
        "If my people"
        was nearly instant, producing one result: the verse I was looking for.

        Great app, BTW. Thanks for all your hard work!

        Show
        Thomas Stuart Bockman added a comment - AND definitely needs to be the default search mode, not OR. Beyond that, I think Ishmael's suggestions are good. I was trying to find 2 Chronicles 7:14, from which I remembered included the phrase "If my people" and the word "humble", so I searched for if my people humble It took forever, to the point that I thought the app had crashed. This was, of course, because there are several thousand hits for that combination in OR mode. When it finally came up I took one look at the list and gave up on scrolling through it looking for the verse I wanted. On the other hand, searching for "If my people" was nearly instant, producing one result: the verse I was looking for. Great app, BTW. Thanks for all your hard work!
        Hide
        Nic Carter added a comment -

        ok, have had my first stab at this. Ended up having AND as the default, fuzzy isn't on by default (but it will remember your setting each time you run PocketSword, so in the world of iOS 4.x it should remember it for a while), defaults to searching the entire Bible, you can search for Strong's Numbers, and hopefully the UI is actually quite usable.
        sorry it's taken so long!

        Show
        Nic Carter added a comment - ok, have had my first stab at this. Ended up having AND as the default, fuzzy isn't on by default (but it will remember your setting each time you run PocketSword, so in the world of iOS 4.x it should remember it for a while), defaults to searching the entire Bible, you can search for Strong's Numbers, and hopefully the UI is actually quite usable. sorry it's taken so long!

          People

          • Assignee:
            Nic Carter
            Reporter:
            Christoffer Björkskog
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: