Hi Thomas, As you asked, I went through the link( http://www.google.com/events/io/2010/sessions/gwt-continuous-build-testing.html ) but there it was a bit difficult for me to understand the basic reason as to *why*
1.* * we shouldn't use *view.getSaveButton().addClickHandler()*.... i.e to say why we should not have *getter* in our Display interface?? . What I understood from the video is that it is not a good practice to maintain views state information within the presentation, but sorry to say I didn't understood how is that gonna help us. ? 2. In that video its also mentioned that we should use setListeners() rather than addListeners(), that is to avoid more than one listener in the interface. 3. He says he is diverging from Rays understanding of MVP, with respect to not using HasClickHandlers() , please explain why ? One of the reason why I couldnt understand the point could be that in that video there is lot of Google Wave specific code, It would had been easier for me to understand had he used a more generic and a more simpler code to make us understand his point. Please pardon me if I have offended any one. Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/QZ0qKpPH3ykJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
