Timeline for How many presenters should I use in proper MVP?
Current License: CC BY-SA 3.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2017 at 22:23 | comment | added | RubberDuck | More like this @RSahu i.imgur.com/lzbWvne.jpg | |
| May 30, 2017 at 21:58 | comment | added | R Sahu | @RubberDuck, are you thinking of something along the lines of imgur.com/CJUhqg7. | |
| May 30, 2017 at 21:48 | comment | added | RubberDuck | @RSahu you drew them as intended. What I'm saying is they should point the other way. PresenterN shouldn't know that PresenterCommon exists. I'm also skeptical of having one "god" model. Each PresenterN should have its own model while PresenterCommon orchestrates interactions in between the others. This can be easily achieved by treating PresenterNs as models that raise events for PresenterCommon to react to. | |
| May 30, 2017 at 21:42 | comment | added | R Sahu | @RubberDuck, I thought I had the arrow directions correctly drawn for dependencies. dlsweb.rmit.edu.au/toolbox/ecommerce/dad_respak/dad_tutorial/…. | |
| May 30, 2017 at 21:37 | comment | added | RubberDuck | Yes. I did interpret it differently. I would invert the dependencies and control. | |
| May 30, 2017 at 21:17 | history | edited | R Sahu | CC BY-SA 3.0 | Refined a bit |
| May 30, 2017 at 21:12 | vote | accept | Willi Mentzel | ||
| May 30, 2017 at 21:12 | comment | added | Willi Mentzel | @SRahu your first sketch is confusing somehow. :( maybe you could remove it? Otherwise superb answer and effort!!! | |
| May 30, 2017 at 21:09 | comment | added | R Sahu | @WilliMentzel, RubberDuck interpreted my diagrams differently than I what I meant. | |
| May 30, 2017 at 21:07 | comment | added | Willi Mentzel | @RSahu I see, I was confused because of RubberDuck's comment which contradicts what you just said (doesn't it) and this confused me! :( | |
| May 30, 2017 at 21:04 | comment | added | R Sahu | @WilliMentzel, PresenterCommon can communicate with Presenter N using an abstract Presenter interface. But it has to know the list of Presenters in needs to communicate any changes to the Model. Presenter N has to be registered with PresenterCommon for that to work correctly. | |
| May 30, 2017 at 21:01 | history | edited | R Sahu | CC BY-SA 3.0 | Fixed image |
| May 30, 2017 at 21:00 | comment | added | Willi Mentzel | @RSahu So, if View1 receives input and View3 should update accordingly, how would that be possible if PresenterCommon does not know Presenter 3? :( I am sry for keeping to ask.. Thank u for your efforts. I already upvoted!! | |
| May 30, 2017 at 16:05 | comment | added | R Sahu | @WilliMentzel, Hopefully the updated answer is useful :) | |
| May 30, 2017 at 16:05 | history | edited | R Sahu | CC BY-SA 3.0 | Expanded a bit |
| May 30, 2017 at 15:27 | comment | added | Willi Mentzel | @RSahu So, with API/Framework you would mean my Activity (to speak in Android terms)? The way I thought of it until now was: View1 (Activity), View2 (Fragment 1), View3 (Fragment 2). I know the concept is not bound to any Framework, but it would be nice if you would use Android terms next to the abstract ones. Thank you! | |
| May 30, 2017 at 15:23 | comment | added | R Sahu | @WilliMentzel, I updated the answer a bit to clarify a few things. Hopefully the answer makes more sense now. | |
| May 30, 2017 at 15:22 | history | edited | R Sahu | CC BY-SA 3.0 | Refined a bit |
| May 30, 2017 at 11:52 | comment | added | Willi Mentzel | @RubberDuck If P1, P2, P3 don't know about the main presenter who is going to call its methods? | |
| May 30, 2017 at 11:46 | comment | added | RubberDuck | @WilliMentzel Presenter 1,2,&3 don't know about the master controller. That's why the arrows only go in one direction. The overseer is responsible for coordinating between presenters, not individual actions on models or views. Is it too much complexity? I don't think so. I think it's less complex than having a God presenter that knows everything about every model/view. | |
| May 30, 2017 at 7:44 | comment | added | Willi Mentzel | So, the (Main)Presenter knows all the other Presenters (1,2,3)? If, yes why are the arrows only in one direction? Can't the Presenter call methods on the (Sub)Presenters? If View1 receives a button click for instance, methods would be called on the following entities in order: View1 -> Presenter1 -> Presenter -> Presenter3 -> View3? Isn't that a little too much complexity? | |
| May 30, 2017 at 1:13 | history | edited | R Sahu | CC BY-SA 3.0 | Fixed image |
| May 29, 2017 at 23:57 | history | edited | R Sahu | CC BY-SA 3.0 | Refined a bit |
| May 29, 2017 at 23:52 | history | answered | R Sahu | CC BY-SA 3.0 |