sklr Posted January 15, 2013 Share Posted January 15, 2013 Hi, Currently, script filters are stateless -- if one takes an argument, the filter script gets called after each letter is typed in order to regenerate the suggestions list. I've got a few cases where the full list of possible suggestions is known regardless of input, but the list is large and I'd like to allow the user to narrow down the options by typing more letters. For example, I have a script filter 'foo' that returns options ['bar', 'baz', 'quux']. As soon as the user types 'foo b', that should be reduced to ['bar', 'baz'], etc. Of the two ideas I have involving this at the moment, the first has all of its data generated locally. Therefore, I could update the generation script to take another parameter to filter results by without too much pain. However, the second workflow gets its data from a JSON webservice. The webservice isn't really designed for autosuggest, and is way too slow to consider calling it after every character. Because of the stateless nature of filters, if I wanted to make this workflow useful I'd have to deal with caching request data somewhere, expiring the cache, filtering results, etc etc. Do-able, but painful. Would there be any value in a new type of script filter that accepts a single long list of items, each of which is valid, and then deals with allowing the user to narrow down the selection by additional typing without needing to call out to the original script again? Link to comment Share on other sites More sharing options...
jdfwarrior Posted January 17, 2013 Share Posted January 17, 2013 Mind if I ask what language you are creating this script in? I do similar things with php all the time. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now