write a @UiHandler method in another class the widget is declared look
stupid to me. (Cool, let's put 8 class with @UiHandler("widget") and let see
which handler wins!)
Why don't you simply do the opposite?
* @UiHandler("dialogOk")*
* void dialogOk(final ClickEvent event) {*
* yourOtherClass.doSomething();*
* }*
Imagine your other class is an Activity (Presenter from MVP pattern), and
you have a correcttly separated View / activity...
--
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/-/RzvccKeCRbEJ.
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.
