摘要:將的生命周期函數對應成,生命周期改變,會造成改變,而變化將觸發事件,從而被接收。與一樣,都是通過注冊來監聽的生命周期回調,來給每個添加的。
版權聲明:本文已授權微信公眾號:Android必修課,轉載請申明出處眾所周知,Android凡是需要展示給用戶看的,都包含著生命周期這個概念,例如Activity、Fragment、View等都與生命周期息息相關,在生命周期函數里,它們各自完成創建、渲染、銷毀等工作。
但是一旦我們往某個生命周期函數中,加入我們自己的邏輯,若是處理不當,就有可能破壞其原有的生命周期,造成內存泄漏甚至應用崩潰等問題。
Android官方似乎也注意到了這一點,因此在Google IO 2018大會上,推出了Android Jetpack開發工具包,其中就包含了一個非常重要的生命周期組件,即本篇的主角-Lifecycle
本文篇幅較長,請大家耐心閱讀。
Lifecycle是什么?
Lifecycle是一個生命周期感知組件,一般用來響應Activity、Fragment等組件的生命周期變化,并將變化通知到已注冊的觀察者。有助于更好地組織代碼,讓代碼邏輯符合生命周期規范,減少內存泄漏,增強穩定性。
Lifecycle已經納入新版本的AppCompatActivity和Fragment中了,并且Lifecycle還是Android Jetpack中其他兩個組件LiveData和ViewModel的基礎,意味著這個庫可能將持續伴隨著我們后續的開發,因此有什么理由不學習一番呢?
按照國際規范,我們先講使用,后解析源碼。
一、使用 1.添加依賴:在app或者module目錄下的build.gradle中,添加依賴:
dependencies { ...... implementation "android.arch.lifecycle:runtime:1.1.1" implementation "android.arch.lifecycle:extensions:1.1.1" // 如果你使用java8開發,可以添加這個依賴,里面只有一個類 implementation "android.arch.lifecycle:common-java8:1.1.1" }2.實現LifecycleObserver接口
public class Java7Observer implements LifecycleObserver { private static final String TAG = Java7Observer.class.getSimpleName(); @OnLifecycleEvent(Lifecycle.Event.ON_CREATE) public void onCreate() { Log.d(TAG, "onCreate"); } @OnLifecycleEvent(Lifecycle.Event.ON_START) public void onStart() { Log.d(TAG, "onStart"); } @OnLifecycleEvent(Lifecycle.Event.ON_RESUME) public void onResume() { Log.d(TAG, "onResume"); } @OnLifecycleEvent(Lifecycle.Event.ON_PAUSE) public void onPause() { Log.d(TAG, "onPause"); } @OnLifecycleEvent(Lifecycle.Event.ON_STOP) public void onStop() { Log.d(TAG, "onStop"); } @OnLifecycleEvent(Lifecycle.Event.ON_DESTROY) public void onDestroy() { Log.d(TAG, "onDestroy"); } }
首先,我們需要實現LifecycleObserver這個接口,然后在我們的方法上加上@OnLifecycleEvent注解,注解值表示該方法對應生命周期的哪個函數,這里我們把所有生命周期函數都加上了,并簡單地打印了一句Log。
我想有人會問,為什么這個class要命名Java7Observer ? 沒錯,因為Java8中,官方推薦用另外一種方式:
public class Java8Observer implements DefaultLifecycleObserver { private static final String TAG = Java8Observer.class.getSimpleName(); @Override public void onCreate(@NonNull LifecycleOwner owner) { Log.d(TAG, "onCreate"); } @Override public void onStart(@NonNull LifecycleOwner owner) { Log.d(TAG, "onStart"); } @Override public void onResume(@NonNull LifecycleOwner owner) { Log.d(TAG, "onResume"); } @Override public void onPause(@NonNull LifecycleOwner owner) { Log.d(TAG, "onPause"); } @Override public void onStop(@NonNull LifecycleOwner owner) { Log.d(TAG, "onStop"); } @Override public void onDestroy(@NonNull LifecycleOwner owner) { Log.d(TAG, "onDestroy"); } }
理由很簡單,Lifecycle源碼中有一段注釋:
/* ..... ** If you use Java 7 Language, Lifecycle events are observed using annotations. * Once Java 8 Language becomes mainstream on Android, annotations will be deprecated, so between * {@link DefaultLifecycleObserver} and annotations, * you must always prefer {@code DefaultLifecycleObserver}. *
* ...... */
翻譯一下就是:“如果你丫的用的是java7,那你就用注解唄,但是我告訴你,一旦java8上位了,你那些注解就過時了,我勸你最好用DefaultLifecycleObserver”
3.將LifecycleObserver添加到Lifecycle的觀察者列表如果你使用新版本的AppcompatActivity(>26.1.0),可以這么寫:
public class MainActivity extends AppCompatActivity { @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); // 直接調用getLifecycle(),添加Observer getLifecycle().addObserver(new Java7Observer()); getLifecycle().addObserver(new Java8Observer()); } }
如果你的AppCompatActivity沒有更新到最新,那么你需要自實現LifecycleOwner接口,并在Activity生命周期函數中分發事件
public class MainActivity extends Activity implements LifecycleOwner { private LifecycleRegistry mLifecycleRegistry; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); mLifecycleRegistry = new LifecycleRegistry(this); mLifecycleRegistry.handleLifecycleEvent(Lifecycle.Event.ON_CREATE); mLifecycleRegistry.addObserver(new TestObserver()); } @NonNull @Override public Lifecycle getLifecycle() { return mLifecycleRegistry; } @Override public void onStart() { super.onStart(); mLifecycleRegistry.handleLifecycleEvent(Lifecycle.Event.ON_START); } @Override public void onResume() { super.onResume(); mLifecycleRegistry.handleLifecycleEvent(Lifecycle.Event.ON_RESUME); } @Override public void onPause() { mLifecycleRegistry.handleLifecycleEvent(Lifecycle.Event.ON_PAUSE); super.onPause(); } @Override public void onStop() { mLifecycleRegistry.handleLifecycleEvent(Lifecycle.Event.ON_STOP); super.onStop(); } @Override public void onDestroy() { mLifecycleRegistry.handleLifecycleEvent(Lifecycle.Event.ON_DESTROY); super.onDestroy(); } }
ok,完事兒了,咱們跑起來看一哈,已經成功和生命周期關聯上了。
能舉個熟悉點的例子嗎?MVP想必大家都用過,或者聽說過,View層通過Presenter層和Model層進行通信,因此Presenter層如果做了什么超出View生命周期的事,又沒有及時釋放內存,就會造成內存泄漏。
所以,原來的Presenter,為了響應生命周期,我們可能會這么寫:
先定義所有的生命周期函數
public class MainPresenter { public void onCreate() { } public void onStart() { } public void onResume() { } public void onPause() { } public void onStop() { } public void onDestroy() { } }
然后再與Activity生命周期一一綁定,如果有多個類似的需要響應生命周期的類,Activity的生命周期函數就會變得非常臃腫
public class MainActivity extends AppCompatActivity { private MainPresenter mPresenter; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); mPresenter = new MainPresenter(); mPresenter.onCreate(); } @Override protected void onResume() { super.onResume(); mPresenter.onCreate(); // VideoPlayer.onResume(); // ... } @Override protected void onStart() { super.onStart(); mPresenter.onStart(); // VideoPlayer.onStart(); // ... } @Override protected void onPause() { super.onPause(); mPresenter.onPause(); // VideoPlayer.onPause(); // ... } @Override protected void onStop() { super.onStop(); mPresenter.onStop(); // VideoPlayer.onStop(); // ... } @Override protected void onDestroy() { super.onDestroy(); mPresenter.onDestroy(); // VideoPlayer.onDestroy(); // ... } }
因此,Lifecycle就是為了解決這個痛點,將生命周期的響應分發到各個觀察者中去,我們只需要在Activity中調用一行代碼:
getLifecycle().addObserver(mPresenter);
代碼量蹭蹭就下來了。諸如音視頻播放、圖片加載,這些吃內存大戶,都應該響應生命周期,及時釋放內存,否則很可能就會造成OOM。
二、知其然,還得知其所以然在項目中引入一個庫,卻不懂是怎么實現的,是一件非常危險的行為,因此我們不僅要學會怎么用,還得知道其中的原理。
先看一張官方的圖:
可以看到兩個很顯眼的單詞:State和Event,這也是貫穿整個Lifecycle的兩個概念:狀態和事件。
Lifecycle將Activity的生命周期函數對應成State,生命周期改變,會造成State改變,而State變化將觸發Event事件,從而被LifecycleObser接收。
State:狀態,是Lifecycle中對應Activity生命周期的一種狀態標識,從圖中可以看到,它有INITIALIZED、DESTROYED、CREATED、STARTED、RESUMED這5中狀態。
INITIALIZED:對應Activity的onCreate之前的生命周期
DESTROYED:對應Activity的onDestroy
CREATED:對應Activity的onCreate到onStop之間的生命周期
STARTED:對應Activity的onStart到onPause之間的生命周期
RESUMED:對應Activity的onResume
Event:事件,當State發生變化時,Lifecycle會向已注冊的LifecycleObserver發送事件,例如:當State從INITIALIZED變化到CREATED時,就會發出ON_CREATE事件。
因此,弄懂Lifecycle,其實也就是需要弄懂兩件事:
State是如何與Activity/Fragment的生命周期綁定的?
Event事件是如何分發到LifecycleObserver的?
ok,帶著這兩個問題,我們開始看源碼:
1.從AppCompatActivity的getLifecycle()開始直接ctrl+左鍵跟進源碼,由于AppCompatActivity繼承自SupportActivity,我們發現,AppCompatActivity.getLifecycle(),最終定位在了SupportActivity.getLifecycle()方法中
public class SupportActivity extends Activity implements LifecycleOwner { ...... private LifecycleRegistry mLifecycleRegistry = new LifecycleRegistry(this); @Override protected void onCreate(@Nullable Bundle savedInstanceState) { super.onCreate(savedInstanceState); ReportFragment.injectIfNeededIn(this); } @Override public Lifecycle getLifecycle() { return mLifecycleRegistry; } ...... }
不難看到:
最終getLifecycle()返回的是一個LifecycleRegistry 對象,所以所有對LifecycleObserver的操作都是由LifecycleRegistry 完成的
在onCreate()方法中,我們還看到了一個ReportFragment.injectIfNeededIn(this),先做個標記,后面再說
2.LifecycleRegistry字面意思:生命周期登記處
這個類是Lifecycle中最重要的一個類,它是Lifecycle的子類,起著添加觀察者,響應生命周期事件,分發生命周期事件的作用
public class LifecycleRegistry extends Lifecycle { // LifecycleObserver Map,每一個Observer都有一個State private FastSafeIterableMapmObserverMap = new FastSafeIterableMap<>(); // 當前的狀態 private State mState; // 生命周期擁有者,上述的SupportActivity繼承了LifecycleOwner private final WeakReference mLifecycleOwner; public LifecycleRegistry(@NonNull LifecycleOwner provider) { mLifecycleOwner = new WeakReference<>(provider); mState = INITIALIZED; } /** * 添加LifecycleObserver觀察者,并將之前的狀態分發給這個Observer,例如我們在onResume之后注冊這個Observer, * 該Observer依然能收到ON_CREATE事件 */ public void addObserver(@NonNull LifecycleObserver observer) { State initialState = mState == DESTROYED ? DESTROYED : INITIALIZED; ObserverWithState statefulObserver = new ObserverWithState(observer, initialState); ObserverWithState previous = mObserverMap.putIfAbsent(observer, statefulObserver); ...... // 例如:Observer初始狀態是INITIALIZED,當前狀態是RESUMED,需要將INITIALIZED到RESUMED之間的 // 所有事件分發給Observer // while ((statefulObserver.mState.compareTo(targetState) < 0 && mObserverMap.contains(observer))) { pushParentState(statefulObserver.mState); statefulObserver.dispatchEvent(lifecycleOwner, upEvent(statefulObserver.mState)); popParentState(); targetState = calculateTargetState(observer); } ...... } /** * 處理生命周期事件 */ public void handleLifecycleEvent(@NonNull Lifecycle.Event event) { State next = getStateAfter(event); moveToState(next); } /** * 改變狀態 */ private void moveToState(State next) { if (mState == next) { return; } mState = next; ...... sync(); ...... } /** * 同步Observer狀態,并分發事件 */ private void sync() { LifecycleOwner lfecycleOwner = mLifecycleOwner.get(); if (lifecycleOwner == null) { Log.w(LOG_TAG, "LifecycleOwner is garbage collected, you shouldn"t try dispatch " + "new events from it."); return; } while (!isSynced()) { mNewEventOccurred = false; // State中,狀態值是從DESTROYED-INITIALIZED-CREATED-STARTED-RESUMED增大 // 如果當前狀態值 < Observer狀態值,需要通知Observer減小狀態值,直到等于當前狀態值 if (mState.compareTo(mObserverMap.eldest().getValue().mState) < 0) { backwardPass(lifecycleOwner); } Entry newest = mObserverMap.newest(); // 如果當前狀態值 > Observer狀態值,需要通知Observer增大狀態值,直到等于當前狀態值 if (!mNewEventOccurred && newest != null && mState.compareTo(newest.getValue().mState) > 0) { forwardPass(lifecycleOwner); } } mNewEventOccurred = false; } /** * 向前傳遞事件,對應圖中的INITIALIZED -> RESUMED * 增加Observer的狀態值,直到狀態值等于當前狀態值 */ private void forwardPass(LifecycleOwner lifecycleOwner) { Iterator > ascendingIterator = mObserverMap.iteratorWithAdditions(); while (ascendingIterator.hasNext() && !mNewEventOccurred) { Entry 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(); } } } /** * 向后傳遞事件,對應圖中的RESUMED -> DESTROYED * 減小Observer的狀態值,直到狀態值等于當前狀態值 */ private void backwardPass(LifecycleOwner lifecycleOwner) { Iterator > descendingIterator = mObserverMap.descendingIterator(); while (descendingIterator.hasNext() && !mNewEventOccurred) { Entry 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(); } } } }
我們再看看新版AppCompatActivity是如何將事件分發給LifecycleRegistry的,還記得SupportActivity中有這么一段邏輯嗎:
public class SupportActivity extends Activity implements LifecycleOwner { @Override protected void onCreate(@Nullable Bundle savedInstanceState) { super.onCreate(savedInstanceState); ReportFragment.injectIfNeededIn(this); } }
我們看看ReportFragment是什么
3.ReportFragmentpublic class ReportFragment extends Fragment { public static void injectIfNeededIn(Activity activity) { android.app.FragmentManager manager = activity.getFragmentManager(); if (manager.findFragmentByTag(REPORT_FRAGMENT_TAG) == null) { manager.beginTransaction().add(new ReportFragment(), REPORT_FRAGMENT_TAG).commit(); manager.executePendingTransactions(); } } @Override public void onStart() { super.onStart(); dispatchStart(mProcessListener); dispatch(Lifecycle.Event.ON_START); } // ...... 其他生命周期也是同樣調用了dispatch(Lifecycle.Event.xxx)分發事件 @Override public void onPause() { super.onPause(); dispatch(Lifecycle.Event.ON_PAUSE); } private void dispatch(Lifecycle.Event event) { Activity activity = getActivity(); if (activity instanceof LifecycleRegistryOwner) { ((LifecycleRegistryOwner) activity).getLifecycle().handleLifecycleEvent(event); return; } if (activity instanceof LifecycleOwner) { Lifecycle lifecycle = ((LifecycleOwner) activity).getLifecycle(); if (lifecycle instanceof LifecycleRegistry) { ((LifecycleRegistry) lifecycle).handleLifecycleEvent(event); } } } }
可以看到,SupportActivity添加了一個沒有頁面的ReportFragment,在ReportFragment的生命周期函數中,調用了LifecycleRegistry.handleLifecycleEvent()方法來分發生命周期事件。用一張圖總結一下就是:
AppCompatActivity中添加了一個ReportFragment,其生命周期變化時,調用LifecycleRegistry.handleLifecycleEvent()方法通知LifecycleRegistry改變狀態,LifecycleRegistry內部調用moveToState()改變狀態,并調用每個LifecycleObserver.onStateChange()方法通知生命周期變化。
因為不是所有的頁面都繼承AppCompatActivity,為了兼容非AppCompatActivity,所以封裝一個同樣具有生命周期的Fragment來給Lifecycle分發生命周期事件。
那我們不繼承新版本AppCompatActivity時,Lifecycle是如何通過ReportFragment來分發生命周期事件的呢?
這里我們直接使用AndroidStudio強大的搜索功能,alt+F7搜索ReportFragment的調用者,我們發現:除了SupportActivity以外,還有兩個地方使用到了ReportFragment:LifecycleDispatcher和ProcessLifecycleOwner4.LifecycleDispatcher
字面意思:生命周期分發者
class LifecycleDispatcher { static void init(Context context) { ((Application) context.getApplicationContext()) .registerActivityLifecycleCallbacks(new DispatcherActivityCallback()); } /** * 給所有子Fragment設置State */ private static void markState(FragmentManager manager, State state) { Collectionfragments = manager.getFragments(); if (fragments == null) { return; } for (Fragment fragment : fragments) { if (fragment == null) { continue; } markStateIn(fragment, state); if (fragment.isAdded()) { markState(fragment.getChildFragmentManager(), state); } } } private static void markStateIn(Object object, State state) { if (object instanceof LifecycleRegistryOwner) { LifecycleRegistry registry = ((LifecycleRegistryOwner) object).getLifecycle(); registry.markState(state); } } // 通過注冊Application.registerActivityLifecycleCallbacks來獲取Activity的生命周期回調 static class DispatcherActivityCallback extends EmptyActivityLifecycleCallbacks { @Override public void onActivityCreated(Activity activity, Bundle savedInstanceState) { if (activity instanceof FragmentActivity) { ((FragmentActivity) activity).getSupportFragmentManager() .registerFragmentLifecycleCallbacks(mFragmentCallback, true); } // 給每個Activity添加ReportFragment ReportFragment.injectIfNeededIn(activity); } @Override public void onActivityStopped(Activity activity) { if (activity instanceof FragmentActivity) { markState((FragmentActivity) activity, CREATED); } } @Override public void onActivitySaveInstanceState(Activity activity, Bundle outState) { if (activity instanceof FragmentActivity) { markState((FragmentActivity) activity, CREATED); } } } }
可以看到LifecycleDispatcher是通過注冊Application.registerActivityLifecycleCallbacks來監聽Activity的生命周期回調的。
在onActivityCreated()中添加ReportFragment,將Activity的生命周期交給ReportFragment去分發給LifecycleRegistry
在onActivityStopped()以及onActivitySaveInstanceState()中,將Activity及其所有子Fragment的State置為CREATED
5.ProcessLifecycleOwner字面意思:線程生命周期擁有者
public class ProcessLifecycleOwner implements LifecycleOwner { public static LifecycleOwner get() { return sInstance; } static void init(Context context) { sInstance.attach(context); } void activityResumed() { mResumedCounter++; if (mResumedCounter == 1) { if (mPauseSent) { mRegistry.handleLifecycleEvent(Lifecycle.Event.ON_RESUME); mPauseSent = false; } else { mHandler.removeCallbacks(mDelayedPauseRunnable); } } } void activityPaused() { mResumedCounter--; if (mResumedCounter == 0) { mHandler.postDelayed(mDelayedPauseRunnable, TIMEOUT_MS); } } private ActivityInitializationListener mInitializationListener = new ActivityInitializationListener() { @Override public void onCreate() {} @Override public void onStart() { activityStarted(); } @Override public void onResume() { activityResumed(); } }; void attach(Context context) { mHandler = new Handler(); mRegistry.handleLifecycleEvent(Lifecycle.Event.ON_CREATE); Application app = (Application) context.getApplicationContext(); app.registerActivityLifecycleCallbacks(new EmptyActivityLifecycleCallbacks() { @Override public void onActivityCreated(Activity activity, Bundle savedInstanceState) { ReportFragment.get(activity).setProcessListener(mInitializationListener); } @Override public void onActivityPaused(Activity activity) { activityPaused(); } @Override public void onActivityStopped(Activity activity) { activityStopped(); } }); } }
根據官方注釋,我們可以了解到:
ProcessLifecycleOwner是用來監聽Application生命周期的,因此它只會分發一次ON_CREATE事件,并且不會分發ON_DESTROY事件。
ProcessLifecycleOwner在Activity的onResume和onStop方法中都采用了Handle.postDelayed()方法,是為了處理Activity重建時比如橫豎屏幕切換時,不會發送事件。
ProcessLifecycleOwner一般用來判斷應用是在前臺還是后臺。但由于使用了Handle.postDelayed(),因此這個判斷不是即時的,有默認700ms的延遲。
ProcessLifecycleOwner與LifecycleDispatcher一樣,都是通過注冊Application.registerActivityLifecycleCallbacks來監聽Activity的生命周期回調,來給每個Activity添加ReportFragment的。
從源碼中我們看到,他們的入口都是init(Context),繼續搜索源碼,我們發現:
public class ProcessLifecycleOwnerInitializer extends ContentProvider { @Override public boolean onCreate() { LifecycleDispatcher.init(getContext()); ProcessLifecycleOwner.init(getContext()); return true; } // ...... } AndroidManifest.xml......
了然,Lifecycle自動在我們的AndroidManifest.xml中添加了一個ContentProvider,用于初始化ProcessLifecycleOwner和LifecycleDispatcher,這么做的好處是,不需要我們在Application中顯示調用,不需要我們寫一行代碼。
總結回到我們最初的兩個問題:
State是如何與Activity/Fragment的生命周期綁定的?
在Activity中添加一個ReportFragment(如果你的Activity繼承AppCompatActivity,會在父類的onCreate()中添加ReportFragment,否則由LifecycleDispatcher添加),在ReportFragment生命周期函數中調用LifecycleRegistry.handleLifecycleEvent()方法改變State。
Event事件是如何分發到LifecycleObserver的?
LifecycleRegistry在收到handleLifecycleEvent()后,內部調用moveToState()方法,改變State值,每一次State值改變,都會調用LifecycleObserver.onStateChanged()方法將Event分發到LifecycleObserver
漲知識?學技能?關注微信公眾號:Android必修課
文章版權歸作者所有,未經允許請勿轉載,若此文章存在違規行為,您可以聯系管理員刪除。
轉載請注明本文地址:http://specialneedsforspecialkids.com/yun/77165.html
摘要:五六月份推薦集合查看最新的請點擊集前端最近很火的框架資源定時更新,歡迎一下。蘇幕遮燎沈香宋周邦彥燎沈香,消溽暑。鳥雀呼晴,侵曉窺檐語。葉上初陽乾宿雨,水面清圓,一一風荷舉。家住吳門,久作長安旅。五月漁郎相憶否。小楫輕舟,夢入芙蓉浦。 五、六月份推薦集合 查看github最新的Vue weekly;請::點擊::集web前端最近很火的vue2框架資源;定時更新,歡迎 Star 一下。 蘇...
摘要:五六月份推薦集合查看最新的請點擊集前端最近很火的框架資源定時更新,歡迎一下。蘇幕遮燎沈香宋周邦彥燎沈香,消溽暑。鳥雀呼晴,侵曉窺檐語。葉上初陽乾宿雨,水面清圓,一一風荷舉。家住吳門,久作長安旅。五月漁郎相憶否。小楫輕舟,夢入芙蓉浦。 五、六月份推薦集合 查看github最新的Vue weekly;請::點擊::集web前端最近很火的vue2框架資源;定時更新,歡迎 Star 一下。 蘇...
閱讀 2923·2021-11-23 09:51
閱讀 3160·2021-11-12 10:36
閱讀 3204·2021-09-27 13:37
閱讀 3157·2021-08-17 10:15
閱讀 2587·2019-08-30 15:55
閱讀 2749·2019-08-30 13:07
閱讀 792·2019-08-29 16:32
閱讀 2642·2019-08-26 12:00