Its only relevant if you are changing a bunch of stuff at the exact same time. Here is a real world example:
A grid, similar to EXT's grid. Capabilities with a large number of rows: Sorting, Selecting (shift select), adding, deleting, re-ordeing via drag, changing height (excel type), changing width of a column. In these cases, changing the CSS is a major speed improvement. However, does this mean you should put it in the core? Probably not. But it's a strong suggestion to any grid maker to consider this method in their plugin. Another use case: Let's say someone builds a powerpoint like app with the ability to marquee select a large group of elements and then move them. This one is a stretch, but this method should be considered there too. Another use case: Advanced dashboards. Let's say your dashboard loads up and grows the bars or charts in an identical way. This would keep the animation smoother. A big question in my mind is: On a slow machine with ONE animation: Is doing it this way smoother than not? Does CSS manipulation of a single animation make it smoother? What is the gating factor for a slow computer? CPU or Ram or Video card? Or all three? How can one test this? Glen On 7/9/07, Sean Catchpole <[EMAIL PROTECTED]> wrote:
On 7/9/07, weepy <[EMAIL PROTECTED]> wrote: > When the chess pieces appear initially, they all slide onto the board. > It's a bit jerky really - esp since its trying to move 32 x 60x60 pngs > with alpha channel. There are lots of browser limitations with working with PNGs. But more importantly, this new animation function will only speed up simultaneous animations, it will not speed up 64 different animations (if that's how you're doing it). ~Sean
