Generally, I wouldn't do this at all. I'd have a RowItemView and a RowItem presenter and let that deal with any row-related actions and fire events in the unlikely situation that the parent needs to know that the row has done something.
Ian http://examples.roughian.com 2009/9/6 fonghuangyee <[email protected]> > > Hihi , > After i go through so many MVP example, i found that we always use > presenter to get those HasClickHandler from Display( Or View) to do > some action. This way works nice for static clickable action, but if > we have some dynamic button ( example a table listing with a list of > clickable action ), then i have to get a list of HasClickHandler from > display? and every time i add new row to the table listing, i have to > take care of the handler action, quite troublesome. > I hope that someone can give me some advice on handling this kind of > scenario. > > Thanks. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
