In this specific case, using the AnimationSchedulerImplTimer worked fine and is the workaround I suggested and some people have used. I would suspect that in most cases, there is never a requirement to use a prefixed API and a non-prefixed alternative could be provided, even if it might be less desirable.
Our application is used by 100s of customers and typically deployed behind their firewall. We release often, but some of our customers only update once or twice a year. If their browser is Chrome, their browser will be updated much more frequently and beyond our control.
Because of this, we would prefer not to use unstable APIs in our code.
What I would like to see is an option, either a compile flag or a property in the .gwt.xml file, to toggle the use of unstable prefixed APIs.
For certain applications, like implementing Quake in GWT (which is awesome http://www.youtube.com/watch?v=XhMN0wlITLk), it will be necessary to use some prefixed APIs.
Based on the responses to the two threads I linked above, I think there are other people using GWT who would also prefer stability over using prefixed APIs. I'd appreciate hearing your thoughts.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Post a Comment