On Mar 1, 7:03 pm, Christian Goudreau <[email protected]> wrote: > Is this architecture also possible with the new activity / places approach? > > Yes ! And just to let everyone know, the next major version of Gwt-Platform > will be focused on Gwt 2.1 mvp integration.
Hi, so is this the correct approach for it http://tinypic.com/r/236vq0/7 ? When the Activity is created it gets the instance of the view and creates a new presenter. It binds these two together. When the activity is stopped (by place change) the presenter has to be set to null. Erik On Mar 2, 6:29 am, Geoffrey Wiseman <[email protected]> wrote: > On Mar 1, 3:14 pm, Brian Reilly <[email protected]> wrote: > > > It looks to me like Guit leans toward the "Abstracted Control View" > > approach, as indicated by the @ViewField annotations on the HasText > > fields. > > That would have been my reading too, although it seems as if the > abstracted controls are injected into the presenter (proxies?), and > with the handler methods, there's touches of the 'View Delegate' > pattern as well, I agree. > > It's not an exact match for any of the patterns I've described, but > I'd say there's enough in common to draw some strong parallels. I'm > actually quite curious to dig further into some of these MVP > frameworks for GWT now and get a better sense of how they match up. > > - Geoffrey -- 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.
