A lot of people are asking for a faster DevMode, is that because you are closing DevMode after every change? You don't have to do that, you can leave DevMode running for the entire day and just refresh the browser itself (while coding in whichever IDE you wish, as long as it's compiling the classes into the correct directory). If you make server side changes, you can just click the "Restart Server" button under the Jetty tab.
Furthermore, GWT 2.0 adds the "-draftCompile" flag which, according to the GWT Blog http://googlewebtoolkit.blogspot.com/2009/12/introducing-google-web-toolkit-20-now.html "If you do need to compile to JavaScript often — though hopefully development mode will dramatically reduce your need to do so — you can use the GWT compiler's new -draftCompile flag, which speeds up compiles by skipping optimizations. To be clear, you definitely shouldn't deploy JavaScript compiled that way, but it can be a time saver during non-production continuous builds." -draftCompile in addition to restrictions to the user agent you compile to (if you can afford to do that during development), should make your compiles a lot faster. Hope that helps! All the best, -- Arthur Kalmenson On Thu, Dec 17, 2009 at 3:08 PM, Konstantin.Scheglov <konstantin.scheg...@gmail.com> wrote: > > >> >> What do folks here think is important? > > +1 for faster DevMode startup. > I don't understand why it recompiles all Java classes again and > again, when Eclipse already has classes in "output" folder. > Plus performing JSNI code parsing and applying ASM converters.... > Would be great to cache all these things on disk and start... hm... > 10 times faster. ;-) > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
