konmik / konmik.github.io Goto Github PK

What category are we going to place AysncTaskLoader or how do we Use Presenters with AsyncTaskLoader which is attached to a Fragment when using MVP Pattern

The method getView() on Nucleus is deprecated, would be a good idea to change the example to use restartable or deliver methods

Throwing in RxJava without any preface in the introduction of MVP throws in a new element that developers may not be familiar with. This breaks the flow of trying to understand the issue the article is about.

https://github.com/konmik/konmik.github.io/wiki/Introduction-to-Model-View-Presenter-on-Android
Technically speaking, MainPresenter has three threads of events: onNext, onError, onTakeView.
It's misleading to use "thread" here - I think you did not mean a Thread. Please change it.

getView() of RxPresenter is deprecated and we should use restartableXX and deliverXX methods for pushing data from RxPresenter into View.

There is no good explanation how these methods work. What is "latest onNext value"?

How do we set the user input from the view back to the models (no example of that either). This library should be simple. Maybe it is because I'm a little stupid but I don't understand a thing of it...

You mentioned here that people should not use this

.switchMap(it -> serverApi.login(name, password)
    .switchMap(loginResult -> serverApi.requestChatToken(loginResult.loginToken)
        .switchMap(chatToken -> serverApi.doOtherThingsAfter(chatToken))))

but instead use this

LoginResult loginResult = serverApi.login(name, password);
String chatToken = serverApi.requestChatToken(loginResult.loginToken);
return serverApi.doOtherThingsAfter(chatToken);

This is the classic usecase for USING RxJava, NOT avoiding it. The network is inherently asynchronous & your blocking recommendation is a terrible suggestion as each API call blocks the thread that its run in

RxJava can use network backpressure to request only the set of details you need without actually blocking any thread thru non blocking IO & without paying thread switching cost if you use RxJava variant. So your example is completely counter productive

This is a great post!But I doubt the situation in case 3 .
Fragment with setRetainInstance(true) | no change | save/restore | save/restore
How to provethe retained fragment will re-create after the process restart?

The KISS principle link on MVP page (https://github.com/konmik/konmik.github.io/wiki/Introduction-to-Model-View-Presenter-on-Android) leads to 404 Not Found