Hey Brad, Sorry about that, I've just seen a number of people in the IRC channel asking about why DevMode was so slow and it turned out they had been closing it after each check. I just wanted to throw that comment up there for those that didn't know. I guess our apps haven't got to that size yet....
All the best, -- Arthur Kalmenson On Fri, Dec 18, 2009 at 9:50 AM, Brad Leupen <[email protected]> wrote: > Arthur, > > No, we are not closing DevMode. Our client app is not small. > Refreshing DevMode in 2.0 takes 20-30 seconds on a decent multi-core > workstation. Often, we are only able to refresh a handful of times > before we start running into out-of-memory exceptions and browser > crashes (FF 3.5.6). I don't want to sound unappreciative - DevMode in > 2.0 is MUCH MUCH faster than before. We are very excited about this. > However, I rarely need to use the debugger in the actual client. Most > of the time I just want to refresh the layout or test the usability of > a widget. For this, DevMode is overkill and, in fact, useless for > testing real world UI latency. > > Draft Compile is a wonderful idea but even it takes over a minute to > compile a single permutation of our app. > > At the end of the day, all i want to do is make a small change to a > widget and refresh my browser to test the layout, look and feel, and > usability. over and over and over. Sometimes i might need to debug my > ui logic but not most of the time. > > Brad > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
