Hi all, Reading your two posts, and if it helps you (tanteanni) to be more confident if you have two opinions encouraging the same approach, I will say that I completely agree with Thomas: "I couldn´t live without MVP" once I have understand it and know its advantages over other design patterns (architecturally speaking). Having a dumb view and leaving the logic decoupled gives you (and/or your team) power and efficiency, therefore time-saving development, when it comes to develop large applications.
But Thomas, there´s something I don´t understand, when you say "Activities however are in no way related to MVP". Activities are the Presenters in the MVP pattern, I mean, they own the views and there happens the logic decoupling. The views talk/notify the Activities when some user action that needs logic happens. Activities are responsible to talk to the server, send and retrieve data, goto() other Place´s, and therefore keeping the views "dumb". So, when you say that Activities are not related to MVP I can only think that I´m missing something... Could you please shed a bit of light on this? :) 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.
