Anybody find the Contacts2 example confusing and complicated?

hi all,

I am trying to follow along the whats in "http://code.google.com/
webtoolkit/articles/mvp-architecture-2.html", however the code that I
downloaded from that same page doesn't match what is being shown on
the page. It contains the same set of class and the methods does the
roughly the same thing albeit via different code, it just tick me a
bit the when I am trying to digest whats going on.

And is there anybody think its way too much classes and way too many
generics used to construct a simple CRUD app for a single simple
entity? I am posting this just to see if anyone feels the same towards
that and have a better to go around it.

And Spring Roo's scaffolding code seems to be taking a more direct
approach as well. I am still trying to go thru the docs make sense of
both the new GWT 2.0 presenter approach and the Roo's approach.

Please feel free to comment, especially with any real world app
experience using the new MVP-2 architecture, was it really worth the
trouble?

Thanks,
Joseph

--
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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.