On Tue, Mar 24, 2009 at 3:59 PM, Vitali Lovich <[email protected]> wrote:
> 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. > I don't know that the OOPHM document is the right place to discuss other compiler flags. Also, I don't think -localWorkers will have any impact on hosted mode at all, since it is used to compile different permutations in parallel. it will speedup web-mode compilation if you have more than one permutation, but nothing for hosted mode. > 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. > It is doing a bytecode compile (including of generated code), not a web-mode compile, so it should be very long unless you have a really large app. There is a project we call instant hosted mode which will allow reuse of your IDE's bytecode compilation rather than having to recompile, but it isn't ready yet (soon though). > 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. What IDE are you using? I know there are issues with hot-swap between JDT and Javac, so if you aren't using Eclipse you may have some hot-swap issues (Eclipse and GWT both use JDT), which allows you to change some classes without doing a refresh. That is independent of a refresh, which is basically tossing the running classes and reloading them. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
