Closed lectricas closed 7 years ago
In Nucleus presenter is not supposed to control view.
Controlling view (if you really need it) with Rx is weird as I personally think, because Rx is more complex than simple method calls.
@konmik , but what about rxbinding? I think it's nice to get rid of logic in my activity. I took this project as an example https://github.com/matzuk/TestableCodeMobius Can you show your way of handling the scenario when button status depends on editText status?
I have no idea how and why someone will need to control presenter from view with rx(bindings) to control view from presenter back. This type of ping-pong logic is not efficient. There many ways to split the app logic into parts, and ping-pong is the most complicated and less efficient one.
@konmik I agree that bindings require more code and sometimes unreadable. can you please show some examples of how to split the logic?
Hi. What I want is to turn RxBinding callback back to my acitivity. Restartable is not suitable for that, however I need my view object in order to call the callback method. getView is depricated, so I tried to use deliveryFirst:
so this is my method, which listens fields for click event by
RxView.clicks(myview);
And... this seems kinda huge for just one simple callback. RestartableFirst for example make more actions and code looks better and more readable. Second< I have to do this map call
(clicksFrom.map(aVoid -> aVoid))
bacause call somehow don't understand that I'm passing an object there. What I'm doing wrong?