I think it might be a good idea to also reference the -localWorkers flag. I find that it cuts down on my startup time significantly (especially on my desktop which is quad-core, but even on my dual-core laptop). With OOPHM I find this to be particularly more annoying because the browser freezes on startup while the server is compiling the code.
Also, perhaps a mention that every refresh of the page launches a fresh compilation of the code & thus the browser locks up for a while there as well. The other thing I noticed is that after changing client-side code & refreshing, although the debugger claims the source is out of sync, it works perfectly with the changed code. On Tue, Mar 24, 2009 at 3:20 PM, John Tamplin <[email protected]> wrote: > On Fri, Mar 6, 2009 at 7:27 PM, John Tamplin <[email protected]> wrote: > >> I will write up a document next week about how to use OOPHM with trunk (it >> isn't going to be usable with 1.6). > > > Sorry for the delay, but I finally got around to writing it up -- see > UsingOOPHM <http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM>on > the wiki. Let me know if that doesn't address any issues you have. > > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
