If you are interested in Why Bineroo? Why Flutter? and details on the inception of the project, I encourage you to read the introductory article “It all started with a mosquito”.
Starting with this article, I will dive a bit deeper into more technical details on the project. Readers will need a bit of understanding of the Flutter framework.
Analysis of the requirements
The core element of the game is a grid.
A grid is composed of N by N elements called tiles (N = 6 on the example above). The first rule of the game is “Equal number of blacks and whites in each column and row”, therefore you guessed that N is always an even number.
Each individual tile can be in one of the following states:
- 0 (represented by a white circle ⚪️ )
- 1 (represented by a black circle ⚫️)
- Empty (represented by an empty circle with a red border)
Now you understand why it is called Bineroo 😉
Each tile can also be mutable or not. This depends on its initial state. If a tile is given a non-empty initial state (i.e. 0 or 1), it is considered immutable. It will keep its initial state during the whole game. If a tile is given an empty initial state, then it is considered mutable.
From a UX perspective, I decided that tapping on a mutable tile would make it shift from one state to another in the following order:
empty -> 0 -> 1 -> empty and so on.
In order to represent the state of the whole grid at any moment, I chose to use a string of N*N characters composed of 0’s, 1’s, and dots (dot representing an empty element). The title of this article should be a bit less confusing now 😄.
Tapping on a mutable tile will make it shift its state (as explained above) and consequently will also change the state of the whole grid. At every change, we need to check if the grid has been totally and successfully completed. If it is a success, the user is notified and the game stops. If there are still some empty elements or errors, nothing happens.
If we wanted to be totally purist, verifying the current state would require to check the respect of all 3 game rules in order to decide if the completed grid is correct or not.
This is not a difficult exercise but for the sake of simplifying this article and focusing more on widgets rather than on algorithm, I took the liberty to add a solution string. Checking the correctness of a grid is simple as checking if the current state of the grid represented by its string variable is equal to the solution string. Voila!
Once again, I know that for a given initial grid state, there may be multiple possible correct answers. I have a cool exercise in mind, purely algorithmic around that subject. I promise I will come back to it in a future post but for the moment, please stick to my simplistic option.
At that point, I believe everything is crystal clear and we can head to our favorite IDE (VS Code for me) to start the fun part: coding.
First, start by creating a new Flutter project
flutter create <project_name>
Let’s start with the Tile widget by creating a new file named “tile.dart” in the lib folder.
As mentioned above in the requirements, a tile may have a changing state if it is mutable. Consequently, the Tile widget extends the StatefulWidget class and we also need a _TileState class that extends State<Tile> class.
In terms of properties, a tile will have:
- A value represented by a String of a unique character with one of the following possibilities “0”, “1”, “.”
- A mutable state represented by a bool
- A position represented by an int equals the index of the tile within the grid String
- A callback function represented by a dynamic type var that will be called every time a mutable tile is changed
The build method of the _TileState class is pretty straightforward as the widget is very simple: A Container with a circle shape encapsulated within a GestureDetector to handle the tap events. No need to comment on this simple code.
Let’s move on to the Grid widget.
Create a “grid.dart” file in the lib folder
First question: Is Grid a Stateless or Stateful widget? From the first point of view, one would think of a Stateful widget as the grid state is changing over time. The answer is not obvious and I chose to extend the StatelessWidget class. So why?
Making the grid stateful would mean that every time the state is changed, the whole has to be redrawn. In our case, the grid state is changed every time a mutable tile is tapped. But we only need to redraw the tapped tile and not the whole grid. That would be a waste of performance. Thanks to the callback function, the tapped tile can inform the grid of its change so this latter can take the appropriate action (here: check for success). Each tile is already a stateful widget, therefore the whole grid does not need to be stateful.
There are always multiple solutions to the same problem but as a rule of thumbs, I always start by making my widgets stateless and, when the need for redrawing comes, I ask myself what part of the screen needs to be changed and I make the smallest component Stateful to fit that requirement.
Bonus: How to convert a stateless widget to stateful with key shortcuts
1. Click on the stateless class you want to convert
2. Tap Ctrl + Shift + . (this is a dot)
3. Select to Convert to StatefulWidget from the drop-down
This Ctrl + Shift + . has a lot of other possibilities to help you refactor you code. It works very well. I recommend you have a closer look at it to save some time.
The grid has 3 properties:
- its initial value
- its current value
- its solution
All properties are represented by a String of N*N characters.
The onTapped method is passed as a parameter to every instantiated tile and is called every time a mutable tile is changed.
A simple operation on the current String value of the grid is necessary to update it (NB: the position parameter of the tapped Tile is here necessary to know the index of character of the grid value to modify).
Once updated, we just check if the new value is equal to the solution or not. If it is the case, then we show an AlertDialog to inform the user of success (NB: showDialog method requires a BuildContext. This is the reason why we pass a BuildContext parameter via the onTapped method).
At this point, the coding can be considered as completed. At least for a first iteration. We can move to the next phase and see what’s missing and/or not working as expected
Test and Fix
Flutter and all its tooling ecosystem are very graphical so when it comes to testing, I always favor building a simple app to embed my widget and see how they behave rather than using unit test code. I know it is not great for automated CI/CD pipeline but for the time being, it will be just fine.
So, delete all code from the generated file “main.dart” in the lib folder and replace it with the following code:
The app uses the Material design. The main widget is a Container with a blue background and a Grid at its center (NB: Grid is encapsulated in a Center widget to place the grid at the center of the Container that automatically takes the whole available space).
Run the code on a local emulator and Bingo
Well …. not so Bingo
How come the grid is stuck at the top of the screen?
This is where the DevTools become very handy.
Your widget tree should look like this
The problem comes from the fact that most of the widgets of the tree have no imposed constraints from their parents.
If there is one rule to understand and keep in mind is this one:
Constraints go down. Sizes go up. Parent sets position.
More details here
In our case, MaterialApp imposes no constraints on Scaffold that imposes no constraints on Container that imposes …. Down to the Tile. The tile is the only widget with imposed constraints. Why? The GridView is taking the whole available space (no constraints and no sizes). But we specified in the GridView constructor that we wanted N elements on the cross axis (here the horizontal). Therefore the framework will divide the screen widget in N and assign this value as the width of each tile. As tile are squared, their height is equal to their width. The tile has constraints both in width and height.
So how to fix this problem? As the rule states, you can set sizes. The problem here is that the grid is taking the whole screen while we wanted it to be a square of size equals to the screen width. Let’s do that.
Wrap the GridView inside a Container and set the container height to the screen width (using MediaQuery widget). NB: Use the Ctrl + Shift + . to do the wrapping 😉
Re-run and now it should be all fine.
Tap the tile and make sure the immutable ones are not changing and the mutable ones are correctly moving from one state to the next one.
Let me help you to test the success verification by showing you the solution for the test grid
As expected the code is working for any grid size. Here are a few examples:
N = 8 / Initial value =
N = 10 / Initial value =
N = 12 / Initial value =
N = 14 / Initial value =
I won't give you the answers. You need to figure it out by yourself. Code a solving algorithm. Solve it on paper. Do as you want. I will be happy to get your answers as comments on this article.
This is the end of my first technical article on Bineroo. I hope you enjoyed it. Feel free to react and leave any comments. Always good to get some feedback.
The next article will be about persistence. How to save and resume a grid and having the possibility to play multiple grids in parallel without having to restore from the beginning.
Once again, this blog is meant to be a living thing. If you have any topics you want me to talk about, please leave a comment with your request.
PS: I am a great fan of Gitlab but too bad it is impossible to embed Gitlab snippets in Medium (Open issue here https://gitlab.com/gitlab-org/gitlab/-/issues/26936) and I find codepen.io, not that convenient. Had to put snippets on Github 😐