I was surprised to see the search option from the new selection menu running an Inline search as opposed to opening a search panel.
I would, in general, think that opening a search panel is a better option.
Thoughts?
Since I never use inline search, this option is a non-starter for me.
It makes sense to me. If I'm searching on a word in a resource, then I think most often I want to see results within that resource. This is especially true in Bibles.
When I want to search through my whole library, that's not usually prompted by a word I've just read (unless I want a definition for that word, in which case I can double-click).
It makes sense to me. If I'm searching on a word in a resource, then I think most often I want to see results within that resource.
To each his own. Personally, I would rather use "Search this Resource" from the context menu.
To me, there are two great advantages of inline search for most searches. One is that you retain formatting, markup and interlinear etc. The other is simply speed. With the search panel I have click to read in context. With an inline search (when 'paragraph' is selected for the context), I can read all my search results in context.
(I do still use the search panel, especially when I'm expecting 100s of results that I need to scan through quickly, but inline works much better for me most of the time.)
I often have my Bible text that I am studying in linked to guides. Opening the search inline moves all the links while a search this resource in a search results window does not. I have another Bible text that is set for send link here. It is a workflow in almost all my layouts that is effective. As such I prefer that an inline search not be the default.
Additionally I often have a search pane open with send searches here selected. This allows me to determine where my searches go.
I can see how either way could be unworkable in certain setups or situations. I think I'll want the Inline route most of the time, but there will definitely be times that won't work. I would suggest having a split button with a disclosure triangle that lets you choose Inline or Search Panel, and make the selection "sticky". This would allow everyone "set it and forget it" either way, as well as provide the flexibility to choose differently based on the occasion.
I typically have several study layouts that include a search panel set to Send all Searches Here. I would prefer to have the selection search recognize that search setting and send it to that panel.
Just as a point of clarification, the search button:
To each his own.
And there's the problem. I actually prefer a search panel, myself; but we are trying to pick defaults that we think most the people would benefit from. Keep in mind the goal of this feature is at least as much "discoverability of tools for new users" as it is "convenience for all users." Design goals are to keep it simple and smart; configurable was a secondary consideration for this iteration.
Having said that, it might not be a bad idea to have the Search button respect "Send searches here" in all cases, which would provide a workaround for users who don't prefer to use Inline Search.
This seems a sensible idea, that doesn't introduce any additional UI complexities.
Just as a point of clarification, the search button: always searches inline on short selections (1-5 words).
we are trying to pick defaults that we think most the people would benefit from
Put me down who NEVER uses the inline form because of the limitations in seeing sufficient/relevant context.
An excellent idea
Just as a point of clarification, the search button: always searches inline on short selections (1-5 words). on long selections in non-bibles, opens a search panel for "All Resources." on long selections in Bibles, is omitted on the Selection Menu to make room for other actions.
Thanks, Adam, for that insight - appreciated
That sounds like a good plan.
I don't understand this with the range of "context" options available
For Bibles with pericope titles it's not a big problem ... but in most cases I need to be able to see chapter titles, section titles, ... in order to place the location in the structure of the resource. I am someone who works from the top down to the details ... so I have to have the "top" visible. People who work from the details up likely have no problem.
Having said that, it might not be a bad idea to have the Search button respect "Send searches here" in all cases,
I expected it to respect "Send searches here", but wasn't upset when it used Inline Search. So if you make that change, the destination is easily configurable.
This is good to know and I would suggest having thorough documentation available before this goes golden.
Excellent approach. I love it
the search button: always searches inline on short selections (1-5 words). on long selections in non-bibles, opens a search panel for "All Resources." on long selections in Bibles, is omitted on the Selection Menu to make room for other actions. ... Having said that, it might not be a bad idea to have the Search button respect "Send searches here" in all cases, which would provide a workaround for users who don't prefer to use Inline Search.
the search button:
...
Thanks for the feedback, everyone. Some new thoughts incoming.
Counter-proposal: Search button always opens a search panel.
Reasons:
The only thing I would counter this with is "discoverability" of inline search. I expect this feature to be relatively under-used... That said, I appreciate the consistency consideration.
Like it [Y]
+1 [Y] Like, especially with Send search here option (so can replace search in an existing tab instead of opening a new tab).
Keep Smiling [:)]
