Re: JsInterop Question regarding execution in index.html

> Thanks that worked! Given that this flag was off by default, what are the > main ramifications of leaving it on? > The flag is not active by default because your project might depend on GWT libraries that are also published as pure JS libraries by exporting the GWT code to JS using

Re: JsInterop Question regarding execution in index.html

Thanks that worked! Given that this flag was off by default, what are the main ramifications of leaving it on? . The below code is successfully exported globally when the flag is on: @JsMethod(namespace = JsPackage.GLOBAL, name = "handleOpenUrl") public static void runMe(String url) {

Re: JsInterop Question regarding execution in index.html

Check if this flag is activated -[no]generateJsInteropExports Generate exports for JsInterop purposes (defaults to OFF) On Mon, 13 Feb 2017 at 14:01 Paul Mazzuca wrote: > Thanks for the quick reply. This was my first inclination, which does not > work. > >

Re: JsInterop Question regarding execution in index.html

Thanks for the quick reply. This was my first inclination, which does not work. @JsMethod(namespace = JsPackage.GLOBAL, name = "handleOpenUrl") public void runMe(String url) { Window.alert("Success"); } Perhaps, I am doing it wrong, but I had always thought the JsInterop wraps existing

Re: JsInterop Question regarding execution in index.html

You can use jsinterop . On Mon, 13 Feb 2017 at 13:24 Paul Mazzuca wrote: > I need to create a javascript function called "handleOpenUrl(url)" that > will be

JsInterop Question regarding execution in index.html

I need to create a javascript function called "handleOpenUrl(url)" that will be called from a Cordova plugin (https://github.com/EddyVerbruggen/Custom-URL-scheme) for a hand off from a mobile browser. If I create the function inside my index.html, it is called successfully. The challenge is

[gwt-contrib] Re: JsInterop Question

That's fine, I was just trying to pre-empt Elemental 2.0 a bit and got the impression from the compiler complaint and some of the design docs linked here that examples like the above wouldn't be possible. Regards, Ben. On Monday, 24 August 2015 22:32:55 UTC+10, Jens wrote: You need to use

[gwt-contrib] Re: JsInterop Question

You need to use normal JavaScriptObject + JSNI for now for these cases. -- 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

Re: JsInterop question ...

Any chance of reply? If it's a bad question I'm happy to hear that as well, just so I know I'm thinking about this the wrong way. Regards, Ben. On Wednesday, 1 July 2015 05:30:17 UTC+10, Benjamin Tillman wrote: Hey everyone, just a quick question regarding JsInterop: how is it proposed to

[gwt-contrib] Re: JsInterop Question

Any chance of reply? If it's a bad question I'm happy to hear that as well, just so I know I'm thinking about this the wrong way. Regards, Ben. On Friday, 31 July 2015 17:13:32 UTC+10, Benjamin Tillman wrote: Hey everyone, I posted this question on the GWT group here

Re: JsInterop question ...

I haven't found a solution either. The final JSInterop version will probably have quite different annotations: (https://groups.google.com/forum/#!searchin/google-web-toolkit-contributors/annotations/google-web-toolkit-contributors/Dwdk-aEHs8Y/OvSNe6egUekJ) There is also a paragraph about

[gwt-contrib] JsInterop Question

Hey everyone, I posted this question on the GWT group here https://groups.google.com/forum/#!topic/google-web-toolkit/sj3pyJPijB8 at the beginning of the month, but since I didn't get a reply I'm just cross-posting here :) Just a quick question regarding JsInterop: how is it proposed to manage

JsInterop question ...

Hey everyone, just a quick question regarding JsInterop: how is it proposed to manage javascript functions that can potentially take more than one type of parameter? For example, take the websocket interface http://www.w3.org/TR/websockets/#the-websocket-interface: @JsType(prototype =