Adds a new setting to the setup screen to select the minimal word length.

Shorter words entered by the user will not be checked. The grid above the board displays a white 'x' instead of the number and the results page will not display shorter words.

Current possible values as '2+', '3+' and '4+'.

If there is time remaining, but I cannot think of any words anymore, I'd like to be able to go to the results screen without having to wait until time is up.

When scrolling though the list of possible words, I would like to see the board I've been playing.

If possible, when a word is selected, highlight it on the board, preferably using arrows or animation to show the full path, not just the letters used.

With this change, the positions of the sliders are remembered from run to run.

If you clear data in the settings, the built-in defaults are re-applied.

To clear the data, go to your application overview, long press the app and drag it to App Info, click on Storage. Then there is a button called clear data.

This can be used by the dart analyzer to generate warnings.

For an example, see https://github.com/TOPdesk/dart-html-whitelist/blob/master/analysis_options.yaml

When during gameplay the screen is rotated from portrait to landscap I get the following output in the console:

I/flutter (32302): The following message was thrown during layout:
I/flutter (32302): A RenderFlex overflowed by 426 pixels on the bottom.
I/flutter (32302): 
I/flutter (32302): The overflowing RenderFlex has an orientation of Axis.vertical.
I/flutter (32302): The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and
I/flutter (32302): black striped pattern. This is usually caused by the contents being too big for the RenderFlex.
I/flutter (32302): Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the
I/flutter (32302): RenderFlex to fit within the available space instead of being sized to their natural size.
I/flutter (32302): This is considered an error condition because it indicates that there is content that cannot be
I/flutter (32302): seen. If the content is legitimately bigger than the available space, consider clipping it with a
I/flutter (32302): ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex,
I/flutter (32302): like a ListView.
I/flutter (32302): The specific RenderFlex in question is:
I/flutter (32302):   RenderFlex#50038 relayoutBoundary=up1 OVERFLOWING
I/flutter (32302):   creator: Column ← _InheritedProvider ← Provider ← MediaQuery ← LayoutId-[<_ScaffoldSlot.body>] ←
I/flutter (32302):   CustomMultiChildLayout ← AnimatedBuilder ← DefaultTextStyle ← AnimatedDefaultTextStyle ←
I/flutter (32302):   _InkFeatures-[GlobalKey#91812 ink renderer] ← NotificationListener<LayoutChangedNotification> ←
I/flutter (32302):   PhysicalModel ← ⋯
I/flutter (32302):   parentData: offset=Offset(0.0, 80.0); id=_ScaffoldSlot.body (can use size)
I/flutter (32302):   constraints: BoxConstraints(0.0<=w<=683.4, 0.0<=h<=331.4)
I/flutter (32302):   size: Size(683.4, 331.4)
I/flutter (32302):   direction: vertical
I/flutter (32302):   mainAxisAlignment: start
I/flutter (32302):   mainAxisSize: max
I/flutter (32302):   crossAxisAlignment: center
I/flutter (32302):   verticalDirection: down

The screen also displays an error message:

Some boards are great, others not so.

Currently the board is generated by randomly selecting letters based on the frequency they occur in their language.

Some problems:

• Clusters of consonants. (dead letters, not part of any dictionary word)
• Lonely X and Q
• Boards with too few solutions

Possible improvements:

• Start with placing a 9+ word on the board. Possibly adjust the bias for generating the rest of the letters.
• Use letter combination frequency (we can generate those from the dictionary) to improve the chances of finding words that contain letters that have a low frequency. Examples: 'Q' raises the chance of a neighboring 'U', or in Dutch, improve the chances of generating a 'sch' or 'ij' path.
• Replace dead letters. Letters that are not part of any of the found words can be replaced by other letters. Possibly it is easier to regenerate a whole new board. Don't forget to stop after a few tries. We could also say that each board letter should be part of at least two words. Keep in mind that the solver needs to be able to find all occurrences of the dictionary words for this to work.
• Build the board by fitting dictionary words, not by selecting single letters. (nice programming challenge). The difference with replacing dead letters is that this can optimize for putting in as many words as possibly. The algorithm should not be too strict to prevent generating the same puzzles.

Or a combination of some of the ideas above.

This pull request makes is no longer necessary to carry the whole configuration.

Also, the loading of the languages is split off, making it easier to test (not included),.

The idea is that we only need to load one language at the time. And contents of a language not dependent on the game state.

For my understanding, life cycles:

• Application: language data (currently immutable), preferences (mutable)
• Game: board, solution, game parameters (all immutable)
• UserAnswer, Game Clock: change after every swipe, second (mutable)

This pull request moves the scoring algorithm to gamelogic. This allows for easier unit testing (not included)

Added feature: if all words have been found, the result screen will be shown directly.

In the previous implementation, the back arrow was no longer part of the navigation bar of the results screen. However, the android back button would go back to the game screen.

By using pushReplace, the game screen is removed from the navigation history.

Keep track of committers, both to give them credits, and to make sure their commits transfer the rights to the project. See https://github.com/rzwitserloot/lombok/blob/master/AUTHORS