m-lamonaca/dev-notes
1
0
Fork 0
mirror of https://github.com/m-lamonaca/dev-notes.git synced 2025-06-08 02:37:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Use local images instead or remote ones (#4)

Browse source
This commit is contained in:
Marcello 2021-07-01 20:37:27 +02:00 • committed by GitHub
parent 68723844c3
commit 28ec06cb95
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
36 changed files with 21 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Android/Activity.kt.md
View file

@ -12,7 +12,7 @@ Log.c("tag", "logValue") //critical log
## Activity Life Cycle
![Life Cycle](https://developer.android.com/images/activity_lifecycle.png)
![Life Cycle](../.images/android_activity-lifecycle.png)
```kotlin
package com.its.<appname>

4
Android/Fragment.md
View file

@ -5,11 +5,11 @@
A **Fragment** represents a behavior or a portion of user interface in a `FragmentActivity`. It's possible to combine multiple fragments in a single activity to build a multi-pane UI and reuse a fragment in multiple activities.
Think of a fragment as a *modular section of an activity*, which has its *own* lifecycle, receives its *own* input events, and which you can add or remove while the activity is running (sort of like a "sub activity" that you can reuse in different activities).
![Fragment](https://developer.android.com/images/fundamentals/fragments.png)
![Fragment](../.images/android_fragments.png)
A fragment must always be hosted in an activity and the fragment's lifecycle is *directly affected* by the host activity's lifecycle.
![Fragment Lifecycle](https://developer.android.com/images/fragment_lifecycle.png)
![Fragment Lifecycle](../.images/android_fragment-lifecycle.png)
## Minimal Fragment Functions