I would encourage any effort to get an "instant compile" feature in dev mode. When designing the GUI and tweaking a widget here or there or css, a quick turn around would be a huge win. Right now, tweaking the GUI is a cumbersome process.
Chris.... On Dec 18, 10:16 am, Scott Blum <sco...@google.com> wrote: > Thanks for the feedback Brad. We've talked internally about an idea for > "instant compile" where the workflow would be essentially like hosted mode, > except it would very quickly translate your code into JavaScript with zero > optimizations. It sounds like there might be some interest in this. > > (Of course, we also want to make hosted mode much faster than it is even in > 2.0!) > > On Fri, Dec 18, 2009 at 9:50 AM, Brad Leupen <qcomps...@gmail.com> 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
