Can you tel me a bit about what problems you had with CSSTransitionGroup? I was thinking of potentially adding support for CSS Transitions to Ominate, so your experiences would be useful.
Also, let me know if you have any problems or find any bugs :) On 4 May 2014 17:05, Jack Schaedler <[email protected]> wrote: > Very cool. I tried to use the CSSTransitionGroup on Goya, but it left a > bit to be desired. I'm going to try incorporating this tonight! > > > On Sunday, May 4, 2014 2:48:37 PM UTC+2, Daniel Kersten wrote: > > Just pushed an update which adds the ability to watch app-state changes > to trigger animations and specify a notify function that gets called when > the animation completes. Also "upgraded" the documentation :) > > > > > > > > > > > > On 4 May 2014 01:25, Daniel Kersten <[email protected]> wrote: > > > > > > > > Hey everyone, > > > > > > I've just pushed my little Om project to Clojars and Github :) > > It's still early in development, but I'd love some feedback on how it > should progress. > > > > > > > > > > > > Ominate allows you to animate any Om component by wrapping the component > in (ominate ...) before passing it to build, specifying duration, easing > function and animation. > > > > > > https://github.com/danielytics/ominate > > > > > > > > > > > > > > --- > > > > > > Animations are simply functions which take in a value between 0 and 1 > and the DOM node of the component being animated and then do "something" to > the DOM node (typically changing it's style). Additionally, animations may > provide begin and end functions which get applied to the DOM node before > and after the animation runs, allowing them to modify the node to prepare > for the animation and then clean up again afterwards. > > > > > > > > > > > > > > Currently, Ominate is only packaged with two animations: fading > (changing opacity over time) and color-fading (blending? - placing a color > overlay above the component and then fading that). I plan on adding many > more animations after I've finalized the API. Right now, animations are > triggered by putting a value on a channel. > > > > > > > > > > > > I'm still deciding what the final API should look like. Feedback and > suggestions welcome! > > > > > > Some ideas I'm thinking about: > > I would like to allow animations to be triggered by app state change, > perhaps by passing a cursor to Ominate and a predicate function to apply to > the cursor - when it returns true, the animation is triggered. > > > > > > Ominate should also report animation completion back to the user - a > callback passed to (ominate ...) is probably the best way to do this.It > would be cool if different animations can be "sent" to the component rather > than only supporting preset animations. > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
