Vahalaru03/16/2021, 3:24 AM
theapache6403/16/2021, 3:29 AM
. The navigation between these screens are done by @Arkadii Ivanov’s Decomposer library.
is a simple class maintained to keep the structure android-way. Here's the
class : https://github.com/theapache64/cyclone/blob/master/core/src/main/kotlin/com/theapache64/cyclone/core/Activity.kt
Vahalaru03/16/2021, 4:08 AM
Zach Klippenstein (he/him) [MOD]03/16/2021, 5:02 AM
can certainly be used for basic navigation transition animations, which is I think what you’re asking. Just be aware that it doesn’t actually do everything you’d expect from a navigation solution - consider a main/detail pair of screens. The main screen has a list of items, tapping on an item navigates to a detail screen. If you use
for the transition, then if you’ve scrolled the list, when you navigate back, I believe the scroll position will be lost. Probably the Decomposer library handles this case correctly, as would fragments, Jetpack Navigation, compose-router, and other real navigation libraries.
Why is it that the people that create these kinds things always focus on the "advanced" stuff or the "oh that'd be cool" but don't think about the easy basic things?What kind of focus would you like to see? Just better docs/more examples?
Vahalaru03/16/2021, 8:36 AM
Zach Klippenstein (he/him) [MOD]03/16/2021, 5:12 PM