It's to sad that if i want to change a small line of code, like css on uibinder i need to recompile all the project.
Plus JSR 303 Validation annotations aren't compiled in superdev mode i will put a issue El miércoles, 14 de noviembre de 2012 02:24:35 UTC-6, StefanR escribió: > > In a larger GWT multi project app and it took me several hours to get the > new SuperDevMode running (I found this > video<http://jeff-davis.blogspot.de/2012/07/setting-up-gwt-25s-superdevmode.html>very > helpful). > Now, I'm a bit disappointed about the coolest new feature of 2.5 and I > wonder if I have missed something. > > - Compilation is slow. It takes between 1 and 2 minutes plus the > bootstrap time of my server app. The app has sth above 20k LOC and heavily > uses RequestFactory and GIN code generators, maybe that's the reason? So > overall startup performance is worse than with standard DevMode. > - Code changes require a recompile. In DevMode non-structural changes > are applied automatically by the Eclipse Debugger. > - Debugging the code in the Browser is ... hm, it works. But honestly, > nothing compare to a IDE debugger. Browsing through the source tree in > Chrome is a pain with thousands of classes. > - GWT CodeServer is very resource intensive. During compilation, I > cannot use my machine for anything else. If it's running it takes more > than > 1GB of RAM. > > Is anyone successfully using SuperDevMode for larger apps? > -- 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/-/AMpYpWpT0zYJ. 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.
