Thank you for this new version!
We immediately tested this 2.8.1 and checked that everything works as
expected in development mode.
However we experienced a strange and blocking deployment problem:
- compilation with unchanged settings (xml files, compilation settings ...
exactly as with 2.8.1)
"*the fact that 2.8 will be maintained in parallel. *(Jens) " !?!
We would certainly appreciate to know more about this fact (announced?
published? where?).
As a matter of fact, if version 3.0 is in line with various statements read
here and there on the web (disparition of widget library,
Okay and Tnx for the DOCTYPE answers.
Now something else...
*ECLIPSE RELOAD GWT WEB SERVER - MEMORY NOT CLEARED.*
With RC1, it was impossible to reload the web server using the eclipse
plugin.
With RC2, it is possible again.
However, there is a major problem encountered during the reload: the
Hi,
RC2 seems OK for our kind of developments... Great!
However I have a general question about the DOCTYPE header directive in the
various *.gwt.xml files.
What is the good option among:
a) these lines are useless because quirk/standard discussion is obsolete.
Ok to remove?
b) these lines
Le mercredi 10 août 2016 14:20:05 UTC+2, Thomas Broyer a écrit :
>
> Workaround would be to duplicate the class, applying the changes, and
> using it as the -server argument to DevMode instead of the broken one from
> GWT.
Tnx Thomas...
Would you be more explicit please ?
Which class should
Same problem exactly.
Any practical solution or workaround would be highly appreciated.
The link provided by Thomas Broyer could not help to find a solution (in
eclipse neon).
PG
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe
Totally agree. GWT 3.0 without RPC would be GWT 3.dead for many of the
current GWT developpers,
For me GWT is "Web development based on Java expertise, with practically no
other technology implications". Extremely powerful and pleasant. Seems that
GWT 3.0 is announced as "no more GWT":
Our
