The Chrome plugin model slows down development mode a fair amount. Note that you can ignore those hang timeout warnings that the Chrome UI surfaces--the dialog will go away once the codeserver hands control back to JS (e.g. while waiting for a long refresh).
What NPObject error specifically are you hitting? On Wed, Feb 2, 2011 at 10:12 AM, Edson Richter <[email protected]> wrote: > I've a development environment composed by NetBeans, Apache Tomcat > 6.0.30 and GWT 2.0.4. > > In the client side, I've Google Chrome and Mozilla Firefox. I gave up > on testing Internet Explorer due the amount of bugs (in IE, to be > clear). > > Google Chrome is the fastest and stable browser I've been using so > far, but for debug I can only use FireFox. > In Chrome, if I don't get "NPObject..." bug, then I get repeated > timeouts. > > My application is a business application that uses several custom > gadgets, but I don't believe this is the problem, since Firefox works > well (either to run or debug the application). Also, as I stated > before, Chrome is that fastest (but I cant debug the application). > > Can anyone help me? Is there any Chrome configuration or restriction? > Is the plugin working in Chrome for debug mode? > > I'll appreciate your help. > > Regards, > > Edson Richter. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
