@@JimPekarek hello from 2019, navigation editor not working properly, as always all new features not production-ready - data binding, navigation... Looks like experiment, but not as usable feature.
@@nickolaysavchenko2582 exactly, Android is late to game in on this subject. They're trying to do something to keep up but apparently it blew up in Android core team's face ))
How do I handle CollapsingToolbarLayout for specific Fragment if I have Toolbar that is placed in the Activity? Do I hide the Activity's Toolbar and then handle Fragment's Toolbar separately? How will this affect the up navigation?
It would be great if the activity could own the toolbar and each fragment has the option of implementing a collapsing toolbar. Why do I have to embed a toolbar in a collapsing toolbar layout?
Finally after 10 years they are starting to understand that Android Fragments and UI design are completely shitty... And then they take inspiration from Apple ? Really ? What is going wrong with you Google ?
Every back button or navigation item selection recreates the whole fragment. So what is the use of this if I can't keep the last state of the fragment state.
Will there be a implementation 'android.arch.navigation:navigation-activity:1.0.0-alpha01' that fixes the up and back button handling for activities without the need to switch to this Fragment style?
There is no proper way to update the toolbar based on the navigation destination... Currently It's basically impossible to implement a destination with a SearchView in the toolbar...
With larger applications with many fragments - can you have multiple .xml files for the navigation graph or can you only have one very large graph for the entire project?
Since Google is pushing for a single activity navigation where the activity is just an entry point it makes more sense to have just one huge and highly complex navigation graph for the entire project
Hello, I tried this but I have an issue accessing a nested graph fragment inside another nested graph from the root navhost. (Like from Home to contacts nested graph, contacts being inside the account nested graph). Global action does not work from root only from the account nested graph. And if I extract contacts from the account nested graph it works BUT the "selected" icon in my bottom navigation view will be "home" and not "account" :'(
Can a fragment in the navigation graph have multiple pop-to fragments? Can a navigation graph looks like a net? For example in the case of 06:17, what if an app has multiple entries to the user_profile? Or I'll need to create multiple separate paths?
Prior to migrating to androidx I used the support navigation activity and heavily used activities as opposed to fragments.On migration to androidx i got an error on oncreate.How then do i use the navigation controller on layouts because it only accepts R.id.next and not R.layout.next
How to manage fragment state duting backstack. Like first contains recyclerview and user scroll to end then onitemclick navigate to second screen. now if user back to previous fragment there is not state managed. it is possible or not.if possible how to manage ?
Hello from 2019, navigation editor not working properly, as always all new features not production-ready - data binding, navigation... Looks like experiment, but not as usable feature.
why they copy ios i dont understand and even if they copy they cam make it better but these are only good for fragment transactions Not activity result
Nice! I will be happy to follow and learn from you. :P Oh by the way, is it ok if I can also seek your advice in this open source android app I have posted below? Just need some feedback about it... Just need to search ' *pub:Path Ahead* ' in Google Play (P & A are case sensitive). thanks a-hundred !!
Why? It's good that they stay there. Good for competition. Also, that's nothing. See the monstresity they made here: ua-cam.com/video/jdKUm8tGogw/v-deo.html Really ruined material design. Centered title, ugly FAB in the middle, action item (of profile) on the right... And it's not the only example I've seen there... It has already started. Check the newstand app. Even the search action item on the left...
Because Apple did it right the first time. The only thing I really don't like about the storyboards and xibs, is that you cant use a language like xml to write them without the UI builder.
I waited so much time for something like this. It's a big improvement for the Android developers life! Thank you!
Now the iOS developers that work near me can't mock me anymore for not having a storyboard :D
And we can continue to mock them every time they run into merge conflicts with their storyboards. It's a win-win!
@@JimPekarek hello from 2019, navigation editor not working properly, as always all new features not production-ready - data binding, navigation... Looks like experiment, but not as usable feature.
@@nickolaysavchenko2582 exactly, Android is late to game in on this subject. They're trying to do something to keep up but apparently it blew up in Android core team's face ))
D
D
@@JimPekarek dndb
D bdv
Dd
B
Dbd
Bd
B
DVD dad
How do I handle CollapsingToolbarLayout for specific Fragment if I have Toolbar that is placed in the Activity?
Do I hide the Activity's Toolbar and then handle Fragment's Toolbar separately? How will this affect the up navigation?
It would be great if the activity could own the toolbar and each fragment has the option of implementing a collapsing toolbar. Why do I have to embed a toolbar in a collapsing toolbar layout?
See other talk ua-cam.com/video/WVPH48lUzGY/v-deo.html
Finally after 10 years they are starting to understand that Android Fragments and UI design are completely shitty... And then they take inspiration from Apple ? Really ? What is going wrong with you Google ?
Every back button or navigation item selection recreates the whole fragment. So what is the use of this if I can't keep the last state of the fragment state.
State of the fragment should be stored and restored in ViewModel, as Fragments are volatile
Will there be a
implementation 'android.arch.navigation:navigation-activity:1.0.0-alpha01'
that fixes the up and back button handling for activities without the need to switch to this Fragment style?
There is no proper way to update the toolbar based on the navigation destination... Currently It's basically impossible to implement a destination with a SearchView in the toolbar...
how to prevent recreating the whole fragment everytime I select a bottomnav item
Why call it NavHost instead of NavigationHost? just introduces unnecessary inconsistency
How to prevent fragment recreate during pop behavior ? Like Second fragment to first fragment .
no solution yet?
Navigation component crashes.
java.lang.IllegalArgumentException: navigation destination
😫😫😫😫
I wish they would of covered the tablet example or an example of when you have multiple fragments on the screen...
With larger applications with many fragments - can you have multiple .xml files for the navigation graph or can you only have one very large graph for the entire project?
Since Google is pushing for a single activity navigation where the activity is just an entry point it makes more sense to have just one huge and highly complex navigation graph for the entire project
What's the software they are using for demo @ 5:28?
is there any workaround given by navigation component to handle multiple backstack in android as specially in java ?
Nice idea but what should we do with tablet navigation?
Hello, I tried this but I have an issue accessing a nested graph fragment inside another nested graph from the root navhost. (Like from Home to contacts nested graph, contacts being inside the account nested graph). Global action does not work from root only from the account nested graph. And if I extract contacts from the account nested graph it works BUT the "selected" icon in my bottom navigation view will be "home" and not "account" :'(
it's just like iOS. Thanks for doing this.
is it just for Fragments?
Does it working with custom controller instead of fragment (for example conductor controllers)?
yes, you can create your own subclass of Navigator to handle custom destination types
Can a fragment in the navigation graph have multiple pop-to fragments? Can a navigation graph looks like a net?
For example in the case of 06:17, what if an app has multiple entries to the user_profile? Or I'll need to create multiple separate paths?
How I do handle shared elements on transitions from FragmentA to FragmentB? :O
Shared Element support is coming soon!
Prior to migrating to androidx I used the support navigation activity and heavily used activities as opposed to fragments.On migration to androidx i got an error on oncreate.How then do i use the navigation controller on layouts because it only accepts R.id.next and not R.layout.next
How do I add business logic to the navigation? You showed static navigation, what about dynamic?
check the documentation, there's a section on conditional navigation
How to manage fragment state duting backstack. Like first contains recyclerview and user scroll to end then onitemclick navigate to second screen. now if user back to previous fragment there is not state managed. it is possible or not.if possible how to manage ?
All the pain I had to suffer over the last years now seam so unnecessary
That really good improvement
What about Instant Apps? How is it supposed to work with them?
You can't use findViewById in a fragment... getview()?.findViewById is correct ?
Can we use Android Jetpack on an Android 7 targeted devices?
Hello from 2019, navigation editor not working properly, as always all new features not production-ready - data binding, navigation... Looks like experiment, but not as usable feature.
How do i get this presentation?
8:06 what is the role of the Activity? Yup, it is *not just "a screen"* :D
What is Steve Merchant is doing there?
HOW TO MAKE A DEEP_LINK OPEN A FRAGMENT WITHOUT BACKSTACK ?
Are they doing all navigation work in android studio? please reply me
yes
Patching, Patching and Patching, what is the next? what is the end?
There's no end in technology. It'll always be evolving.
Added depdencies, still unable find this "navigation editor". Anyone had any luck with this ?
You have to use Android Studio 3.2 canary 14 or 15
why they copy ios i dont understand and even if they copy they cam make it better but these are only good for fragment transactions Not activity result
thank you very much
Welcome...
Nice! I will be happy to follow and learn from you. :P
Oh by the way, is it ok if I can also seek your advice in this open source android app I have posted below? Just need some feedback about it...
Just need to search ' *pub:Path Ahead* ' in Google Play (P & A are case sensitive).
thanks a-hundred !!
Awesome
Why do all these new things look like iOS?
Exactly what i was asking...
Maybe to attract iOS developers?
Only , thing. ANDROID IS BETTER LOL
Why? It's good that they stay there. Good for competition.
Also, that's nothing. See the monstresity they made here:
ua-cam.com/video/jdKUm8tGogw/v-deo.html
Really ruined material design. Centered title, ugly FAB in the middle, action item (of profile) on the right...
And it's not the only example I've seen there...
It has already started. Check the newstand app. Even the search action item on the left...
Because Apple did it right the first time. The only thing I really don't like about the storyboards and xibs, is that you cant use a language like xml to write them without the UI builder.
Guys re-invented Cicerone library from terrakok
Cicerone is used in one of my work projects, and it's not that convenient and safe, especially when talking about arguments.
And Cicerone doesn't have that beautiful navigation graph editor, plus it demands you to write more boilerplate code instead of removing it of.
put speed to at least 2x
I need more than that via JS hack
x)
eklasa