Serialization: animations are view state. They can safely be left out of a serialized and persisted model.
Print out the model: True, but if you're using animation in an app, you're beyond poking at the model in the REPL. Harder to equate: My animation library provides an "equals" function. In addition to sampling the easing function, it accounts for a few other ways animations can have different representations but be considered equal (e.g. start at time t with delay k == start at time t+k with no delay). "just store the things needed to create the function" -> This is essentially the "EasingDescription" idea I talked about above. The problem is that easing functions can be created in many way (sinusoids, polynomials, exponentials, bounces) and I want to allow the client to specify any function. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
