https://github.com/nazmulidris/android_arch_comp
https://github.com/nazmulidris/android_arch_comp
Last synced: 4 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/nazmulidris/android_arch_comp
- Owner: nazmulidris
- License: apache-2.0
- Created: 2017-12-06T23:59:08.000Z (almost 8 years ago)
- Default Branch: main
- Last Pushed: 2020-12-13T04:53:54.000Z (almost 5 years ago)
- Last Synced: 2025-03-24T22:43:20.596Z (7 months ago)
- Language: Java
- Size: 145 KB
- Stars: 6
- Watchers: 3
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# android_arch_comp
This simple Android app showcases how you might use a ViewModel and LiveData in your apps. You can get the article that
accompanies this project on
[medium](https://proandroiddev.com/introduction-to-android-architecture-components-cab33baa65f6) or
[developerlife.com](https://developerlife.com/2017/12/07/introduction-to-android-architecture-components/).
The sample just has 1 Java file — MainActivity.java. This Activity loads its state from a StateViewModel, which contains
two pieces of data.
_Data # 1_ - There’s a UUID String that is generate the first time this StateViewModel is created and this is displayed
in the UI. This String does not change for the lifetime of the Activity. It is stable across configuration changes. So
as you rotate the screen, and the Activity is destroyed and then recreated (but not finished), the same UUID String will
be displayed in the UI. When you finish the Activity by pressing the back button, or by going to the task switcher and
swiping the Activity away, then the ViewModel will be destroyed and onCleared() will be called.
_Data # 2_ - The ViewModel also creates a ScheduledExecutor that runs a simple task every second. This task simply
updates a counter, and it generates a log message (“tick”, or “tock”). This Executor also sets the value of this counter
in a CounterLiveData object. The UI actually subscribes to this LiveData object and when it changes the UI gets updated
with the current count. This too is stable across configuration changes. When the Activity is finally finished, the
onCleared() method actually shuts the executor down. Also, you have to be mindful of which thread the CounterLiveData’s
value is set.
# Change master to main
The
[Internet Engineering Task Force (IETF) points out](https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1)
that "Master-slave is an oppressive metaphor that will and should never become fully detached from history" as well as
"In addition to being inappropriate and arcane, the
[master-slave metaphor](https://github.com/bitkeeper-scm/bitkeeper/blob/master/doc/HOWTO.ask?WT.mc_id=-blog-scottha#L231-L232)
is both technically and historically inaccurate." There's lots of more accurate options depending on context and it
costs me nothing to change my vocabulary, especially if it is one less little speed bump to getting a new person excited
about tech.
You might say, "I'm all for not using master in master-slave technical relationships, but this is clearly an instance of
master-copy, not master-slave"
[but that may not be the case](https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.html). Turns out the
original usage of master in Git very likely came from another version control system (BitKeeper) that explicitly had a
notion of slave branches.
- https://dev.to/lukeocodes/change-git-s-default-branch-from-master-19le
- https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
[#blacklivesmatter](https://blacklivesmatter.com/)