I agree that it would be very helpful to see some examples of building a more complex composite UI.
I've been trying to find a good way to handle this while keeping a clean separation between view and presenter. It gets worse when trying to use GIN along with UiBinder. Both help with construction of object graphs, but I'm struggling to find a way to use them to construct parallel, linked presenter/view hierarchies. The best I've come up with so far is to inject the presenter into the view, mark any injected views as @UiField(provided=true), and not worry about trying to put the presenters into a hierarchy... just let them dangle off of the view instances. However, that presents other problems when it comes to configuring different instances of the view/presenter pairs (the view is starting to be not-so-dumb). As for the complexity of the example code, it looks to me like there isn't any "Contact" specific code in the most complex parts of ContactsViewImpl. This could probably be moved into framework classes (which could be thoroughly tested with GwtTestCase) where application developers wouldn't have to look at it every day or worry about the complexity. -Brian On Apr 25, 6:54 am, interdev <jason.ved...@gmail.com> wrote: > Thank you everyone for sharing. > > >@Chris Ramsdale, > >"We use the technique described in part II. Composite views are responsible > >for instantiating their own children, and making them available for the > >parallel composite presenters. " > >"Regarding the nested layer presenters, thanks for the feedback and I'll look > >into our codebase for examples that we can share publicly. " > > Chris, I was wondering if you can share any code samples, or if > possible ask google team > to write a tutorial on more complex layouts and navigation. (parent/ > child, composite views). > > I've visited many forums, and this has been an area where many are > struggling. The MVP tutorial is great for introducing the concepts, > but > for real world applications with complex layout, i think more examples/ > resources are definitely helpful for those who want to follow best > practices. > > almost all GWT books are written prior to 2009, mainly dealing with > widgets, and very little on architecture, especially MVP. > > Thank You > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
