Ok thanks Jens, great to know that (especially for the second point)
Le mardi 11 novembre 2014 10:48:10 UTC+1, Jens a écrit : > > 1- First of all, I actually have a problem with my huge project, and the >> browser says: >> Uncaught com.google.gwt.core.client.JavaScriptException: (RangeError) : >> Maximum call stack size exceeded Impl.java:286entry0_0_g$ >> Impl.java:286(anonymous function) >> How can I ever guess what's wrong with the app, or where to put a >> breakpoint with this??? >> > > Tell Chrome to stop on any exception (in DevTools under "Sources" the > small sign button on the right). > This is just one of the encountred issues: it also happened to me that the breakpoint didn't stop when I've put it inside a click handler, I never understood why but I had to do a workaround. Sometimes I put the breakpoint on a java source and it breaks in the js code instead..!?? So sure there's a learning curve and a jump has to be done here, but let's not forget that the strength of GWT was to write in java and have a js compatible to all browsers. Now we have: write in Java in your usual tools, but leave you environement when you'll have to debug and by the way, learn all the js tricks and learn the chrome dev tools, and then also learn how to read the values in js. Also eventually keep calm since the tools are not always stable :). I mean, the "kepp your java skills and we'll handle the js" is not that true anymore... > > >> 2- Second argument: it's true the recompilation is blazing fast. But in >> the developement phase it is very common to add or remove methods (on the >> server side), or to do things the JVM cannot handle without restart. So >> I've found I'm loosing a lot more time than in the emulated mode, since the >> first page display is always very very very long (above 2 minutes), and >> this gets the developer distracted and forgetting what he wanted to do. >> > > Use DevMode -noserver or start CodeServer directly. Obviously you need a > local app server then to serve your server side code. We do it that way (to > have the same production env locally) and I rarely restart my CodeServer. > Also take a look at: https://gwt-review.googlesource.com/#/c/9450/ > Actually I started the code server separately then when I launched with eclipse I found eclipse was launching the code server with no need for my separate launch. I therefore assumed it was kind of harcoded in the plugin. The most stressing point on this is that I have to guess to understand what is happening. Documentations are quite brief with step by step description but no explaining that -noserver will allow you to launch your code server alone. I know how hard it is for someone who knows well a product to write a lear documentation, since there are a lot of assumptions that things are obvious (where actually they are not and the reader may not even know the thing exists at all). -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
