SuperDevMode recompiles RPC since they are unchanged

[Hakan Cunier]

Hi,
We are using GWT 2.7.0, and trying SuperDevMode. Works well unless you restart the jetty server. After starting jetty in superdevmode and launch chrome (sdbg) it compiles and generates rpc manifests. Well no problem, when you shutdown and start jetty, same compilation/calculation thing happens again without ANY CHANGE made in the files. Nothing changed i mean just a restart.

We have 20 RPC services and each has many methods and returning too many types unfortunately taking too long(~5 min/each). Its too interesting that although we currently use Legacy mode (although it was deprecated) it works at acceptable speeds(~90secs for ALL) under this conditions with Firefox 26.

This really stops/aborts/cancels us on development. Should switching to 2.8.1 make sense? Or what we are doing unexpected by the SuperDevMode? Or is this a needed thing?

[Jens]

IMHO it is preferable to launch SuperDevMode and your server (be it jetty or anything else) separately so you can restart them separately. We do that at work and only rarely restart SuperDevMode.

Generally restarting SuperDevMode in GWT 2.8.x works better as GWT 2.8.x stores a cache on disk that can be reused between restarts. Also GWT 2.8.x SuperDevMode only recompiles code that has been modified when you reload the browser. GWT 2.7. always recompiles the whole app when using the bookmarklets to recompile your code. So generally GWT 2.8.x SuperDevMode should work faster in terms of recompilation.

-- J.

[Thomas Broyer]

On Tuesday, September 19, 2017 at 5:30:11 PM UTC+2, Jens wrote:

IMHO it is preferable to launch SuperDevMode and your server (be it jetty or anything else) separately so you can restart them separately. We do that at work and only rarely restart SuperDevMode.

I wholeheartedly agree, but even when using the embedded Jetty container in DevMode, you can restart the webapp without restarting DevMode.

 

Generally restarting SuperDevMode in GWT 2.8.x works better as GWT 2.8.x stores a cache on disk that can be reused between restarts. Also GWT 2.8.x SuperDevMode only recompiles code that has been modified when you reload the browser. GWT 2.7. always recompiles the whole app when using the bookmarklets to recompile your code. So generally GWT 2.8.x SuperDevMode should work faster in terms of recompilation.

Hey Jens, nobody should use the bookmarklets in 2.7 either ;-)

But yes, as I said in https://github.com/gwtproject/gwt/issues/9549#issuecomment-330555850, 2.8 (or HEAD-SNAPSHOT) should work better and would be the basis for a fix/improvement if ever needed, so the first thing to do is (always) updating to the latest version (and trying HEAD-SNAPSHOT too if you can).

[Jens]

Hey Jens, nobody should use the bookmarklets in 2.7 either ;-)

Oh indeed, mmmh I guess mixing it up was a symptom of always using some custom build of GWT :-)

-- J.

[Ignacio Baca Moreno-Torres]

Eh! the bookmark (or similar tool https://gist.github.com/ibaca/1dc87a58ee542840a5f90c5ff2931329) are still useful if you use only the codeserver.

--
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]

On Wednesday, September 20, 2017 at 11:25:45 AM UTC+2, Ignacio Baca Moreno-Torres wrote:

Eh! the bookmark (or similar tool https://gist.github.com/ibaca/1dc87a58ee542840a5f90c5ff2931329) are still useful if you use only the codeserver.

If you mean "only the codeserver", without an HTTP server for the HTML host page, then yes; but that's really an edge-case (and the only valid use case for the embedded Jetty in DevMode if you ask me)

That's what I call a "standalone app" in https://tbroyer.github.io/gwt-maven-plugin/codeserver.html

I'd still strongly recommend using either DevMode or a separate HTTP server ("python -m http.server" works great; but there are many other similar lightweight tools; or possibly https://github.com/tbroyer/gwt-devserver) and not rely on the bookmarklets.

We're getting really off topic for the thread though.

[Hakan Cunier]

Hi again,

I wonder my issue is related with https://github.com/gwtproject/gwt/issues/7519

19 Eylül 2017 Salı 17:05:34 UTC+3 tarihinde Hakan Cunier yazdı: