No video :(

Beginning Flutter - Understanding and Refactoring the Widget Tree

Подписаться 5 тыс.

Просмотров 8 тыс.

50% 1

In this video you are going to take a look at:
- The fundamentals of widgets
- How to use a full widget tree
- How to use a shallow widget tree
- Refactoring with a Constant
- Refactoring with a Method
- Refactoring with a Widget Class
The widget tree is how you create your UI; you position widgets within each other to build simple and complex layouts. Since just about everything in the Flutter framework is a widget, and as you start nesting them, the code can become harder to follow. A good practice is to try to keep the widget tree as shallow as possible. To understand the full effects of a deep tree, you’ll look at a full widget tree and then refactor it into a shallow widget tree, making the code more manageable. You’ll learn three ways to create a shallow widget tree by refactoring: with a constant, with a method, and with a widget class.
Looking for Updates:
JediPixels.dev
Beginning Flutter Book:
www.amazon.com...
Subscribe:
www.youtube.co...
Twitter:
/ jedipixels
#flutter #appdevelopment #dart #appdevelopment

Опубликовано:

26 авг 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 17

@sandwichtube 3 года назад

Thanks. My code is now next level.

@JediPixels 3 года назад

Thank, much appreciated.

@venkatbalak6692 3 года назад

A big thank you for your videos. Very helpful for a beginner like me.

@JediPixels 3 года назад

Thank you.

@chournpechsovann4120 3 года назад

thanks

@JediPixels 3 года назад

Thank you.

@user-gu5ts5nx8r 4 года назад

Thanks for sharing

@JediPixels 4 года назад

Thanks for watching!

@SnowGroth 4 года назад

so... to conclude, it's best to refactor with a widget class?

@JediPixels 4 года назад

It really depends on your needs. Refactoring by a Widget Class give you the better performance optimization but it requires writing more boiler plate code. Refactoring with a Constant or a Method allows the separation of code for better readability (separating logic) but no performance gain. I personally use both Widget Class and Method refactoring.

@kasandrop 4 года назад

I just got lost now. Because you say 5.14 Every time the parent widget is redrawn, all the widget classes will not redraw. They built only once. And you dont say that these widgets have to have const constructor. Earlier on you say if we omit const the widget will be called( will rebuild itself) every time the parent redraws.4.51

@JediPixels 4 года назад

The Constructor for the StatelessWidget (ContainerLeft) needs to be declared with the const keyword and when you use this StatelessWidget (ContainerLeft) in your page, it must be declared with the const keyword. At 4:52 in the video you can see the code showing it. // Constructor for ContainerLeft StatelessWidget const ContainerLeft({Key key,} : super(key: key); // In your page, initialize the widget with const keyword const ContainerLeft() I hope this clarifies your question. Thank you.

@kasandrop 4 года назад

@@JediPixels Thank you for the answer