Closed jshvarts closed 6 years ago
Does not look like Issues is the right place to discuss it. Closing.
Sorry, I'm just on mobile and haven't had a chance to look into your sample but I gladly will add a link to your sample in the readme. Thanks for sharing your hard work!
James Shvarts notifications@github.com schrieb am Di., 12. Dez. 2017, 20:03:
Closed #292 https://github.com/sockeqwe/mosby/issues/292.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sockeqwe/mosby/issues/292#event-1384214561, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjnrqyX2z8RDf4lzPaUx2JF9qquOGX-ks5s_s4bgaJpZM4Q-DVs .
No problem, Hannes! Having implemented custom MVP solutions before, I am really impressed how Mosby+Conductor simplify it. I hope that the sample code will help increase adoption of the library!
Hey @sockeqwe and everyone,
I finally got around to working to understand Mosby and Mosby plug-in for Conductor for MVP apps. As I learn, I am creating some simple screens at https://github.com/jshvarts/MosbyMVP
These are great libraries so I hope that this samples repo will help grow Mosby and Conductor even more.
Things that I want to still add are:
1) Samples of using Delegate Callbacks rather then extending Base classes. 2) Maybe samples of using Fragments rather than Activities (in my book, Conductor makes Fragments obsolete) 3) My version of a TODO app using Mosby plug-in for Conductor with Dagger.
Anything else that you'd like to see? Any comments so far?
I read http://hannesdorfmann.com/mosby/summary/ and I am not sure how I feel about MvpNullObjectBasePresenter and MvpQueuingBasePresenter. Not sure how widely they are used.
Thanks again for the library!