| Issue 10: | Please, make it possible to use BinderContributors for methods not annotated with @ViewHandler | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Currently [// Process contributors] section is situated within if (m.isAnnotationPresent(ViewHandler.class)) {} statement.
Sep 2, 2010
Project Member
#1
gal.dol...@gmail.com
Sep 3, 2010
I need an ability to do smth like this:
@MyViewHandler
void a$b$c$click(){
// handler
}
generated implementation will be
view.a.getB().getC().addClickHandler(new ClickHandler() {
public void onClick(final ClickEvent event) {
presenter.a$b$c$click();
}
});
OR
@Setter
<T> T a$b$c$value(){
// handler
}
generated implementation will be
view.a.getB().getC().setValue(presenter.a$b$c$value());
Sep 3, 2010
mmm... got your point, and I think I have the perfect solution for the custom VIewHandler: an extension system. On the other hand, for the setters I think the best you can do is to use either a @ViewField or a ViewAccesor, Those are very new, but really easy to use. Still, I will like to see the real use case if possible. Can you explain the situation? I opened a group http://groups.google.com/group/guitframework, you can start a discussion there. Best!
Sep 4, 2010
As far as I understood, @ViewFields will help me with my first point: it is possible now to bypass strict convention about @ViewHandler annotated method name and now I can use extension mechanism to implement my own method name handling logic. Correct?
Sep 14, 2010
(No comment was entered for this change.)
Status:
Invalid
|