Fork me on GitHub

What techniques are there for incorporating animation into an Om app? At the moment I'm using the 3rd party "Velocity" lib and sending messages via channels but this feels too contrived


I can utilise the stock life cycle events to get something to show via did-mount. But when it came to animating the disappearance of something I thought I could just use will-unmount, however it seems the DOM element is unloaded before my animation kicks in


@teamaverage: I'm not sure if this would help or not, and I'm not 100% sold on the approach myself, but here it is:


@teamaverage: also this semi-related issue with CSS animations and core.async:


@teamaverage: would love to know what you come up with by way of a solution. How do you like Velocity?


Thanks for the link @meow I'll check it out : )


@meow: After thinking about it a little more, I can clarify by saying I know of a few ways to achieve animation but I'd like the most idiomatic way; one that doesn't go against the grain of React/Om


The simple thing I'm aiming to get working is a button-toggle dropdown where the button is a component (i.e. with its own life cycle methods) and so is the drop-down but both live in the same namespace


The latest technique is I'm just passing a map of state through to om/build when I'm constructing the drop-down. I've a function which converts this state {:show-results true/false} to a velocity call.