> I agree that we need a more general low-labor way to bind events in a > GWT app, but this doesn't seem to be it. Am I missing something?
It's not necessarily related to events, but I've been pleased with the low-labor aspect of generating views: http://gwtmpv.org/viewgeneration.html My workflow: * In Foo.ui.xml, add a "ui:field=name" line * Eclipse project builder sees the change, automatically runs codegen * IsFooView is updated with "IsTextBox name()" * GwtFooView is updating with @UiField name/etc. * StubFooView is updated with "StubTextBox name()" * In FooPresenter, which extends Presenter<IsFooView>, add: * view.name().addClickHandler(...) Given GwtFooView is entirely generated, I cannot use @UiHandler events, hence FooPresenter calling "addClickHandler". However, I don't find this to be a big deal, as I'm trending towards a gwt-pectin-style binding DSL: // in FooPresenter onBind binder.bind(model.nameProperty).to(view.nameTextBox) So still no inner-classes, and the model/view keep each other up to date when one or the other changes. Note that the model part is entirely optional, it's only required if you want the handy "binder.bind" syntax. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
