Hey, > So, I made some tests and it seems there are not that much difference using > a queue or not. That sounds good because it reduces the complexity if no queue is required.
> Anyways, it's nearly impossible to acheive obtain the same framerate with > JS... even with animationFrameRequest - when the number of dom elements > rise, the result becomes awful: animations aren't smooth and furthermore, > the visual result seems inferior to a simple global "slower" setInterval() > call. Thats what I have expected as well. But I don't see it as a big problem because its only a fallback for browsers not supporting CSS animation. They get the best experience possible. :) > I attach > http://qooxdoo.678.n2.nabble.com/file/n7298912/animation.zip my demo example > to this message if you want to have a look. Thanks. Took a quick look at it but not in detail. > PS: However, I think it would be nice to have the equivalent of > qx.bom.element.AnimationJs.stop() and qx.bom.element.AnimationJs.pause() in > qx.bom.element.AnimationCss - useful when the repeat attribute is set to > "infinite" Those methods are internal and should not be used. Every animation call returns a handle which is equivalent for both types and offers these methods. :) Regards, Martin ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
