Re: [gwt-contrib] Re: Future direction for common JS api's

Elemental2 uses typescript as it's intermediate representation, so you can do Closure Externs -> TypeScript -> JsInterop or WebIDL -> TypeScript -> JsInterop or (insert favorite syntax here) -> TypeScript -> JsInterop. BTW, Note that JSweet really punts on most JLS semantics, so it's problematic

Re: [gwt-contrib] Re: Future direction for common JS api's

Interesting; I had not seen JSweet before. The javac -> TypeScript -> JS approach is surprisingly parallel (albeit with different selections) to J2CL's ecj -> closure -> JS. - Stephen On Wed, May 18, 2016 at 8:50 AM Jens wrote: > Given that Elemental 2 is developed

[gwt-contrib] Re: Future direction for common JS api's

Given that Elemental 2 is developed behind closed doors, I would guess it can take TypeScript definition files and/or some IDL input to generate JS APIs for GWT / J2CL. That should cover nearly all Web APIs. IMHO TypeScript definition files would be preferred because there are tons of them on