Это видео недоступно.
Сожалеем об этом.
How to use Flutter Navigator 2.0? | Warning: it's complicated
HTML-код
- Опубликовано: 12 авг 2024
- Worksheet: github.com/happyharis/navigat...
Answer: github.com/happyharis/navigat...
The new Navigator 2.0 is a little confusing, with the new Navigator and Pages widgets. Is the new navigator an imperative or declarative programming? What is imperative or declarative?
Therefore, this video will these questions and show you how to refactor your Flutter project from a default navigator, to the new one. Should you use the new navigator? That maybe a next video.
Is the default navigator declarative or imperative or both? I think is imperative. I'm open for any suggestions.
👉 Subscribe to our weekly Flutter newsletter:
learnfluttercode.com/newsletter
📱 Pre Sign Up to Learn Flutter App :
learnfluttercode.com/app
Check out our website - learnfluttercode.com/
🔥 Check out our courses - zukunf.com/courses
🖼 Learn Flutter Code Instagram:
/ learn.flutter.code
Haris's LinkedIn - / muhammad-haris-bin-sam...
Haris's Twitter - / thehappyharis
⏰ Timeline:
00:00 - Introduction
00:42 - Difference between Navigator 2.0 vs Navigator
01:21 - Imperative Programming
05:03 - Declarative Programming
05:50 - Convert default navigation to the navigator 2.0
07:40 - onPopPage params
11:42 - What is ValueChanged function?
13:51 - Create page for book
16:11 - Declarative also has some imperative
16:48 - Summary
🎨 Source:
/ learning-flutters-new-...
0:35 Forking ohh.... Okay
Great video, it was clear and simply. I was able to get the main concept of the nav. Keep up the great work!!👍🏿👍🏿
Glad it helps!
Thanks for this simple and approachable intro to Nav2.
As noticed and commented, it is a lot of boilerplate indeed. Reason for that is to enable building navigators for much more complicated cases.
For basic stack push/pop and its named variant, Nav1 or packages based on it to even simplify it (eg autoroute, fluro, get) are still very good alternatives. I am looking forward to seeing packages that make using Nav2 simpler and less boilerplaty for some specific more advanced use cases, often related to Web and Desktop navigation and their seamless transition to phone sized navigation. Not only url handling, but eg inserting master/child view page as poppable page when you resize the screen to phone size. Totally doable now that you can easily control the page stack.
No problem. It is a lot of boilerplate. And I would agree that it is for more complicated cases
I really like your method to explain and share in flutter learning (in many of your videos), put it in real life case to make me more easy to understand the logic inside of coding, great works and thanks!
Bro you have a such great personality and your explanation is on the point and made the things so easy to be absorbed
thanks bro
Not a fan of how most people do navigation... I tend to hide the navigation logic inside the page you are navigating to
So when navigating I just call a async handler:
final result = await BookPage.navigate(context,book);
Then I can handle the result of the popped page in a linear fashion. I think people are overcomplicating navigation...
Thanks for the video, nice introduction to the new navigator
I loved your video man it was cristal clear thanks
Maybe a quick code recap would have been perfect at the end :)
Thanks for the idea!
Tnank you very much...
how do you zoom.. is it a shortcut? OR zooming is done while editing the video?
Hi, please Let me know if I add a new page support page totally unrelated to book and doesn't depend on _selected book . On a button click from anywhere take to support page . How can we navigate from any page to support page
Very well explained
Thanks
I'll keep using auto_route instead :D
hi sir, i enjoy watching your videos. I was going to ask something.Which theme are you using?
thanks. material theme.
those are some crazy boilerplate code. No thanks I'll keep using nav 1.0
I agree on this.
Is it possible that nav 1.0 will get "obsolete" and we will have to migrate to 2.0? Because I'm currently learning nav 1.0 from an online course.
@@arthurlima923 Here in Brazil we belive that it will used just for packages to easely some tasks, and that the "normal user" will continue to use nav 1.0.
@@MaxweelFreitasdaSilva Opa, valeu cara! Sou Brasileiro também. Achei muito complexo o 2.0, espero que depois simplifiquem.
@@arthurlima923 Então, com vista nisso a comunidade (Flutterando) está empacotando o nav 2.0 dentro do Modular (pacote que te auxilia com gerenciamento de rotas e injeção de dependências)
What extension of vscode do you use to mark code blocks with white lines? Thanks 🙂
Same here
It's simple.
* Open VS Code Settings (by pressing ctrl + ,)
* In search bar, type "flutter UI guides"
* Now TICK the checkbox - (preview flutter UI guides)
Does it mean tha the whole application is updated every time a navigation flow is executed?
I am more interested the vs code extension you use to display the errors on the same line. What is the extension called?😁
Error Lens.
thanks man!
Happy to help!
Can I ask how I can set the initial route (at first launch of the app) to '/home' instead of '/'?
change initial route to '/'
Great video! Now, about the new navigator.... what a mess.
Tell me about it
BRILLIANT!!!
Hi I love your videos, one question how do you get the 'red' comments in VSCode while you are typing in commnads please, thanks Pierre
I use the VSCode extension error lens.
@@LearnFlutterCode thanks a million, I'am looking for a demo on how to use an existing sql database in flutter app
I thumb up because it is easy to follow as a basic introduction to Navigator 2.0
The best moment is when he says: "Personally, I don't know exactly what onPopPage does". 😀
That comment tells how messy is the new Navigator API.
if you press a "BackButton" an event gets triggered to pop the current page. You can use that function to e.g. reload something.
so basically it listens to the change of selected book automatically so we just change the state that's all that's kind of cool with state management its easy
What vscode plugin gives you the errors inline with the code?
Error Lens in VSCode extension
Tutorial on how you made the books app it looks sick
I have not figure out how to make the tab bar, the one you see is fake XD. Other than that, most of the UI is achievable
thanks for this video but i think old one is better
it really is complicated
Make sure you 'fokk' the project !
yeah i wonder how i can 'fokk' projects, because there are so many i want to 'fokk'
I thick it's so f**kable in huge project . just use 1.0 version :)
It depends on your use case
yep
i dont understand lol.. how can u navigate nnext screen
No worries, a lot of people do not understand too.
@@LearnFlutterCode I understand this.. but I not understand that flutter web navigation.. if u kind can give example again that not have id book
like a simple navigation to the next screen using navigation 2.0
in search of gold we lost Dimond be like :p
why it so complex now? for what?
Some Javascript developer must have snuck in a #@%&*(&d things up for us.
for simple cases, this method is too complex. however, if you want to have users change the url and sync with your flutter web app, then this is one way.
@@LearnFlutterCode For any case, this is too complex. I have no problem synchronizing my URL with the existing system & Fluro - and I'm currently exploring ways to get Fluro out of the mix. Someone must be feeling the need for some extra job security, needlessly complicating things so nobody can follow behind them. What ever happened to 'optimize for developer happiness'?
Isn't the level of the audio extremely low?
Thanks for raising the issue. Will take note!
0:35 you can follow along this tutorial by fu*king this project
Audio is way too low!
Will take note
sorry, but this approach of creating stateful widget instead of stateless just because of navigation 2.0, sucks.
what's hard about this? XD
ever
ry
thing
Arguably the worst thing Flutter introduced so far