On Mon, Feb 15, 2010 at 11:01 AM, Nathan Wells <[email protected]> wrote: > The main reason (for me) for removing and dependencies on the model > from the view is that as you add dependencies, you will also add > state. > You will then be managing your application state in your view, > which is (1) something you would want to use JUnit for, and (2) a > major reason for the presentation layer in the first place.
Well, that's not really true or at least it certainly doesn't have to be. Your display.setContacts(List<Contact) method doesn't have to *store* the list (and therefore introduce state into your view). It can just do the same thing that setData(List<String>) does (in the MVP Contacts example). I.e., it can remove all entries from the table and iterate through the Contact list, populating the table with contact values, throwing the List<Contact> away after it's done. Yaakov. -- 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.
