Your video series are gold mines, some widget are hard to find, and you do not always know what you're looking for. Thanks for that, I hope this serie and the 101, will continue.
I'm familiarizing all flutter widgets by watching *Flutter Widget of the Week* by sequence. I do some little experiment after watching each videos. Now I got stuck to this InhertedModel widget. I'll skip it for now and come back later once I have the deep understanding on Flutter framework. I feel that this widget plays an important role on complex Flutter projects.
Scoped model solves a different problem. InheritedWidget/InheritedModel ancestors can only subscribe to the data, but not change it(not directly at least). Ancestors of Scoped Model can also change the data they subscribe to.
From the pragmatic state video from Google, Scoped Model: The state of a specific widget A has to be passed down through many descendants to arrive the leaf widget F, then if state changes, myriads in the branch will get rebuilt (but u actually only want the widget F to get rebuilt).
it is not about class inheritance at all. nested widgets are not inherited from theirs ancestor container. it is kinda bad name they choose that causes "anti-inheritance seizure" for some people. I think a word like "composite" would be a better match.
@@emilyfortuna2262 build my own provider? Thanks but no)) I fully trust and rely on Rémi Rousselet 😁 P.S. I agree that we need to know how it's built and how such pattern works in Flutter
Provider and Riverpod are mostly overkill for some apps. And if done badly they can bloat code/affect performance. But if it works for you. Then good ;D
![[Part 1] รักมาไม่ทันตั้งตัว❤ หนุ่มสาวโสดถูกจับมาแต่งงานกันกะทันหัน แถมเธอยังเป็นหัวหน้าของเขา?!](http://i.ytimg.com/vi/y2pOOMkuFI0/mqdefault.jpg)
Your video series are gold mines, some widget are hard to find, and you do not always know what you're looking for.
Thanks for that, I hope this serie and the 101, will continue.
its coming from google, the one who makes flutter, ofc it'll have a good and informatic videos about the product
A bit complicated but I'm sure it'll be clear once I do a practical
I gave up half way. I will try it another day🙄
I'm familiarizing all flutter widgets by watching *Flutter Widget of the Week* by sequence. I do some little experiment after watching each videos. Now I got stuck to this InhertedModel widget. I'll skip it for now and come back later once I have the deep understanding on Flutter framework. I feel that this widget plays an important role on complex Flutter projects.
I think the new Provider package substitutes the need for this widget now for newcomers.
@@shubhammittal9764 thanks in advance, I'll note that.
InheritedModel is really OP if done nicely. You get fine grained control over the rebuilds.
This is sort of difficult to understand on first go. But I'm sure this would prove handy when required.
Ah, another state management option. Good to know about it, but I 'll just stick to Provider for now.
Music and animations make it look fun and easy. But I'm pulling my hair out. Oh well. Just need to keep grinding. I'll get there...
We are waiting for Flutter Web Stable version
its stable now . whats your plan to do hanh? :P
I thought that its really a cool idea of a widget
This is what I have been looking for!
nice work google
Very useful but how does this differ from ScopedModel?
ScopedModel, like InheritedWidget rebuilds your Widget for any change. InhertitedModel only rebuilds when the "aspect" changes.
Scoped model solves a different problem. InheritedWidget/InheritedModel ancestors can only subscribe to the data, but not change it(not directly at least). Ancestors of Scoped Model can also change the data they subscribe to.
From the pragmatic state video from Google, Scoped Model: The state of a specific widget A has to be passed down through many descendants to arrive the leaf widget F, then if state changes, myriads in the branch will get rebuilt (but u actually only want the widget F to get rebuilt).
Hey google. India loves you
is it like to context on react ?
not really useful to my work since my design is to stay away from the inheritent bloating classes like i used to face in java or c#
it is not about class inheritance at all.
nested widgets are not inherited from theirs ancestor container.
it is kinda bad name they choose that causes "anti-inheritance seizure" for some people.
I think a word like "composite" would be a better match.
Apparently Provider package is recommended over inherited widgets/models
@@emilyfortuna2262 build my own provider? Thanks but no))
I fully trust and rely on Rémi Rousselet 😁
P.S. I agree that we need to know how it's built and how such pattern works in Flutter
Provider and Riverpod are mostly overkill for some apps. And if done badly they can bloat code/affect performance.
But if it works for you. Then good ;D
way better than react
This is new
0:42 demonetized.
Why?
@@ShivamJha00 it's the demonetized icon, the yellow filled circle with a dollar symbol in the middle.