-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardize search/find to search #7398
Conversation
There is 'File search' in the Gesture manager already. There is 'Fulltext search' in the readermenu. Some help text added.
Co-authored-by: NiLuJe <ninuje@gmail.com>
koreader/plugins/calibre.koplugin/main.lua Line 112 in 0674e60
|
I would keep |
Not a simple question) Based on the definition, |
The equivalent with search would be something like this:
Most things in the menu are very much on purpose. Plenty of headers are legacy. |
Kindle uses These are the similar activities (from a user's point of view): Find, search, lookup, look up - the Occam's razor is needed. |
(No real opinion about these - I think I'd like this uniformity, but I don't know if we should really go toward radical uniformity - and impoverish vocabulary and have users learn/get used to poor english expressions :) From French, I would naturally use "search a word in a dict" - but it seems to me that "look up a word in a dict" feels like better english - and I might now use that after seeing it that often in KOReader :) |
Find/search is fairly immaterial. In my mind Find/search in text Incidentally, the Apple dictionary app uses all three.
|
We can see the following entries: 1 Text 2 File 3 OPDS catalog 4 Dictionary 5 Wikipedia 6 Calibre To summarize:
Hope this helps you, the code owners, to make the final decision on terminology unification. |
I would be happy to provide further unification based on two decisions:
|
I don't use the 2 "Find..." so I won't notice the change - I'm fine with the current "Search" ones. |
File search Very nice imho. |
Calibre is a proper name
Sorry, don't understand a conflict with opdsbrowser.lua. |
@@ -1199,7 +1199,7 @@ function DictQuickLookup:lookupInputWord(hint) | |||
end, | |||
}, | |||
{ | |||
text = _("Lookup"), | |||
text = _("Look up"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto
@@ -706,13 +706,11 @@ end | |||
|
|||
function OPDSBrowser:browseSearchable(browse_url, username, password) | |||
self.search_server_dialog = InputDialog:new{ | |||
title = _("Search OPDS catalog"), | |||
title = _("Enter author or title to search for"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit reductive, you can arguably match on tags in a Calibre catalog.
(i.e. , I prefer the previous title + hint combo, possibly with minor tweaks).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer the previous title + hint combo
Do you mean input_hint
?
There is just a hint
in the code
hint = _("Search string"), |
but I cannot find it in the InputDialog so I've removed it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly there was a typo in the field name, yeah, but I know the feature exists ;p.
I generally prefer simpler dialogs where possible, with a simple and obvious left = cancel, right = the action, without any middle. That way the menu may be more complex but the dialog is simpler. It's a trade-off. |
Thank you. Now we have a very-long-press easter egg for switching between Dict and Wiki
so the idea of domain switching is in the air. Three buttons allow simple switching and show unified accustomed dialogs. If not agreed, as a compromise it might be |
I suspect it's not (except visually), but that's an interesting point. |
Yeah, it's hard for a developer to stand at the average user's point of view. He knows what's under the hood. |
Answer myself: we can have the same |
Since this PR is about wordings only, let's postpone redesign of the search input. |
When would we see it? Only when hitting the little pencil icon at top right of any lookup result (that I can figure from you screenshot), or elsewhere too? |
As we have one combined search results window (DictQuickLookup), we can have one combined input invoked from the main menu. Calling it from the DictQuickLookup allows switching domains for a new search. |
I'm done with wordings, all reprimands fixed. Thank you very much. |
So, the little pencil icon + the menu. Is that all ? When you say "main menu", I assume you mean the 2 entries If these 2 would become a single menu item Or do you see us keeping that existing menu, and both "lookup" items launching that same dialog with both buttons ? (If yes, do you see these buttons inverted, so the one related to the menu item hit is the right most one?) |
Yes, I thought about these 3 modules and to have just one main menu entry for lookup. |
Great, thanks! |
There is
File search
in the Gesture manager already.There is
Fulltext search
in the readermenu.Some help text added.
This change is