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 Chrome (didn't try in Firefox yet). Still I guess it could be faster to debug using separated .js files. However, as this is no longer GWT's goal, ok. At least now debugging in Chrome is usable, and I no longer need that old version of Firefox 26 which still runs the classic dev mode.
Em sexta-feira, 5 de dezembro de 2014 12h31min41s UTC-2, Jens escreveu: > > Separate compilation mentioned in your linked issue has been reworked into > incremental per file compilation what you have now with GWT 2.7. The > benefit is that people do not have to refactor their applications into > multiple modules to get the benefit of faster recompiles in SDM. > > > Regarding CodeServer restarts: > > With current GWT master branch, a restart of the CodeServer reuses the > caches from the last compile which reduces the startup time of CodeServer > significantly. > > Keep in mind that you do not have to use the DevMode class to start the > embedded Jetty + Code Server process. You can also split these processes so > you do not have to restart SDM CodeServer if you do a server side change. > > DevMode -noserver or launching CodeServer directly only starts the SDM > code server. Then you can provide your own application server or actually > start DevMode -nosuperdevmode which does start classic DevMode but also > the embedded Jetty for your server side code. > > I rarely restart CodeServer during the work day. > > > -- J. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
