We have discussed this issue at length on our team, as we're building
an application that will eventually grow to be quite large. There are
certainly pros and cons to each approach (nesting presenters vs a flat
lookup at the AppController level).
Nested Pros
Handy place to hook up a hierarchical
Thanks for your insight. I was wondering how the flat lookup approach
would work. When the application starts the MainContainerPresenter
would be created and the go method would be called with a
RootLayoutPanel as a parameter. What I don't see is where the other
presenters would be created, and
On my project I used Gin to wire up nested presenters/views, it is very
nice. I wouldn't dream of doing large-scale MVP now without dependency
injection--it really takes a lot of tedious wiring code out. This book
helped a lot for me:
For now I don't want to bring Gin or Guice into play because I want to
understand MVP. Then I will put DI to simplify things. Let's say I
have a basic UI with a north region and a center region of a
DockLayoutPanel. The north region contains a button, when clicking
that button, the center region
I try to implement the best practices discussed in the article Large
scale application development and MVP. My application is designed
using several widgets:
MainContainerWidget: a DockLayoutPanel
NorthWidget: a widget in the north region of the main container
CenterWidget: a widget in the center
