So it's not necessarily not having interruptible animations, it's more all 
the code that you'll need to manage them.  

In elm-style-animation you can just start a new animation and interruptions 
are handled automatically.

When you have description and state split, you have to juggle switching out 
the animationDescription at the right time.

view model =
      animate animationDescription model.animationState

becomes the following when you have multiple possible animation 
descriptions.  Lets say we have model.animId to keep track of what 
description is running so we can switch between them.

view model =
        myAnimationDescription = lookup model.animId
        animate animationDescription model.animationState

Easy peasy.  

What about when you want to have a delay and then an interruption, you have 
to keep track of the delay and switching out animationDescription when the 
interruption occurs.  Great, we can do that.

You also have to implement logic that handles what happens when multiple 
delayed interruptions are queued up.  So now you have a queue of animation 
interruptions to manage.  Ok then.

Basically all of this is totally writable's just that that's a 
large part of the built in functionality of the elm-style-animation 
library.  Why write all that code if a library handles it out of the box?

On Thursday, October 13, 2016 at 3:25:17 PM UTC-4, Zinggi wrote:
> @Frederick
> Yes, that's where I got my inspiration from ;)
> @Matthew
> I don't think this is a problem, but I also don't understand what you mean 
> by "you'd have to do all the interruptions manually".
> Could you elaborate?
> I haven't studies your library closely, so I don't know how your library 
> currently deals with interruptions.
> I once created an animation library for react 
> <>, it kinda works like I described 
> above and it does have interruptable animations.
> But of course react doesn't map nicely to elm.
> On Thursday, 13 October 2016 21:02:29 UTC+2, Frederick Yankowski wrote:
>> The elm-autocomplete package does something much like you describe. 
>> Configuration data, including some functions, is defined separately from 
>> the model and is passed as an additional parameter to the update function.
>> On Thursday, October 13, 2016 at 1:34:29 PM UTC-5, Zinggi wrote:
>> I think it would be nice to separate the *descriptions* of an animation 
>>> from the *state* of an animation.
>> ‚Äč

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 
For more options, visit

Reply via email to