Issue 10: Please, make it possible to use BinderContributors for methods not annotated with @ViewHandler
Status:  Invalid
Owner: ----
Closed:  Sep 2010
Project Member Reported by Alexande...@gmail.com, Sep 2, 2010
Currently  [// Process contributors] section is situated within  if (m.isAnnotationPresent(ViewHandler.class)) {} statement.



Sep 2, 2010
Project Member #1 gal.dol...@gmail.com
Mmm, I am not sure I understand this one.

The BinderContributors works on ViewHandlers and EventBusHandlers cause the framework triggers the method when some event happen.

Can you give more details about what you trying to do?
Sep 3, 2010
Project Member #2 Alexande...@gmail.com
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
Project Member #3 gal.dol...@gmail.com
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
Project Member #4 Alexande...@gmail.com
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
Project Member #5 gal.dol...@gmail.com
(No comment was entered for this change.)
Status: Invalid