Got it. I liked `zazz.march` exactly because of its simplicity :) The only thing lacking for my use case is "halting" the animation (or all animations currently managed by zazz) . I don't know how it fits with your architectural vision for the zazz module, but it would be nice if it exposed some kind of a `purge` method that just stops any active animations managed by zazz (by purging its internal state). Or, better off, a method for "unregistering" individual targets that are currently being animated.
Anyway, I'll be looking for workarounds. Thanks!