I wouldn't use these MVP patterns like gwtp before understanding well the different View patterns, start reading here: http://martinfowler.com/eaaDev/SupervisingPresenter.html (martin fowler).
Every situation is different, and "simple" adding a tool like gwtp might not work for you, even worse, might result in awkward buggy code. If you understand well the theory, you can always use (parts) these framework, but to my experience, if you understand well the patterns, you will not use them (anymore) and make things yourself as it's not a lot of coding. Personally I don't think I would use nested presenters, I did that in the past, but didn't like it. I use kind of Autonomous views -> All my widgets extend from lightweight IsWidget objects that construct the actual Widget (builder pattern). I have good experience with it, like and results in good unit testing (I wrote something about that some time ago in this forum). Op woensdag 10 april 2013 01:30:55 UTC+2 schreef Mohammad Al-Quraian het volgende: > > I did my own way of nesting presenters and now I hit a design issue, > should the nested presenter have a reference to the nesting presenter? Is > there a better design than this? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
