Conversation
I wouldnt say so - the animation system is going to be overhauled at some point - so now is a nice time to get as many things in so they dont get "lost in the shuffle" - css animations can always be enhanced "later"
Usually, i would say "yes", but here i feel like it doesnt matter so much - i doubt many (any?) people are using css animations (they are clunky - even in css3) so i think it can wait for a refactor (that wont stop the clunkiness of them ofc)
At some point (probably sooner rather than later), ill see about making all this moddable by the module.xml - that way if someone does want to an a new function they wont need to go through and modify core code like you have had to I do like the idea about "tunable easing functions" though... how would the function signature for, for example, a tunage bounce look - it maybe worth trying to get that type of thing working now.
as many as you want - the ones you have listed seem perfectly sensible to me
I dont |
|
Ok let me just add most of these then https://easings.net/ Here is a bounce definition, with the coefficients affecting how many bounces etc |

Add a few common easing functions, with a few questions regarding scope:
bouncemaybe don't need to be implemented here? As in, externally defining aFloat->Floateasing function may be more flexibleWill update formatting, unless you have something quick for that