You said "any browsers", so it's not clear which one you use for primary development. GWT DevMode is very slow in Chrome, but it's perfectly acceptable in Firefox. Also, you pay most of the cost up front in the first load; reloading your browser page after making changes is very fast.
Also, when you do need to test production mode JavaScript (e.g. for Mobile Safari, which doesn't have a DevMode), you can tell the GWT compiler to only build a single target (e.g. webkit) by including a line like this in your *.gwt.xml file: <set-property name='user.agent' value='safari'/> On Sep 5, 10:26 am, John Wheeler <j...@highvolumeseller.com> wrote: > The cross-browser time-savings are completely diminished when you take into > account OOPHM or hosted mode development in ANY of the browsers with ALL of > the optimizations on stackoverflow, in the newsgroups, etc. It is incredibly > slow and frustrating. > > People considering GWT development need to know that the hosted mode and out > of process plugins are essentially worthless because once your app gets to > one or two screens, you'll be deploying to live everytime you want to test. > This just sucks for app engine apps which take over a minute to deploy. I > don't like having to wait 5 minutes for compile/test cycles. > > Seriously, it takes 5 seconds for a button to click. Do you guys plan on > doing anything about it ever? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
