Menu
I'm with some doubts regarding the state save using MVP on Android. I defined my fragments/activities as views and then implemented the corresponding presenters.
My example is simple:
I have a activity with some checkboxes and spinners. If the activity is destroyed by the Android system and then recreated, where should I save these spinners and checkboxes states? On the view? On the presenter?
If on the view, should I have the restore logic on the view or on the presenter?
Thank you!
869
The savedInstanceState is a reference to a Bundle object that is passed into the onCreate method of every Android Activity. Activities have the ability, under special circumstances, to restore themselves to a previous state using the data stored in this bundle.
Example of MVP Architecture The role of the Presenter class is to keep the business logic of the application away from the activity. Below is the complete step-by-step implementation of this android application. Note that we are going to implement the project using both Java and Kotlin language.
In the case of MVP, is the model who is in charge of keeping the state of the view.
For example, in you model you have a Post entity with an Array of Categories. In your view you have a Checkbox for each category, and in each checked/unchecked action you add/remove objects from the Post's Category array.
Once the Activity is restored, the View should ask for the Post's Category array in order to find out which are selected and which aren't, so it can set the proper checked/unchecked attribute.
Here's a really good post about it: http://fernandocejas.com/2014/09/03/architecting-android-the-clean-way/
173
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
