• Type ahead suggestions

    By Steve Smillie 1 decade ago

    I found that the Typeahead worked better with 2 adjustments (note my data set is almost 50,000 documents):

    1. Set Autocomplete to 'off' for the typeahead field. Since autocomplete (like in Chome) give the choices but selecting them doesn't trigger the keyup event.

    2. I found using the startKey, instead of the key, on the view datasource seemed to work better for the scope variable that contains the type ahead value.

    I am still having issues where if you type fast the typeahead it doesn't use the whole typed text. Example type 'smith' fast it seem to use 's' or 'sm'.   Type slow and the typeahead seem to work well.  I assume this isn't specific to your design but a more general issue.

    • Great ideas!

      By mark t hughes 1 decade ago

      I will incorporate both of those into the next release.  I expect the delay has to do with waiting for the ajax return of the results and them getting out of sort if you type to fast.  I think that is why i prefer searching.

    • Justed tested the type ahead on the test db typing as fast as i could

      By mark t hughes 1 decade ago

      I set it up like you suggested and with 10k records it seems to work just fine, maybe its the server getting bogged down on your side.

      • Agree,could be my server

        By Steve Smillie 1 decade ago

        Although I am working on a dedicated test server, it is a VM server and has some IO slowness. It may have to do with the 50k documents in my view as well.  I have done similar on smaller views and not seen this issue.

        I hope this improves when on a production ready server.