roSearchScreen enhancement request
I'm having issues using roSearchScreen because it is too "text"-driven. The issue is that there are duplicate text values in the suggestion screen -- and no way to accurately determine the actual sele...
Forum Discussion
Yeah, that's something I'm looking at now. Even with a naive (non-FTS indexed) approach, it's OK to do a per-character search. Obviously, (because of the lack of indexing) it may get slower with more characters. Dealing with thousands of audio, video, and image files -- I can still achieve sub second search times on my laptop. I think it's more intuitive to have an "autocomplete" feel to the search. Having to type and scroll all the way down and then all the way to the suggestion box feels klunky to me. If speed/performance does become an issue, I can always implement FTS with my database engine. What helps is knowing that the Roku will only display a few results. Because of that, I don't actually have to return or find every matching result; I can just quickly return the top N. Because of this, the search is actually really fast in practice.
