- Notifications
You must be signed in to change notification settings - Fork1
Data of android UI is saved during configuration changes of device using view model of life cycle aware components. Different kind of android life cycle aware components. By using these component an app code becomes robust, testable, and maintainable.
dinkar1708-zz/Lifecycle-Aware-Components
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
ComponentsArchitecture components are a set of Android librariesthat help you structure your app in a way that is robust, testable, and maintainable
INPUT - EXAMPLE OF VIEW MODEL - how does data persist using this view model after configuration changes
The ViewModel class is designed to store and manage UI-related data in a lifecycle conscious way.The ViewModel class allows data to survive configuration changes such as screen rotations.
Two examples has been shown
- Data saved in activity
- Data saved across fragments
view modle data persist after the config changes as well ie. data is not lost after screen rotation
- Create MyViewModel which is data source, after changing in data source however activity get rotates but data is available on activity
public class MyViewModel extends ViewModel { private MutableLiveData<List<User>> users; public LiveData<List<User>> getUsers() { if (users == null) {- Get this data in activity
// Create a ViewModel the first time the system calls an activity's onCreate() method. // Re-created activities receive the same MyViewModel instance created by the first activity. // BELOW FOR JUST FOR DEMO PURPOSE MyViewModel model = ViewModelProviders.of(this).get(MyViewModel.class); // THIS KIND OF OBSERVER CAN BE ADDED ANY WHERE LIKE IN ACTIVITY OR FRAGMENT // ADD OBSERVER IN ON CHANGE /* model.getUsers().observe(this, new Observer<List<User>>() { @Override public void onChanged(@Nullable List<User> users) { } });*/ // SEE LAMDA VARIATIONS OF SAME AS ABOVE model.getUsers().observe(this, users -> { // update UI Log.i(TAG, "onChanged.......users...." + users); });pass data between fragments
- Get data in master ie main fragment
// BELOW TWO ARE SAME LABDA FLAVORS HAS BEEN SHOWN MyViewModel model = ViewModelProviders.of(this).get(MyViewModel.class); /* model.getUsers().observe(getActivity(), new Observer<List<User>>() { @Override public void onChanged(@Nullable List<User> users) { } });*/ model.getUsers().observe(this, users -> { // update UI Log.i(TAG, "onChanged users...." + users); recyclerView.setAdapter(new MyFragmenItemRecyclerViewAdapter(users, mListener)); });- Update data in shared view model after item being selected from master/ main frament
//SET SELECTED VALUE IN SHARED VIEW MODEL // THIS DATA IS PERSIST DURING CONFIGURATION CHANGES AS WELL SharedViewModel model = ViewModelProviders.of(this).get(SharedViewModel.class); model.select(item);- Shared data is available after activity recreated on config changesin this case data has been shown on details framgnet UI
SharedViewModel model = ViewModelProviders.of(getActivity()).get(SharedViewModel.class); model.getSelected().observe(getActivity(), new Observer<User>() { @Override public void onChanged(@Nullable User dummyItem) { Log.i(TAG, "onChanged.... " + dummyItem.toString()); textView.setText(dummyItem.toString()); } });
https://developer.android.com/topic/libraries/architecture/viewmodel.htmlhttps://codelabs.developers.google.com/codelabs/android-lifecycles/#0
About
Data of android UI is saved during configuration changes of device using view model of life cycle aware components. Different kind of android life cycle aware components. By using these component an app code becomes robust, testable, and maintainable.
Topics
Resources
Uh oh!
There was an error while loading.Please reload this page.