Open DarthSharkie opened 2 months ago
Progress is made on this in #36, #45, and #49. It isn't done, yet, but once #49 is submitted and builders are submitted, the remainder of this can be done.
I think there will be Animator
interface, CompositeAnimator
sub-interface, and BaseAnimator
superclass. It's a little unclear until the remaining unused methods are cleaned up and the decision is made on whether animators should tick
or not.
More progress made in #55 to simplify CircularAnimator
. The refactoring probably also relates to #44, since Animator
would start being called from the Scheduler, most likely.
Animators have a bit of a confusing API right now between rendering intervals and steps, delays and processing speed, and a few other functions that manipulate these values. Look to simplify and/or rework APIs to improve the interface's usability.
This likely results in being able to extract an
Animator
interface that defines the operations and values an animator must provide. ThePathAnimatorBase
likely stays around as a starting point for several implementations.