The GWT compile process has been taking longer and longer, as I’ve moved from 1.0 to 2.0, because they keep adding optimizations and functionality.\u00a0 You could deal with this in a number of ways.\u00a0 You could write less GWT.\u00a0 You could buy a faster computer.<\/p>\n
More realistically, you could live in your IDE, and run in development (nee hosted) mode.\u00a0 However, sometimes you just have to test with javascript.\u00a0 The external browser development environment<\/a> can be tough to set up correctly, especially if your application depends on external resources, and you can run into weird bugs.\u00a0 I’m currently dealing with an issue where I depend on an external library and it is consistently throwing an assertion exception in development but runs fine in production mode.<\/p>\n If I am compiling to javascript repeatedly, I often compile for just one user-agent, which saves about 80% of the compile time.\u00a0 When I have code more put together, I can compile for all other browsers.\u00a0 This process is not flawless, as I am currently debugging a cross browser issue (something that works fine on FF doesn’t work on Safari) but I probably wouldn’t have tested on Safari until after I was through the lion’s share of development anyway.<\/p>\n The way to target just one browser is to put this string in your module (.gwt.xml) file:<\/p>\n < set-property name=\"user.agent\" value=\"safari,ie6,gecko1_8\" \/ > (remove the spaces next to the angle brackets)<\/p>\n How do you find valid values?\u00a0 Via this thread<\/a>, I found that you look in UserAgent.gwt.xml, part of the gwt-user.jar file.\u00a0 This has the javascript code that looks at navigator.userAgent<\/code>.\u00a0 It is not as fine grained as the ubiquitous browser detect script<\/a>, but shows you what different browsers are known to GWT.<\/p>\n