Yaakov, Having multiple presenters driving a single view would be a bit strange. Typically want to the presenter to define the display interface that the view will implement. Having multiple presenters drive a single view means that either a) the display interface is defined in some parent presenter class, or b) one of the presenters is responsible for defining the display interface. Either way, it decouples the presenter->display relationship that is inherent to the MVP architecture.
For applications with large UI frontends, you could consider breaking the UI up into smaller presenter/view pairs that are managed by some controller class. Take for example Gmail; the folder list would be one presenter with an associated view, the inbox list another, the Google Talk interface another, and so on. All of these would then be managed by some MainViewController class. Keeping widget-based code out of the presenter for ease of testing is golden. Beyond that it's really a question how much code you want to maintain within a single presenter and view. On Sun, Jan 3, 2010 at 9:20 AM, Yaakov Chaikin <[email protected]>wrote: > Chris, or anyone else with experience on MVP in GWT... > > Practically, do you always have 1 view as the user sees it, i.e., the > whole GUI, or if your GUI has many components (as most GUIs do), do > you have multiple views, and most importantly, multiple presenters, > presenting 1 coherent view to the user? In your example, this would be > similar to splitting the GUI into a view that has the buttons and the > GUI that has the list. > > How would that be handled in MVP? > > Thanks, > Yaakov. > > On Wed, Dec 30, 2009 at 2:43 PM, Chris Ramsdale <[email protected]> > wrote: > > While I see that someone has already found it, I just wanted to let > everyone > > know that it's officially there. > > > http://code.google.com/webtoolkit/doc/latest/tutorial/mvp-architecture.html > > > > We're looking to put together parts 2 and 3 shortly. So far I have UI > Binder > > and Code Splitting integration as topics of interest. Let us know what > else > > would be of help. > > - Chris > > > > On Tue, Dec 29, 2009 at 1:00 PM, jpnet <[email protected]> wrote: > >> > >> I really like this article: > >> > >> > http://code.google.com/webtoolkit/doc/latest/tutorial/mvp-architecture.html > >> > >> However, it's almost useless without the entire source package. Are > >> there any plans to post the source code? > >> > >> Thanks, > >> > >> JP > >> > >> -- > >> > >> You received this message because you are subscribed to the Google > Groups > >> "Google Web Toolkit" group. > >> To post to this group, send email to > [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]<google-web-toolkit%[email protected]> > . > >> For more options, visit this group at > >> http://groups.google.com/group/google-web-toolkit?hl=en. > >> > >> > > > > -- > > > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" group. > > To post to this group, send email to [email protected] > . > > To unsubscribe from this group, send email to > > [email protected]<google-web-toolkit%[email protected]> > . > > For more options, visit this group at > > http://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
