Re: [gwt-contrib] Re: Problem with JsInterop

2016-09-02 Thread 'Goktug Gokdogan' via GWT Contributors
That is added relatively recent. And thanks for pointing the documentation issue; add a issue to review all before the final release. On Thu, Sep 1, 2016 at 10:08 PM, Arnaud TOURNIER wrote: > Thanks a lot for your answer. > > I tried the solution with defender methods earlier but it did not work

Re: [gwt-contrib] Re: Problem with JsInterop

2016-09-01 Thread Arnaud TOURNIER
Thanks a lot for your answer. I tried the solution with defender methods earlier but it did not work, as far as i remember the compiler refused @JsOverlay defender methods on the JsFunction. The @JsFunction documentation says that : "A JsFunction interface cannot have defender methods." I will try

Re: [gwt-contrib] Re: Problem with JsInterop

2016-09-01 Thread 'Goktug Gokdogan' via GWT Contributors
The limitation around @JsFunction is basically driven from the limitations of being a function. I think there was an earlier discussion in the contibutor list where we explained this in more detail. Being said that, you can handle some overloading in JsFunction interfaces via defender methods mark

Re: [gwt-contrib] Re: Problem with JsInterop

2016-08-30 Thread Arnaud TOURNIER
Oh thanks! I'll try that. Once I think we need to merge our work on those topics... Thanks! Le mar. 30 août 2016 16:06, Paul Stockley a écrit : > If you are passing Resolver into some function. You could instead > create 3 Resolver interfaces and then overload the function so that it took > eac

[gwt-contrib] Re: Problem with JsInterop

2016-08-30 Thread Paul Stockley
If you are passing Resolver into some function. You could instead create 3 Resolver interfaces and then overload the function so that it took each of the resolver interfaces. On Saturday, August 27, 2016 at 9:51:50 AM UTC-4, Arnaud TOURNIER wrote: > > Hi, > > I am playing with js Promises and m