Yes, the larger the application the more resources Development Mode consumes. I often rely on self-reviewing code and wind up compiling the application to test features. Unit testing is your friend as well, reducing reliance on the debugging functionality of Dev Mode. In one of my non-trivial GWT projects (10K LOC) I defer to debugging only when completely stuck. Finally I noticed that GWT apps run much faster in Dev Mode on Firefox then in Chrome.
I'm placing high hopes on the upcoming Super Dev Mode<http://tbroyer.posterous.com/how-does-gwts-super-dev-mode-work> alleviating the problem. Boris On Tuesday, June 19, 2012 8:21:46 AM UTC-4, Magnus wrote: > > Hello, > > I still have no solution for this problem. Running and debugging web > applications from within eclipse ist very slow, so that one cannot really > work on the project anymore. > > Do others have this problem, too? > > Magnus > On Tuesday, June 19, 2012 8:21:46 AM UTC-4, Magnus wrote: > > Hello, > > I still have no solution for this problem. Running and debugging web > applications from within eclipse ist very slow, so that one cannot really > work on the project anymore. > > Do others have this problem, too? > > Magnus > On Tuesday, June 19, 2012 8:21:46 AM UTC-4, Magnus wrote: > > Hello, > > I still have no solution for this problem. Running and debugging web > applications from within eclipse ist very slow, so that one cannot really > work on the project anymore. > > Do others have this problem, too? > > Magnus > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/s6X-25FWWcsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
