Hi again! It’s about time to add some more code to the BMI Calculator app - by Johny Vino’s design. In this post, I will start creating bottom pacman slider (see below). I will go through implementing the animated hint which will indicate user on how to use the slider. Let’s make it happen! 🙂
As always, let me show you the effect we want to achieve first. This time I am going to show you the exact result widget from this development instead of the design:
First, let’s create static aspects of this view,
Dot are simple stateless widgets to be displayed. Since we are going to have 2 sizes of dots, the size will be parametrized:
We are going to place those widgets inside rows and paddings:
Container specifies slider’s height and decoration (with shape and color) – nothing interesting here.
The main body of the widget is a
Row with pacman and dots. To create the middle dots, we used
List.generate – it allows us to generate any list (in our case a list of widgets) using simple generator (
_generateDot) method. We can also add the bigger dot at the end of the list. Notice that we already specified
Opacity for that dot, the middle ones will be animated later on. Let’s take a sneak peek on what we have:
Now let’s add animation controller, which will be responsible for changing dots’ opacity. For now, we can assume that this controller’s animation will take 1 second and after another 800 milliseconds, it will run again from scratch. At this point, we can also wrap middle dots with
AnimatedBuilder, so that they will be rebuilt alongside animation changes. Let’s take a look at the code:
At this point it looks like this:
As you can see, at this point every dot is animated at the same time. I guess it’s a bad hint to swipe right. Theoretically, we could create a list of
AnimationControllers and have them be delayed from each other by a small amount of time, but I don’t think it would be an optimal solution. The approach I went with is the same I used for Flight Search challenge –
Intervals. Intervals are special kind of animation curves that allow us to “use” only a part of AnimationController. We can specify at what point of our parent animation we want interval animation to begin and end.
Let’s take a look at how it looks in code:
Notice that we also specified
Twin in which we defined the minimum and maximum values for the animations. Now we can see that dots appear one after another:
We are very close to the final effect, now we have to deal with the following problem: After a dot is animated it stays in the maximum state but it should get back to the minimum. Unfortunately,
Tween animations will always give us a curve from
end and we need it to go from
min again. How to deal with that problem? Create our own Animation!
This animation will provide sinusoidal behavior of the value, so that every dot will nicely get from
maxOpacity and then return back to
minOpacity. The only thing left now is replacing Tween with our new animation and tweaking up the parameters to have the look we want:
And that’s it!
If there is anything unclear or there is something I did wrong, please leave a comment and tell me about it!
Originally published at marcinszalek.pl on October 19, 2018.