Thursday, February 15, 2018

Re: Understanding JsInterop

Thanks! I didn't think of casting to Object first... I'll give it a try. I generally turn on as many compiler warnings as I can stand to get my code to compile through a strict filter, but I was getting outright errors.

Also, namespace with "Element", Doh! of course...

On Thursday, February 15, 2018 at 2:10:21 AM UTC-8, Thomas Broyer wrote:

On Thursday, February 15, 2018 at 11:01:41 AM UTC+1, Vassilis Virvilis wrote:
Amazing trick!

Obvious if you think about it - but very difficult to think it initially (for us mere mortals).

Well, when you write "element.getBoundingClientRect" in JS (without the parenthesis), this is exactly what you're doing: getting a reference to the function.
In JS, if you call it later, you need to either use .call(element) or .apply(element) to setup the appropriate 'this' element, or you first need to .bind(element) it to the element. I'm not sure how JsInterop works in this case, maybe (probably) my second example wouldn't actually work as it does neither of these (you could use an element2.core.Function to .call()/.apply() or .bind()).

That being said, I didn't came with this pattern by myself either, I believe I saw it somewhere in GWT's emulation library.

You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment