On Sat, Apr 11, 2009 at 4:30 AM, Dean S. Jones <deansjo...@gmail.com> wrote:
> > onModuleLoad() the culprit... anytime a significant amount of > JavaScript is run, it uses the single browser thread. That same thread > is > used to run "Animated GIF's", hence they freeze while script is being > run. Breaking up the tasks will only make the GIF animation > "choppy" while waiting for an Async call to return. What does an async call have to do with this? That's networking stuff which doesn't apply here. I said used DeferredCommand with IncrementalCommand which simply keeps appending an event to be processed on the event thread while there's more work to be done. Make sure that every invocation of your incremental command takes 1/rate where rate is the fps of your gif (split it up further if it's still kinda choppy), & you shouldn't have any stuttering. Your app might take longer to load, but it'll be more responsive. > I found no easy > way around this is GWT. There is - IncrementalCommand. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
