For example: assume I have a classic MVVM app and I've created a #ViewModel. Does this graphic decision tree help me decide how/where to store this VM?
End result - wrap the VM in @EnvironmentObject so I can retrieve it in many Views.
I don't see this graphic decision tree helping with that decision.
There is so much going on in this screen of my current #dotNETMAUI #MacCatalyst app already:
- Loading #SfSymbols via my custom library
- Coloring all icons with the #macOS/#iOS system colors via my custom library
- Extending image control to load a placeholder from SfSymbol
- Custom FramedContentControlWithText
- Entry handler modification to remove the border on Mac
Note: I did not yet wire up a #ViewModel instance.
#dotNET #CASBAN6 #MAUI #MAUIDev #MVVM #XAML #programming #developer #devlife
#dotnetmaui #MacCatalyst #sfsymbols #macos #viewmodel #dotnet #casban6 #maui #mauidev #mvvm #xaml #programming #developer #devlife
OMG, a #ViewModel in #React ?! - Modularizing React Applications with Established UI Patterns - Juntao Qiu - https://martinfowler.com/articles/modularizing-react-apps.html - Interesting read!
Just published "ViewModel: for UI business, not UI operations" 😐. This is related to the developers' misconception and common mistakes they make around ViewModel in #androiddev.
Read👀: https://blog.shreyaspatil.dev/viewmodel-for-ui-business-not-ui-operations
#kotlin #android #viewmodel #androiddevelopment #androiddevelopers #statemanagement
#AndroidDev #kotlin #android #viewmodel #androiddevelopment #androiddevelopers #statemanagement
I still have a big problem with #JetpackCompose:
In one case the #ViewModel is simply not cleared when using JCNavigation. Unfortunately, #Google does not respond to my ticket at all.
My question is whether you can reproduce this and/or whether you have ideas on how to work around it.
Navigating to another screen beforehand, which then clears the VMs, might work, but it would be more bad than good.
#JetpackCompose #viewmodel #google #kotlin