I've seen many developers turned off MVP by this very issue. While not prone to absolutes, I'd assert that no framework/pattern should be used as a rule. Use it when it has benefits and makes sense.
In the case of MVP to the level of buttons, that might have a benefit at some obscure point in the future, but will result in a lot of code and boilerplate. I was considering the same issue when building a full page calendar widget with GWTP last week and could have made everything down to the day cells MVP, but it just did not provide extra benefit for all the code. So when thinking of MVP, then about the *other* MVP: *Minimum Viable Produc*t. Do you need a few dozen extra interfaces to make those tiles? Do your requirements call for swapping out the views for say different platform views (i.e. mobile) right now? If not, use the Widget pattern until it no longer meets you needs. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
