Yes, remove -nosuperDevMode. On Tuesday, July 7, 2020 at 5:02:19 AM UTC-5, Jasper Suijker wrote: > > Hi, > > We are running with 2.8.2 and want to migrate to 2.9.0 later on. > this is my current gwt server start with arguments: > Main class: > com.google.gwt.dev.DevMode > arguments: > com.test.demo.webclient > -war GWT/war > -nosuperDevMode > -startupUrl demo > > What do i need to change to make it start in superdevmode? (remove > -nosuperDevMode?) > > regards, > > Jasper > > > Op dinsdag 7 juli 2020 02:14:06 UTC+2 schreef Thomas Broyer: >> >> gwt.codesrv is a sign that you're using the deprecated so-called >> "classic" DevMode, that relies on a browser plugin, that indeed only works >> in Internet Explorer nowadays. >> If you haven't already, then first upgrade to at least GWT 2.7.0 (of >> course 2.9.0 would be a lot better), >> then you'll be able to use SuperDevMode the same way as you're used to >> run DevMode, except you don't have to install any plugin: just load the >> page in your browser and it'll automatically trigger the compilation of >> your code. >> Your code will then run in JS in your browser, and you'll debug it from >> your browser's developer tools, leveraging source maps (Chrome or Edge work >> better, likely Safari too; Firefox used to be sluggish but that was >> supposed to be better in recent versions, haven't tried it yet though). >> See http://www.gwtproject.org/articles/superdevmode.html to learn more >> about SuperDevMode. >> >> On Monday, July 6, 2020 at 5:05:13 PM UTC+2, Jasper Suijker wrote: >>> >>> LS, >>> >>> We are using GWT to get our Swing gui available in web. >>> This works nicely. After compiling, we deploy our application in tomcat >>> and it runs and shows the same screens as we have in Swing. >>> >>> Now we want to debug the web parts through the gwt Jetty server. (GWT >>> development mode) >>> To be able to debug, you Start the jetty server and it will give you a >>> url like: http://127.0.0.1:8888/<appp>?gwt.codesvr=127.0.0.1:9997 >>> The part after the question mark is the magic of the GWT server, being >>> able to debug your code. As far as i know this only works in Internet >>> Explorer, is that correct? >>> >>> Internet Explorer is terrible to work with, the javascript engine is >>> terrible and large memory usage, etc.... >>> Microsoft is already pushing users towards Edge, so Internet explorer >>> will stop at some point.. >>> Is there another way to debug GWT? >>> >>> Regards, >>> >>> Jasper >>> >>> >>>
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/057e4f32-d3ce-4401-ac04-40db4c2d3141o%40googlegroups.com.
