Skip to content
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

Search input box optimisation #179

Closed
SynCap opened this issue Jul 17, 2014 · 4 comments
Closed

Search input box optimisation #179

SynCap opened this issue Jul 17, 2014 · 4 comments
Labels
status/wontfix Works as designed, not a bug, out of scope, etc. type/enhancement

Comments

@SynCap
Copy link

SynCap commented Jul 17, 2014

Q1: In case if much docsets is downloaded, searching in is time eating process, even on fast machines (docs neded during hard work, whether is'nt?).
Very cool to get a request's respond immidiatly, but in dozen docsets it's time hard, becouse each typing is new request.

A1: Start seaching process on time delay in 1-3 seconds. Don't start immidiatly! Lets user took something. Don't take count of chars, just timer.

Q2: Why not to get an option in settings, that can be set 2 mode: fast search (by typing), and laizy - start search when start button (where is it?) clicked or pressed? Or may be get a button close to searchbox to switch these modes?

Q3: Why not to clear searchbox in 2 step: after ":"(semicolon), and then before?

All of this, i seems, must improve the usability on large docsets

@k3rni
Copy link

k3rni commented Sep 29, 2014

Q3 is already implemented - with for example ruby: process in the searchbox, the first Esc clears 'process' and returns focus to the searchbox. Press it again, and it clears 'ruby:'.

For the other two options, adding a toggle to search only on hitting Enter should be enough.

@dontdieych
Copy link

Arch Linux
zeal-git 0.0.0.556.09840e8-1

Input field is so blocking. I cannot type keys as usual speed. It must be typed so slowly. Or it screw order of input.

input -> ipunt

Quite serious problem to me.

@trollixx
Copy link
Member

Lags during typing are covered by #265.

Regarding Q2, honestly, I don't see a reason to disable the real time search, as long as it's not freezing UI. For me the search is almost always instant, while I have dozens of docsets installed. So, there's a specific setup, that causes such slowdown.

So, for now I am closing this issue. If you believe, that Zeal needs a "search on Enter" option, for other than performance reasons, please, comment here.

@trollixx trollixx added the status/wontfix Works as designed, not a bug, out of scope, etc. label Feb 17, 2015
@lock
Copy link

lock bot commented Sep 16, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for a related request.

@lock lock bot locked and limited conversation to collaborators Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status/wontfix Works as designed, not a bug, out of scope, etc. type/enhancement
Development

No branches or pull requests

4 participants