Closed somelinguist closed 11 years ago
Fixed in 0.1.9.
What about auto suggest? have you seen the JavaScript Chosen http://harvesthq.github.com/chosen/ or Select2 http://ivaynberg.github.com/select2/
I might end up using auto-suggest for other features, but not for the spelling practice (it would defeat the purpose). I thought about it for the filters, but usually they already narrow the list down pretty well after typing 2-3 letters. I think I would rather add Excel-like filters than simple auto-suggest ones, so it would suggest things in the drop-down that could be checked or unchecked to create the filter.
I tried out Select2 in an early version for making a drop-down based on the semantic domain list, and it took a huge performance hit loading the list with that much data (it was fine after it loaded, though).
Oh, I didn't see that this was about learning to spell.... but isn't that a dead skill anyway? (I mean thinking progressively and digitally....)
On Mar 18, 2013, at 9:04 AM, somelinguist wrote:
I might end up using auto-suggest for other features, but not for the spelling practice (it would defeat the purpose). I thought about it for the filters, but usually they already narrow the list down pretty well after typing 2-3 letters. I think I would rather add Excel-like filters than simple auto-suggest ones, so it would suggest things in the drop-down that could be checked or unchecked to create the filter.
I tried out Select2 in an early version for making a drop-down based on the semantic domain list, and it took a huge performance hit loading the list with that much data (it was fine after it loaded, though).
— Reply to this email directly or view it on GitHub.
I think there's still value in spelling.
Actually, the bug did cover the filters for the grid, too. I had updated both so they would match on precomposed and decomposed characters. I had to use a custom filter in angular for the grid. The default filter ignored case, which is helpful in general (noun and Noun should be the same). The spelling feature probably was case-sensitive before, but you wouldn't notice it as much. I just added .toLowerCase() in both places. But I might add an option somewhere for case sensitivity.
I forgot to check for case after changing the matching algorithm. I'll work on a fix for the next version.