GWT Future plan

[mohammed sameen]

Hi All,

  We have multiple product developed primarily using GWT and currently used by our end customers.

Wanted to know the road map of GWT. I got some unofficial update that google is moving there product which is developed in GWT to some other new technology. Is it true?

What is long term plan for GWT and also we haven't seen any new release from past one year. Any suggestions ?

[Marko]

11 hours ago Google released the first version of this "other new technology", which is named J2CL and is located here: https://github.com/google/j2cl

They took the existing GWT Java Emulation Library, but have rewritten the Java-2-JavaScript transpiler in such a way, that the resulting code is prepared for JavaScript Closure Compiler (https://github.com/google/closure-compiler). This has been made to make Java code much easier to integrate with existing JavaScript apps.

J2CL will not support the GWT Widgets, GWT RPC and other GWT libs - only the basic Java and also the JSInterop.

So basically this is significantly reduced version of GWT with completely new transpiler. And because of such big changed and non-compatibility with GWT this is not called GWT anymore, but J2CL.

Regards,
Marko

[David Nouls]

Hi Marko,

I guess you have not been following GWT discussions a lot. GWT 3 is going to build on top of this j2cl and from what I followed here, on gwt-user and on gitter, there are already a lot of packages of GWT converted to work with j2cl.

There will be problems supporting everything in GWT 2, but quite frankly, it is about time that newer ideas are explored and older technologies are removed.

My hope is that we can start using j2cl and gwt 3 to create reusable webcomponents. Reusable with other technologies, not just if you just stick with one tech stack.

Regards,

David

--
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 google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[Thomas Broyer]

Three quick points:

• There will be a GWT 2.9, which you can somehow track here: https://github.com/gwtproject/gwt/milestone/19
• Many people are working on "disassembling" gwt-user into smaller libs that will also work with j2cl, changing the package from com.google.gwt to org.gwtproject, so they can also be used with GWT 2's gwt-user. A few of them have already moved to the gwtproject organization on GitHub: https://github.com/gwtproject
• GWT 3 will be a "rebuild" based on j2cl and the closure compiler: a set of "build tools" (Maven plugin and Gradle plugin, a "dev server", a solution to bring back "permutations" –mostly for i18n– and a "selection script", etc.), and a set of libraries (see above).

All of this is community driven, with people contributing for the most part on their own time, so there's absolutely no ETA for anything.

On Wednesday, November 14, 2018 at 7:32:27 AM UTC+1, mohammed sameen wrote:

[Freddy Boucher]

Since you're releasing a new version soon, I will try my luck again:

Could you include #19800 Fix date formatting around daylight time transitions in the next release? Thanks

And just a general question, why does it takes so long to approve/merge all the pending PR?

For example this #19800 PR is more than 1 year old and it's just one among all the others.

Anyway thanks

[Michael Joyner]

Is this going to make into GWT JRE Emulation proper any time soon?

https://github.com/OneGeek/GWT-CompletableFuture

[Ahmad Bawaneh]

why it should be?! why not use it as a stand alone lib? we already do.

[Michael Joyner]

It is part of the JRE standard is it not? Shouldn't it be part of the standard JRE emulation?

--

[Thomas Broyer]

On Friday, November 16, 2018 at 3:55:16 PM UTC+1, Michael Joyner wrote:

Is this going to make into GWT JRE Emulation proper any time soon?

https://github.com/OneGeek/GWT-CompletableFuture

If nobody contributes the patch or even files an issue (and Andrei apparently didn't, probably it needed more tests), no.

(and I do agree its place is in GWT proper)

BTW, note that a few classes in this lib are now in GWT proper (e.g. Callable, CancellationException, Executor, Executors, RunnableCallable, etc. are already in GWT 2.8.2), and native Promise support could probably be moved to deferred binding nowadays: https://caniuse.com/#feat=promises