I think it's bad design anyway to pass big chunks of data between fragments just bcs you can. Passing data between activities is not a real issue if you have a good design and are using repositories or use cases or whatever you like. I haven't seen this, are you sure your RecyclerView is not in a NestedScrollView, effectively breaking recycling? I use setCustomAnimations() to do horizontal translation animations, though. The slide out animation is still choppy and doesn't work properly for fragments. Not sure about themeing, the toolbar trick tends to be to add one to every screen if design allows it. Theming screens and toggling toolbar settings (although this maybe easily solvable. Simple-stack for me is a unique case because for me (and any app I work on) it's technically first-party support, but I do answer bug reports relatively fast and try to fix them ASAP (if any). Technically, Ian Lake also dislikes fragments, that's why they're re-building them in place to have a completely different lifecycle than they have now, it's just WIP â¡Ä¯air, i don't really like depending on AndroidX stuff either because Google shifts around a lot every year I would consider adding a second Activity that can display whichever Fragment I want on the second panel, but it seems premature to add the second Activity ahead of time if this is not a requirement anywhere on the horizon. So you typically get stuck with adjustResize. I do understand this one: you can set the window soft-key input mode on the Activity, and while there is a setter for programmatically changing it, it actually gets stuck if you try and doesn't work. ![]() This is a very bad faith characterization of Google's guidance toward app architecture, and it makes it really hard to take you seriously. Multiple Activities means you have to serialize things if you want to pass them around, which is limiting and a pain.Ä«ut I think that just because Ian Lake hates activities doesn't mean I should too. I started around the same time, and I don't see any benefit to having multiple Activities if they're all just going to be a different screen. Maybe it's just me because I started Android before fragments and each screen had to be an activity, but I really don't see the benefit in doing single activity for anything bigger than a simple app with few screens. Check the Owl Material design example app to see how this is done. Theming some screens differently to others That might be one instance where multiple activity is better, but I'd argue it's pretty rare, and unless you're explicitly doing that, it's not a reason to stay multi-activity. ![]() ![]() Multi window (using both panels in a split screen scenario) and multi process Keyboard settings are usually per input field, not per screen. It's nice because of the nested
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |