filler: switch to a pure JS auto filler #21
Conversation
Glucose is fairly slow, and in its current implementation does not support scored wordlists. On a test puzzle of mine, glucose fails to find a solution within the 30 second timeout. I have written a purpose-built, fast javascript solver which finds a solution in 7 seconds on the same puzzle with the same wordlist. Moreover, this implementation supports asynchronous updates (giving visual feedback of the in-progress solve), and scored wordlists, although neither of those features are yet used in this change. Switch Phil to use the javascript solver.
|
Hello and happy holidays! I had written a javascript crossword constructor before finding out about your project. You can read about it and find a link to the webapp: https://bobcopeland.com/blog/2017/11/on-board-the-rebus/ Anyway, I stumbled across Phil, and the UI is a lot better in your webapp. But I think my solver is a bit more complete. So here's a PR for your consideration. Please give it a spin, and if you agree I'd be happy to further flesh out the integration. |
|
ping, any interest in this? |
@bcopeland |
2 participants
Glucose is fairly slow, and in its current implementation does
not support scored wordlists. On a test puzzle of mine, glucose
fails to find a solution within the 30 second timeout.
I have written a purpose-built, fast javascript solver which finds
a solution in 7 seconds on the same puzzle with the same wordlist.
Moreover, this implementation supports asynchronous updates
(giving visual feedback of the in-progress solve), and scored
wordlists, although neither of those features are yet used in this
change.
Switch Phil to use the javascript solver.