I'd like to chime in as well... Since the project posted with the update hasn't been totally refactored, its very confusing for those new to GAE, GWT, MVP, etc (and it shouldn't be). This seems akin to turning in your homework half-done or half-eaten by the dog...
I would like to encourage Google to complete the refactoring, and in doing so -- present the ideas in a more concise and clear manner. The presentation seems to add confusion rather than clarity. I've found the following article to be extremely helpful in the comprehension of MVP: http://www.atomicobject.com/files/PresenterFirstAgile2006.pdf Article suggests T(est)D(riven)D(esign) beginning with the Presenter layer. The article also suggests a possible Adapter layer for use in getting/ setting data between the Presenter and View layers (which, I quite liked and made my own attempts at MVP much simpler and clearer). In my own experience, and reading other comments, seems that the largest struggle people have is in understanding what code should live in which layer, and how best to achieve that. I'd personally prefer to see some additional instruction/suggestions assisting with these issues. Also, I'd like to see the article updated to provide a better overview of what is going to end up where (and why), and a better walk- through of putting the proper bits into the proper places to achieve that. > > 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 [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.
