Totally with you on this one regarding real world applications... I can't believe that you can only trigger one level of animation at a time... For example, having a page transition in as a route, but not being able to animate anything on that page at the same time, or in the case that I'm working on at the moment, collapse some content when the page transitions in, then make it expandable later. I really didn't want to go down the animation within directive route as it's not the "Angular way", and leaves code messy and non-conventional, but I can't see any other way round this. Also I can't believe that hasn't been flagged as an issue by more people in the community. Props to the Angular guys for the rest of the system... its pretty amazing, but this feature seems to be a little lacking.
On Saturday, 15 February 2014 10:09:39 UTC, Matthieu Larcher wrote: > > I have run into that issue too while trying to handle a ngview transition. > As a workaround I resorted to do part of the animation through animate() > and trigger the inner animations through a directive. > It seems to me that angular animations could be improved a lot to fit the > bill when it comes to real world requirements. Clients usually want a more > fine grained control over animations that what is currently possible using > only .animate(). > Anyhow, try to mix both animate and directives, you should be able to get > at least a step further. -- You received this message because you are subscribed to the Google Groups "AngularJS" 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/angular. For more options, visit https://groups.google.com/d/optout.
