On Friday, September 7, 2012 2:43:51 PM UTC+2, Francois Marot wrote: > > Hi Thomas and thanks for your response. > You're right, I'm not talking about how the View sees its Presenter but > how the Presenter is seen from "what's above him" (in my case, usually > another Presenter, my Presenters are nested). From what I understood (and > pretty like it !) from the Google MVP Tutorial > <https://developers.google.com/web-toolkit/articles/mvp-architecture>the > Presenter is usually not a component (or Widget) in itself but puts its > component (its View) inside the container that is given to him in its > go(...) method. So I thought what I am doing was pretty classic MVP... > Nevertheless, I totally agree that the solution using the "HasWidgets" > type in the go(...) method may lead the Presenter to have too much knowlege > of the internals. The drawback: it seems that more components implement the > HasWidgets type rather than the AcceptsOneWidget one. I wouldn't want to > have to force every class to reuse my dirty wrapper (see > HasWidgetsToAcceptsOneWidgetWrapper). Anyone with prior experience ?
The Wave guys: http://www.google.com/events/io/2010/sessions/gwt-continuous-build-testing.html (search for "Creating a new dynamic sub component" in the slides; and you'll note that the "parent view" then adds the "child view" to it and handles layout, not the other way around; there's no go(AcceptsOneWidget) method, instead each view would implement IsWidget) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/XmmK1YinVHEJ. 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.
