Future of GWT

[Gourab Panda]

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.

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
https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_
25rfTRvsuJkTtS2vjgi3o/edit#gid=0&range=15:15
and to stay up-to-date with more about this you can join the gitter
channel we talk very often about this topic
https://gitter.im/gwtproject/gwt

I have a huge code base written in GWT. What you guys think about general
future of the framework.
--

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
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[Mincong Huang]

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.

[1]:
https://github.com/gwtproject/gwt/blob/master/user/super/com/google/gwt/emul/java/lang/String.java#L417

Mincong

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.

I have a huge code base written in GWT. What you guys think about general
future of the framework.
--

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
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[Ahmad Bawaneh]

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

I have a huge code base written in GWT. What you guys think about general
future of the framework.