Jetpack-Lifecycle
相关课程：
官方文档地址：
LifecycleOwner
public interface LifecycleOwner {
/**
* Returns the Lifecycle of the provider.
*
* @return The lifecycle of the provider.
*/
@NonNull
Lifecycle getLifecycle();
}
LifecycleOwner是一个接口，我们的View层实现了此接口，也就是我们的Activity、Fragment实现了此接口。
这样子，我们的View层就具备了getLifecycle的能力了。
我们可以稍微看一下它的实现
比如说FragmentActivity里的
@NonNull
@Override
public Lifecycle getLifecycle() {
// Instead of directly using the Activity's Lifecycle, we
// use a LifecycleRegistry that is nested exactly outside of
// when Fragments get their lifecycle changed
// TODO(b/127528777) Drive Fragment Lifecycle with LifecycleObserver
return mFragmentLifecycleRegistry;
}
返回的是这个
mFragmentLifecycleRegistry
这个玩意是这个
/**
* A {@link Lifecycle} that is exactly nested outside of when the FragmentController
* has its state changed, providing the proper nesting of Lifecycle callbacks
* <p>
* TODO(b/127528777) Drive Fragment Lifecycle with LifecycleObserver
*/
final LifecycleRegistry mFragmentLifecycleRegistry = new LifecycleRegistry(this);
public class LifecycleRegistry extends Lifecycle
LifecycleRegistry 继承自 Lifecycle
也就是这个玩意就是Lifecycle的子类。
okay到此。
Lifecycle和LifecycleRegistry
LifecycleRegistry是Lifecycle的子类
这个LifecycleRegistry关注点两个就好。一个是当前的状态，一个是它收藏观察者。LifecycleRegistry是一个中间商。桥接着View层和需要知道View生命周期的模块。
接下来，我们看看基本的使用吧！
基本使用
通过LifecycleOwner来获取到Lifecycler，View层已经实现了LifecyclerOnwer接口。比如说AppCompatActivity、Fragment已经实现了LifecycleOwner接口。
在activity中，或者fragment中
直接
this.lifecycle
kotlin的写法，如果是java get即可。
拿到以后，往里面添加监听
this.lifecycle.addObserver()
一般来说，传接口都是要实现xxx接口的
这个是我们addObserver的方法
void addObserver(@NonNull LifecycleObserver observer)
也就是说，你需要传一个实现了LifecycleObserver 的类，或者实现了LifecycleObserver的子类才可以。
比如说我们的Presenter需要知道View层的生命周期变化。
我们把Owner传给Presneter
MusicPresenter(owner: LifecycleOwner)
初始化的时候，添加观察者
init {
owner.lifecycle.addObserver(viewLifeImpl)
}
这个观察者的实现类
private val viewLifeImpl by lazy {
ViewLifeImpl()
}
LifecycleEventObserver实现类，LifecycleEventObserver是LifecycleObserver的子类
inner class ViewLifeImpl : LifecycleEventObserver {
/**
* 被动通知View层的生命周期变化
*/
override fun onStateChanged(source: LifecycleOwner, event: Lifecycle.Event) {
when (event) {
Lifecycle.Event.ON_START -> {
//监听GPS信号变化
println("监听GPS信号变化")
//开始监听网络变化
}
Lifecycle.Event.ON_PAUSE -> {
//停止GPS信号变化监听
println("停止GPS信号变化监听")
//停止网络状态变化更新
}
else -> {
}
}
}
}
当View层的生命周期发生变化的时候，就会通知到我们添加的监听了。
也就是会通知到onStateChange里头。
另外一种方式则是通过注解的方式。
同样也是实现LifecycleObserver接口
里面的方法添加注解，比如说：
inner class ValueObserverWrapper(private val valueObserver: (T?) -> Unit) :
LifecycleObserver {
@OnLifecycleEvent(Lifecycle.Event.ON_DESTROY)
fun removeValueObserver() {
println("removeValueObserver...")
//当监听到当前的View，生命周期为Destroy的时候，就把LifecycleProvider从集合中删除
viewLifecycleProviders.remove(valueObserver)
}
@OnLifecycleEvent(Lifecycle.Event.ON_STOP)
fun onStop() {
}
@OnLifecycleEvent(Lifecycle.Event.ON_ANY)
fun onAny() {
}
}
然后创建这个类，添加到Lifecycle里
以上两种方式，是被动的通知。也就是生命周期发生变化的时候，会通知你View层的生命周期发生变化了。
其实除了被动通知以外，还可以主动获取。
我们拿到Lifecycle以后，直接获取currentState，就知道当前View是一个什么状态了。
lifecycle.currentState
如果是java的话，就get
PS：注意一下，ViewModel层/Presenter层最好不要依赖owner，也就是View层。顶多拿着Lifecycler这个中间商。
源码分析
源码分析我们分为：
- View层生命周期变化如何通知Lifecycle
- Lifecycle如何通知观察者View层生命周期变化
一般来说，我们阅读源码的时候，要带着问题去阅读。这样子的话有一个主线，再结合技巧，调试就很容易走通了。
我们分开两部分来阅读Lifecycle的源码，一部分是Lifecycle是如何知道View层的生命周期变化的。一部分是
View层生命周期变化如何通知Lifecycle
前面开始，我们知道Lifecycler是由View层创建的，也就是View层持有Lifecycler。
如果View层要通知Lifecycle生命周期那还不简单，直接调用一个方法就可以了。
创建
final LifecycleRegistry mFragmentLifecycleRegistry = new LifecycleRegistry(this);
哪个呢？
在View走onCreate方法的时候
mFragmentLifecycleRegistry.handleLifecycleEvent(Lifecycle.Event.ON_CREATE);
比如说Destroy的时候
@Override
protected void onDestroy() {
super.onDestroy();
...
mFragmentLifecycleRegistry.handleLifecycleEvent(Lifecycle.Event.ON_DESTROY);
}
到这里，就通知到了Lifecycle生命周期发生变化了。
我们看看这个方法
public void handleLifecycleEvent(@NonNull Lifecycle.Event event) {
State next = getStateAfter(event);
moveToState(next);
}
这里面首先是把事件转成State
大家可以看看这张转换图：
代码如下：
static State getStateAfter(Event event) {
switch (event) {
case ON_CREATE:
case ON_STOP:
return CREATED;
case ON_START:
case ON_PAUSE:
return STARTED;
case ON_RESUME:
return RESUMED;
case ON_DESTROY:
return DESTROYED;
case ON_ANY:
break;
}
throw new IllegalArgumentException("Unexpected event value " + event);
}
moveToState(next);
这行代码很简单，理解为赋值和通知即可。
把当前的next，也就是新的state赋值给mState，也就当前的State。接着就是通知了。
通知的代码我们接下来分析，也就是我们的Lifecycle是如何通知观察者View层状态更新的。
Lifecycle如何通知观察者View层生命周期变化
我们是重注册观察者开始向Lifecycle挂上关系的。所以我们可以从这里入手。
owner.lifecycle.addObserver(viewLifeImpl)
这就是addObserver方法
@Override
public void addObserver(@NonNull LifecycleObserver observer) {
State initialState = mState == DESTROYED ? DESTROYED : INITIALIZED;
ObserverWithState statefulObserver = new ObserverWithState(observer, initialState);
ObserverWithState previous = mObserverMap.putIfAbsent(observer, statefulObserver);
if (previous != null) {
return;
}
LifecycleOwner lifecycleOwner = mLifecycleOwner.get();
if (lifecycleOwner == null) {
// it is null we should be destroyed. Fallback quickly
return;
}
boolean isReentrance = mAddingObserverCounter != 0 || mHandlingEvent;
State targetState = calculateTargetState(observer);
mAddingObserverCounter++;
while ((statefulObserver.mState.compareTo(targetState) < 0
&& mObserverMap.contains(observer))) {
pushParentState(statefulObserver.mState);
statefulObserver.dispatchEvent(lifecycleOwner, upEvent(statefulObserver.mState));
popParentState();
// mState / subling may have been changed recalculate
targetState = calculateTargetState(observer);
}
if (!isReentrance) {
// we do sync only on the top level.
sync();
}
mAddingObserverCounter--;
}
主要是看到它被添加到集合里就行了
ObserverWithState previous = mObserverMap.putIfAbsent(observer, statefulObserver);
添加到mObserverMap了
接着，我们回去看生命周期发生变化的地方
public void handleLifecycleEvent(@NonNull Lifecycle.Event event) {
State next = getStateAfter(event);
moveToState(next);
}
这是moveToState方法
private void moveToState(State next) {
if (mState == next) {
return;
}
mState = next;
if (mHandlingEvent || mAddingObserverCounter != 0) {
mNewEventOccurred = true;
// we will figure out what to do on upper level.
return;
}
mHandlingEvent = true;
sync();
mHandlingEvent = false;
}
这里其实就是分发了
// happens only on the top of stack (never in reentrance),
// so it doesn't have to take in account parents
private void sync() {
LifecycleOwner lifecycleOwner = mLifecycleOwner.get();
if (lifecycleOwner == null) {
throw new IllegalStateException("LifecycleOwner of this LifecycleRegistry is already"
+ "garbage collected. It is too late to change lifecycle state.");
}
while (!isSynced()) {
mNewEventOccurred = false;
// no need to check eldest for nullability, because isSynced does it for us.
if (mState.compareTo(mObserverMap.eldest().getValue().mState) < 0) {
backwardPass(lifecycleOwner);
}
Entry<LifecycleObserver, ObserverWithState> newest = mObserverMap.newest();
if (!mNewEventOccurred && newest != null
&& mState.compareTo(newest.getValue().mState) > 0) {
forwardPass(lifecycleOwner);
}
}
mNewEventOccurred = false;
}
再到这里的遍历
private void forwardPass(LifecycleOwner lifecycleOwner) {
Iterator<Entry<LifecycleObserver, ObserverWithState>> ascendingIterator =
mObserverMap.iteratorWithAdditions();
while (ascendingIterator.hasNext() && !mNewEventOccurred) {
Entry<LifecycleObserver, ObserverWithState> entry = ascendingIterator.next();
ObserverWithState observer = entry.getValue();
while ((observer.mState.compareTo(mState) < 0 && !mNewEventOccurred
&& mObserverMap.contains(entry.getKey()))) {
pushParentState(observer.mState);
observer.dispatchEvent(lifecycleOwner, upEvent(observer.mState));
popParentState();
}
}
}
private void backwardPass(LifecycleOwner lifecycleOwner) {
Iterator<Entry<LifecycleObserver, ObserverWithState>> descendingIterator =
mObserverMap.descendingIterator();
while (descendingIterator.hasNext() && !mNewEventOccurred) {
Entry<LifecycleObserver, ObserverWithState> entry = descendingIterator.next();
ObserverWithState observer = entry.getValue();
while ((observer.mState.compareTo(mState) > 0 && !mNewEventOccurred
&& mObserverMap.contains(entry.getKey()))) {
Event event = downEvent(observer.mState);
pushParentState(getStateAfter(event));
observer.dispatchEvent(lifecycleOwner, event);
popParentState();
}
}
}
到了这里，同学们是否对这个方法很熟悉呢？
void dispatchEvent(LifecycleOwner owner, Event event) {
State newState = getStateAfter(event);
mState = min(mState, newState);
mLifecycleObserver.onStateChanged(owner, event);
mState = newState;
}
onStateChange()方法
mLifecycleObserver.onStateChanged(owner, event);
走到这里，就会通知到我们的实现代码了
inner class ViewLifeImpl : LifecycleEventObserver {
/**
* 被动通知View层的生命周期变化
*/
override fun onStateChanged(source: LifecycleOwner, event: Lifecycle.Event) {
when (event) {
Lifecycle.Event.ON_START -> {
//监听GPS信号变化
println("监听GPS信号变化")
//开始监听网络变化
}
Lifecycle.Event.ON_PAUSE -> {
//停止GPS信号变化监听
println("停止GPS信号变化监听")
//停止网络状态变化更新
}
else -> {
}
}
}
}
因为mLifecycleObserver就是我们传进来保存到集合里的实例。
另外一种注解的方式源码分析，请看视频课程吧。
