> Our current workflow is using SuperDevMode + Jetty and I'd like to
provide similar experience to our team.
I had a similar concern, as before we both SuperDevMode and the app in the
same Java process.
After the switch, we need to start the codeserver and then the app, via
Tomcat. But, things w
We started using GWT in our project in 2009 (GWT 1.5.0!)
When we moved from Maven to Gradle in 2020 (one of the best decisions ever,
because the project is complex, has a lot of code generation and Gradle's
skipping of already executed tasks is a must - it was unbearable with
Maven), we've also
We ended up using no plugins for GWT with Gradle. Even if there are some,
none of them fit well.
Luckily, GWT compiler has a nice CLI, so...
Also, we make the gwt a subproject, as we don't use GWT RPC anyway. This
helps keeping gwt-dev out of any runtime classpath!!!
Below is a trimmed version (
apps and making GWT3.0 that only works for new apps
>> only or requires app rewrite does not make any sense.
>>
>> to get more insight on what have been done check this list
>>
>> https://ci.vertispan.com/
>>
>> On Wednesday, February 19, 2020 at 3
It has always been said that GWT is active when similar questions are asked
in the forum.
However, given that the last version, 2.8.2, was released on Oct 19, 2017
and was a bugfix for the 2.8.0 version, released on Oct 20, 2016, I can't
see it as "active".
At least it smells bad!
Even the 1.0 r
Em quinta-feira, 4 de agosto de 2016 12:03:04 UTC-3, Thomas Broyer escreveu:
>
>
>
> On Thursday, August 4, 2016 at 2:21:29 PM UTC+2, Luis Fernando Planella
> Gonzalez wrote:
>>
>> I've always used the closure compiler with past versions (even with
>&
I've always used the closure compiler with past versions (even with
2.8.0-beta1, which we have used in production already).
Now, to my surprise, it is no longer supported in GWT 2.8.0-rc1, as there's
no mention to it in the release notes
(http://www.gwtproject.org/release-notes.html).
Now the c
"classpath conflict is generally not a valid reason, because the part of
GWT that includes Jetty is not concerned about the server side of the
applications"
Unless you run [Super]DevMode, which runs both in a single JVM, then it is
a pain.
There are other libs which are bundled in GWT jars, caus
I'd like to ask for an update on the planning for 2.8 release.
Are there still many missing functionality? What is the tentative release
schedule?
I'm avid to change our project source level to Java 8, but I'm not
confident in using the SNAPSHOT in a release version of our app.
Any chances it wil
That, of course, depends on the application requirement.
I work on a very large app which is not (only) used by ourselves, but by
other organizations.
And on each organization, administrators can change translations on the fly
- just a F5 or logout / login away.
In this scenario, of course, there
Ok, I'll try to use separated servers for code server and server side.
Regarding the monolithic .js, in GWT 1.6 it was impossible to debug in both
Chrome and Firefox - they both crashed, and I always suspected that the js
/ sourcemap file were too big.
Now with GWT 2.7 I can debug normally in Ch
Hi.
I created an issue several months ago -
https://code.google.com/p/google-web-toolkit/issues/detail?id=8581[1] to split
up generated .js.
The answer was that a .js file, with its corresponding source map, would be
generated per module.
I'm analyzing now (with GWT 2.7.0) the output, and I stil
>
> ok, but this leads me to the question, why we don't use REST/JSON right
>> from the beginning?
>>
>
> At the beginning of a project you usually know what you want to do. So if
> you want native clients for different platforms then you will start with
> some sort of REST/JSON or protobuff/th
>
> ok, but this leads me to the question, why we don't use REST/JSON right
> from the beginning?
> Isn't it a potential option for nearly any web application today to be
> complemented by a mobile version some day?
>
I work in a large project which started in 2008, but was not full time back
already in FF,
soon in Chrome).
Luis Fernando Planella Gonzalez
Em 18-02-2014 04:57, Klemens Schrage escreveu:
Maybe there are technical reasons for this since trying to use
SourceMaps with CodeSplitting in a production environment gave me
debugging problems (see
https://groups.google.com/fo
reveu:
On Friday, February 14, 2014 8:50:22 PM UTC+1, Luis Fernando Planella
Gonzalez wrote:
Well, after patching CompilerOptionsImpl in gwt-codeserver.jar to
return true in isRunAsyncEnabled(), the code server started
splitting the code, but source maps were only generated fo
mpl has this:
@Override
public boolean shouldSaveSource() {
return false; // handling this a different way
}
This "different way" is explicitly not handling the runAsync case.
Is there a strong reason for this?
Thanks in advance.
Em sexta-feira, 14 de fevereiro de 2014 15h55mi
Hi.
I'm recently attempting to use SuperDevMode, but our project is quite
large, and the generated compiled .js has ~12MB.
Chrome struggles (and hangs) when attempting to download source maps,
making the whole debugging unpractical.
Without SuperDevMode, we use code splitting, and the fragments a
I noticed this only happens when unchecking the launch and deploy to
war directory on the preferences.
I actually don't want the gwt-servlet.jar in WEB-INF/lib.
On 21 jan, 12:13, Luis Fernando Planella Gonzalez
wrote:
> Hi.
> I'm currently using GWT 2.1.1, with the Eclips
Hi.
I'm currently using GWT 2.1.1, with the Eclipse plugin
1.4.2.v201012211742.
When running the development mode without the builtin server, it's all
ok.
However, when running the builtin server, all .svn directories nested
in the war dir are removed, making the source control go mad.
Is there a w
> Anyone has a better idea?
public boolean equals(Object obj) {
if (!(obj instanceof Point)) {
return false;
}
Point p = (Point) obj;
return fX == p.fY && fY == p.fY;
}
public int hashCode() {
return (int) (pX + pY);
}
--
You received this message because you are sub
I have implemented something like this in my own app, but can't post
the GWT code.
However, here is the HTML sketch I reproduced in GWT with widgets:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>