Re: GWT MVP History/Place/Activity Noticable Delay during Place Transition

2011-01-07 Thread Thomas Broyer
DevMode in Chrome is slower than in Firefox (and others) due to sandboxing of the plugin (which makes communicating between the web page and the browser plugin slower), that's a known fact. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

Re: GWT MVP History/Place/Activity Noticable Delay during Place Transition

2011-01-06 Thread zixzigma
Thank you for clarification. when I tested in production mode (rather than development/hosted mode with plugin), it worked fine. I also tried the development mode, this time disabling logging all together, Firefox seemed to have been working ok, but Chrome was showing delays. in production mode

Re: GWT MVP History/Place/Activity Noticable Delay during Place Transition

2011-01-06 Thread Thomas Broyer
Do you experience any delay in the Showcase? http://gwt.google.com/samples/Showcase/Showcase.html I don't. Showcase uses place changes rather than Hyperlink though (and I think you should do it too when using Places, as it helps decoupling the history token from the Place it represents), that be

GWT MVP History/Place/Activity Noticable Delay during Place Transition

2011-01-06 Thread zixzigma
Hello everyone, I am using GWT MVP, I have different DisplayRegions for Different Activities. when I navigate around my app, from the time the History Token changes to the time Activities start showing up in display regions, there is a noticable delay. this delay is more apparent in Chrome than i