Hi Santhosh Kumar Krishnan, I really appreciate you liked it.
There is not really specific code for the article. I took the code we used in the Madrid Flutter Study Jam (as stated in the article) and just plugged the code snippets when creating the Hero widgets.
Hope it helps.
Hi Scott, nice write up.
I have given a look to the code and tested it, and I have seen several things.
Though it is true that you only write one container, Flutter creates, under the hood, the same amount of widgets on both cases. Just give a look to Widget inspector.
Nice Write up!
There is another option, or better, a way to complement your third option.
The State class has a ‘didUpdateWidget()’ that is called whenever the widget definition changes. You need to override this method to respond to widget changes. The build() method is always called after calling ‘didUpdateWidget()’ so no need to call setState().
Thanks Charles for taking the time to write the package.
But I see that the middleware saves the whole state on every action. If the state is big and you have a lot of actions, this can quickly become a bottleneck.
I’ve given a look to the code. But it is not easy to make changes due to the way the…
Nevetherless, the libraries also account for the framework, so, all in all, you end up needing less development time while increasing productivity.
Flutter is still in its infancy and it is already able to stand up to more mature solutions. We can just hope that in the future this will just be better .
Glad you liked it.
Since Wm Leler was also asking for the development process, I answered in his response having in mind all your questions.
In Android the original author uses two ViewPagers. The front ViewPager has some padding so you can see three pages on the…
I can’t really compare because the Android part was done by someone else.
For the Flutter part, it was a learning process where I wanted to use some of the things learned after thoroughly studying the animation sample in the Gallery.