Erick
Erick
I realise this is in draft but I want to raise some discussion around this. I like the idea of navigator inside Flame, but I wonder if this isn't falling...
> Interesting, I thought the other way around, that it will be very nice to handle screens and scenes in the same way in Flame no matter if it is...
> Flutter can't handle Flame "scenes", which is a concept that people ask all the time about and I think having scenes consistent with how you handle screens would be...
> Maybe I misunderstood you then, but that only sounds like a documentation issue. :) I don't think it is only a documentation issue, only the existence of the navigation...
> What I mean is that with only push (without a named push) and pop you can only move linearly, which I guess is why the Route concept was introduced...
Alright, while I was thinking about the example, I think I finally managed to think this through better. > If we have named routes, then it is pretty much like...
Take your time @st-pasha , But like I mentioned on my comments, I definitely see value on this! I think my biggest concern is about the mix of contexts here....
> you don't have to learn this new system because the knowledge of the Flutter's Navigator is perfectly transferable here ... Which is why, I think, it is good that...
@st-pasha can you attach a screen shoot of the example of this PR?