[gwt-contrib] Re: $entry() wrapper and JsInterop

2017-07-11 Thread Ignacio Baca Moreno-Torres
Some related links: https://stackoverflow.com/questions/22519254/how-to-use-gwt-entry-function-in-jsni https://groups.google.com/forum/#!topic/google-web-toolkit/Lf6aQG9al-Q https://gwt-review.googlesource.com/#/q/file:user/src/com/google/gwt/core/client/internal/Entry.java Nice, 18540 sounds

[gwt-contrib] Re: $entry() wrapper and JsInterop

2017-07-11 Thread Thomas Broyer
On Tuesday, July 11, 2017 at 1:46:55 PM UTC+2, Ignacio Baca Moreno-Torres wrote: > > What is going to happen with $entry() utility? Some guidance in the > JsInterop gdoc will be a good idea so libs-creator can apply a uniform > strategy. > > Elemento, for example, is waiting to see what to do

[gwt-contrib] Re: $entry() wrapper and JsInterop

2017-07-11 Thread Jens
Take a look at https://gwt-review.googlesource.com/#/c/18540/ for a possible solution. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[gwt-contrib] $entry() wrapper and JsInterop

2017-07-11 Thread Ignacio Baca Moreno-Torres
What is going to happen with $entry() utility? Some guidance in the JsInterop gdoc will be a good idea so libs-creator can apply a uniform strategy. Elemento, for example, is waiting to see what to do (https://github.com/hal/elemento/issues/18), but there are various libraries already using