http://groups.google.com/group/google-web-toolkit/browse_thread/thread/6a47d4ac1bb9a3b3 <http://groups.google.com/group/google-web-toolkit/browse_thread/thread/6a47d4ac1bb9a3b3> http://www.youtube.com/watch?v=PDuhR18-EdM
<http://www.youtube.com/watch?v=PDuhR18-EdM>Hope those url's work, if you haven't seen them already. I'm leery of what you might mean by "pureMVC" as like more IT concepts, it can get muddled: MVP being no exception. I've implemented or worked with a bunch of MVC implementations, J2EE and otherwise. MVP is worth the effort required to move to it, though, like MVC, there is no "pure" implementation of it. David Chandler gives a great synopsis of it in the first url: Ray Ryan's video is the second. No MVC implementation I've worked with since 1988 has been easy or less than onerous to test, really at any level. There is always too much inbreeding of the layers. MVP doesn't solve this, but can, if done right. With MVP, I typically get 90%+ code coverage on unit tests. I can't get anywhere near that with standard J2EE "Best Practices" MVC. On Thu, Apr 7, 2011 at 7:55 AM, Rodolphe Gomes <[email protected]>wrote: > Hello, > > I am still having doubts between integrating MVP or PureMVC. > Does anyone has any production experience - drawbacks ? > > Thanks a lot > > -- > 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. > > -- 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.
