I'm really loving the Google ecosystem. Coming from a React/React Native background, I'm seeing Angular and Flutter able to do so much stuff for you out of the box and it's really nice. They really took time to think about the developer experience with their products.
I have been following this tutorial and enjoying it very much, but I am extrememly frustrated that there does not appear to be a third video! Am I missing something?
Please make a video about more complex state Management. I don’t know what to do when I have multiple futures to await. Do I combine them into one and use a futurebuilder? Do I call them in initState and act on each one individually? I can get most things to work how I want, but I’d really like to know some best practices.
Is there some design advantage to having widgets behave this way rather than just having them behave the expected way, where if you click a box it becomes checked without the need for extra code?
I think its a matter of performance and change detection - with state changing via setState the underlying "engine" knows it may need to update that widget (and, potentially, that widget only, down the tree) rather than the engine trying to detect changes and handle them. Its like if you wanted to change the icing on the cake to be green - using setState(color=green) in the icing bit of the recipe, you know you ONLY have to remake the icing - the rest of the cake remains the same. The alternative is that you would have to keep track somehow if every part of your recipe constantly checking to see if anything has changed and (potentially) remaking the whole cake in case something has changed.
Data persistence. Changing UI doesn’t mean much if it is not saving the data in a permanent way so that the “check box” has a meaningful effect. The state object is able to reach deeper into the app data. The widget is just made for display purposes. The reasoning is due to ‘separation of concern” so that each small part of the code can just do it’s one thing. It’s easier to keep track of, and there’s less spaghetti code - where variables are reference all these different places in an app and changing one thing becomes a nightmare of tracking everything it effects.
Please help I got on error on flutter web ...errors description is This can happen if the websocket connection used by the web tooling is unabled to correctly establish a connection, for example due to a firewall.
The playlist “Begin learning Flutter” is chaotic. Perhaps someone should sort the videos and maybe move some of them into other playlists. Had to skip 2 videos to get to this, and I hope I can follow further, but it's a bit of a mess.
c'mon flutter just make it simple to update stuff. I still don't get it. it's easy on this example, how do you update a colour of a vector, in child widget when you are using the same widget to show the same widget in multiple places in the same page with different colours for each and you want to change the colours individually when you click it. Use that example and you'll realize you have made it really suckkk to make it happen in real life scenarios. It's easy if it's in the same class, use different classes and pass data like in my scenario and you won't even make a video as it'll be a mess to do it in flutter.
Even though I know what is state, I watch the videos of Flutter team because they are so smooth
I agree
I feel like a kid where my mom is narrating me a fantasy story while I get comfortable in my bed. Smooth story telling!
Yes!!!
Please please 🙏 post more frequently in this series . This is such a great playlist.
These videos can't be easy to make. I think your effort is heroic!
Even the flutter team is explaining with VS code! It's amazing!
@Karthi Keyan said no one ever
When will the third video in the series be ready?
Thanks for these videos!
I’m also looking for the last episode of this series as well. Looks like it’s not coming...
I'm really loving the Google ecosystem. Coming from a React/React Native background, I'm seeing Angular and Flutter able to do so much stuff for you out of the box and it's really nice. They really took time to think about the developer experience with their products.
wow this man is a good teacher
You remind me of Emily so much! Face gestures, eyewinks 😄 it’s like I’m looking at her 😄
I was also thinking the same😂
True
may be they are family
@@eliasayele1102 😂😂
This is high praise! But, no, Emily and Fitz are good friends, but they aren't related.
한국어 자료가 부족했었는데 좋은자료 주셔서 감사합니다!! :)
I can't find the third video in this series. Is it on UA-cam?
That was an incredible explanation of State
This is the clearest tutorial I've ever watched
I have been following this tutorial and enjoying it very much, but I am extrememly frustrated that there does not appear to be a third video! Am I missing something?
Please make a video about more complex state Management. I don’t know what to do when I have multiple futures to await. Do I combine them into one and use a futurebuilder? Do I call them in initState and act on each one individually? I can get most things to work how I want, but I’d really like to know some best practices.
Wwhere is third video??
Smooth, fun and useful
Is there some design advantage to having widgets behave this way rather than just having them behave the expected way, where if you click a box it becomes checked without the need for extra code?
I think its a matter of performance and change detection - with state changing via setState the underlying "engine" knows it may need to update that widget (and, potentially, that widget only, down the tree) rather than the engine trying to detect changes and handle them.
Its like if you wanted to change the icing on the cake to be green - using setState(color=green) in the icing bit of the recipe, you know you ONLY have to remake the icing - the rest of the cake remains the same.
The alternative is that you would have to keep track somehow if every part of your recipe constantly checking to see if anything has changed and (potentially) remaking the whole cake in case something has changed.
Data persistence. Changing UI doesn’t mean much if it is not saving the data in a permanent way so that the “check box” has a meaningful effect. The state object is able to reach deeper into the app data. The widget is just made for display purposes. The reasoning is due to ‘separation of concern” so that each small part of the code can just do it’s one thing. It’s easier to keep track of, and there’s less spaghetti code - where variables are reference all these different places in an app and changing one thing becomes a nightmare of tracking everything it effects.
Where is the third one of these? They are very good but its missing the nice bits
Great explanation! Let's dive into provider package 🤪
hi dear Flutter team can give link of this playlist , thanks
ua-cam.com/play/PLjxrf2q8roU1fRV40Ec8200rX6OuQkmnl.html
very nice explaination
Thank you for your kind words, Heshan! We truly appreciate your continued support 🙂
Good video!
Then what is the use of state less widget
brilliant explanation
Nice job, is there a link to the first video ? Simer
Please help I got on error on flutter web ...errors description is This can happen if the websocket connection used by the web tooling is unabled to correctly establish a connection, for example due to a firewall.
thank you
Really helpful 😊
I love your content so much
is this the same as useState hook in react?
where is the next episode?
what is (newValue)?
Flutter support open GL ?
Thanks Fitz
@Andrew fitz #Andrew fitz, sería una buena idea que tú seas el representante de Flutter spanish no crees?
So helpful
The playlist “Begin learning Flutter” is chaotic. Perhaps someone should sort the videos and maybe move some of them into other playlists. Had to skip 2 videos to get to this, and I hope I can follow further, but it's a bit of a mess.
Flutter gradlew not working properly
amazing
Wheere is the next video please?
Hi! You can find the next video here in the Begin Learning Flutter playlist: goo.gle/3ChTUTE
Please make a social app using sql server
I have been using flutter since 2 years and always wondering that,
Shouldn’t it be updateState() instead of setState() ?
Flutter followed principal of react that's why setstate
Unable to flutter run
I like it
😊❤
má nó thích làm dev mà đ biết tiếng anh xem chỉ nhìn hình đ hiểu cái j
c'mon flutter just make it simple to update stuff. I still don't get it. it's easy on this example, how do you update a colour of a vector, in child widget when you are using the same widget to show the same widget in multiple places in the same page with different colours for each and you want to change the colours individually when you click it. Use that example and you'll realize you have made it really suckkk to make it happen in real life scenarios. It's easy if it's in the same class, use different classes and pass data like in my scenario and you won't even make a video as it'll be a mess to do it in flutter.
And all this time I thought it was Texas
Are you a developer or an actor?
Please add sub italian :)
Эх, почитать документацию на русском языке, будет понятней! Есть особенности, их не понимаю. Переведите, пожалуйста.
[deleted]
Did you do setState? 😀