Future of GWT

2,612 views
Skip to first unread message

Slick Technologies

unread,
May 10, 2018, 4:32:35 AM5/10/18
to GWT Users
I have a huge code base written in GWT. What you guys think about general future of the framework.



Ahmad Bawaneh

unread,
May 10, 2018, 5:03:14 AM5/10/18
to GWT Users
GWT has a Brilliant Future, While GWT 2.x will still receive a long term support, GWT 3 is moving forward faster than ever now, and it also going to ensure a smooth migration path from GWT 2.x.

We as a community now have taken the driver seat, and since then the state of GWT 3 is moving faster toward releasing, check here for the GWT 2.x modules being ported to GWT 3 with the names of the contributors who are working on each


and to stay up-to-date with more about this you can join the gitter channel we talk very often about this topic

Gourab Panda

unread,
May 14, 2018, 12:32:38 AM5/14/18
to google-we...@googlegroups.com
The only problem we saw in Migration is, the Legacy Dev Mode in not supported in GWT3 
It takes hell lot of time for our application to run on GWT super dev mode.

Regards
Gourab.

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

Frank Hossfeld

unread,
May 14, 2018, 12:49:06 AM5/14/18
to GWT Users
why takes it so much time? 

Ahmad Bawaneh

unread,
May 17, 2018, 5:58:53 AM5/17/18
to GWT Users

recently we upgraded one of our applications that has around 300k LOC from gwt-2.5.1 and old gwt maven plugin to gwt-2.8.2 and tbroyer maven plugin, the upgrade went almost smooth and we had no issues with codeserver. the only issues we had were related to old version of GXT having classes not working with new gwt, but since we have no plans to upgrade gxt and knowing that any upgrade will be a breaking change we went an patched the 3 classes causing the issue.

we have been working on the new version for 2 weeks so far and things are great.


On Thursday, May 10, 2018 at 11:32:35 AM UTC+3, Slick Technologies wrote:

Mincong Huang

unread,
May 18, 2018, 1:33:09 AM5/18/18
to google-we...@googlegroups.com
Recently, we also upgraded our application of 100k LOC from GWT 2.7.0 to GWT 2.8.2. Some key changes we faced are:
  1. We uses super dev mode: It compiles correctly, same speed as the legacy dev mode. It also allows us the debug on the dev environment (requires some config).
  2. The method `String#equals` requires instance itself to be non-null [1]: If you've any "dirty" data comparison in GWT 2.7, it won't work in GWT 2.8 anymore. You'll have an exception.
  3. Use Java 8 syntax: codes are more readable.
  4. We're still using the legacy GWT Maven plugin, but latest version. It doesn't support multi GWT modules very well, so we have to launch super dev mode from IDEs (Eclipse and IntelliJ). We might switch to tbroyer maven plugin later.
We're using the new version for 3 weeks now. Everything works fine.


Mincong

Ahmad Bawaneh

unread,
May 20, 2018, 3:55:00 PM5/20/18
to GWT Users
according to my experience codeserver issues happens when client and server dependencies are mixed up, one good way to solve such mix is split the code into client and server module as it is in the default project created by tbroyer gwt modular webapp https://github.com/tbroyer/gwt-maven-archetypes 


On Thursday, May 10, 2018 at 11:32:35 AM UTC+3, Slick Technologies wrote:
Reply all
Reply to author
Forward
0 new messages