[gwt-contrib] Re: GWTCon 2015 keynote question

David Chandler made a statement regarding Sencha GXT: https://www.sencha.com/forum/showthread.php?306057-GWT-3.0-Sencha-GXT-and-the-future-of-the-widget-eco-system- -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from

[gwt-contrib] GWTCon 2015 keynote question

This points to the GWTCon keynote done by Julien Dramaix.

Re: [gwt-contrib] Re: New JsInterop document

On Fri, Nov 13, 2015 at 6:28 AM, Ümit Seren wrote: > Is there a way to add dynamic properties to a JsType without relying on > JSNI ? > > With the experimental JSInterop version I had following solution: > > @JsTypinterface Options { > >@JsProperty void getSomeProp();

Re: [gwt-contrib] Re: New JsInterop document

You could probably support Modules via a GWT linker. Generators and Async functions could be done by a GWT Generator/Linker combo + BabelJS. There's no real plans to support ES6 in GWT, but you could arrange enough hacks with Generator/Linker/Library stuff to make GWT 2.x stuff consumable from

Re: [gwt-contrib] Re: New JsInterop document

Generally speaking J2CL seeks to support Java language features and in the process of doing so make use of modern ES6 features. When it comes to the separate topic of making advanced ES6 features (that don't exist in the Java language) available to J2CL users the path for that is via the JsInterop

Re: [gwt-contrib] Re: New JsInterop document

I think you might be able to get away with Async functions something like this: @JsFunction interface AsyncFunction { T execute(); } public class Foo { Promise fetchJson() { return Async.await(Xhr.fetch("/someJson")); // returns a Promise } } public class Async {

Re: [gwt-contrib] Re: New JsInterop document

Do you plan on supporting these features in j2cl in the future? On Friday, November 13, 2015 at 4:23:21 PM UTC-5, Ray Cromwell wrote: > > > You could probably support Modules via a GWT linker. Generators and Async > functions could be done by a GWT Generator/Linker combo + BabelJS. There's >

[gwt-contrib] Re: New JsInterop document

A number of the new frameworks (Angular 2, Aurelia) are planning on using ES6 and ES7 features such as Modules, Decorators, Generators and Async functions etc. Are there plans to support these on the 2.x code base or would these only be supported by j2cl in the future? On Friday, October 23,

[gwt-contrib] Re: GWTCon 2015 keynote question

I was at GWTcon, and my perception of Juliens keynote and his presentation on JSInterop was, that he used AngularJS to demonstrate that it is now possible to use a JS based framework with GWT 2.8 through JSInterop, and to show solutions to common issues you might run into while doing so. Which

Re: [gwt-contrib] GWTCon 2015 keynote question

I think to be future proof you should use anything that is not based on the widget system. Since that will be gone in GWT 3.0 We are using Ext JS fpr example on top of GWT. On 13 November 2015 at 10:52, stuckagain wrote: > This points to the GWTCon keynote done by

[gwt-contrib] Re: GWTCon 2015 keynote question

Well if you want to switch to J2CL in the future and you want to be absolutely sure that you actually can switch then you should not use any GWT library/framework and GWT SDK features that can not guarantee to work with J2CL. GXT/Vaadin: You should ask them about their plans regarding J2CL

Re: [gwt-contrib] Re: New JsInterop document

Is there a way to add dynamic properties to a JsType without relying on JSNI ? With the experimental JSInterop version I had following solution: @JsTypinterface Options { @JsProperty void getSomeProp(); @JsProperty String getSomeProp2(); @JsProperty void setSomeProp2(String prop);