[gwt-contrib] Missing JsInterop 1.0.0-SNAPSHOT

2016-09-05 Thread Colin Alworth
Looks like somehow the JsInterop jars are missing from the google-snapshots repo now, making it difficult to use the latest nightlies. http://build.gwtproject.org/job/gwt/615/console shows creating, signing, and deploying: Signing and Deploying ./poms/jsinterop/pom.xml to

[gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

2016-09-05 Thread Jens
Hm wondering how it ever worked for you as JsInterop usually qualifies JS code with $wnd but your D3.js has been injected into the GWT iframe. So AFAICT with JsInterop you would had to use TOP_WINDOW anyways. You can make it work within the GWT iframe but then you can't use JsPackage.GLOBAL but

[gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

2016-09-05 Thread stuckagain
It looks like this might be a side-effect of https://github.com/gwtproject/gwt/commit/c511029eaae4ec66ff874d7e69efd9516ccc78db I am using JsInterop to interact with the D3 library, Using namespace=JsPackage.GLOBAL. I guess I will have to use "window" instead ? On Monday, September 5, 2016

[gwt-contrib] ScriptInjector seems to be broken (2.8-SNAPSHOT)

2016-09-05 Thread stuckagain
It looks like the ScriptInjector is no longer working properly in the snapshot. I had code like this: ScriptInjector.*fromString*(pBundle.d3JS().getText()).inject(); To load D3 using a TextResource. Since today (just came back after 2 weeks of holidays) the D3 object is no longer available