xwords/xwords4
Eric House b8f359c3e5 add filtering to wordlist browser
Add a basic regular expression engine to the dictiter, and to the UI add
the ability to filter for "starts with", "contains" and "ends with",
which translate into ANDed RE_*, _*RE_* and _*RE, respectively (with
_ standing for blank/wildcard). The engine's tightly integrated with the
next/prevWord() functions for greatest possible speed, but unless
there's no pattern does slow things down a bit (especially when "ENDS
WITH" is used.) The full engine is not exposed (users can't provide raw
REs), and while the parser will accept nesting (e.g. ([AB]_*[CD]){2,5}
to mean words from 2-5 tiles long starting with A or B and ending with C
or D) the engine can't handle it. Which is why filtering for word length
is handled separately from REs (but also tightly integrated.)

Users can enter strings that don't map to tiles. They now get an
error. It made sense for the error alert to have a "Show tiles"
button, so there's now a dialog listing all the tiles in a wordlist,
something the browser has needed all along.
2020-08-05 09:47:44 -07:00
..
android add filtering to wordlist browser 2020-08-05 09:47:44 -07:00
common add filtering to wordlist browser 2020-08-05 09:47:44 -07:00
dawg add filtering to wordlist browser 2020-08-05 09:47:44 -07:00
debian ignore debian build files 2012-01-04 18:11:29 -08:00
linux add filtering to wordlist browser 2020-08-05 09:47:44 -07:00
newrelay beginnings of new relay: shows persistence 2017-11-05 19:24:41 -08:00
relay add mqtt as a new transport 2020-05-20 13:58:53 -07:00
scripts more work on script 2014-02-26 07:52:18 -08:00
tests allow to run multiple games at once 2005-09-14 05:12:07 +00:00
Makefile include all .xml and .java files, but only if they're not named in a .gitignore file in the same directory 2014-03-01 11:44:20 -08:00