4 ms·
Hey man! Two things: 1) Complexity: While this is more for dynamic UIs than full timelined animations, it has full compatibility with every Popmotion animation
by SirHound 9y ago
Hey man! Two things:
1) Complexity: While this is more for dynamic UIs than full timelined animations, it has full compatibility with every Popmotion animation like Keyframes https://popmotion.io/api/keyframes https://popmotion.io/api/keyframes, so you can do pretty involved stuff
2) DOM-only: My biggest lesson writing Popmotion is people just want easy stuff. So for this initial release I just wanted to concentrate on the DOM. It allows me to offer things like FLIP and leverage my other libraries (Stylefire/Popmotion) which I know are small and fast. That isn't to say there'll never be native support, just that I didn't have time to do that in a month of my spare time.
- finchisko 9y agoYep no problem man. :) I do understand your reasons. It still looks awesome though. Keyframes looks promising for complex animation of single component. But what about multiple components? Like start animation of component only after some other finished its animation...
- SirHound 9y agoIf you have two posed components: <Parent><Child/></Parent> You can currently use props like `delayChildren` to orchestrate between them: https://popmotion.io/pose/learn/animating-children/#animating-children-delay-and-stagger-children https://popmotion.io/pose/learn/animating-children/#animatin... Maybe `waitForChildren` and `waitForParent` booleans would be helpful too There's an advanced way of establishing this relationship for non-heirarchal components but I haven't got to writing the docs for that yet. A CodePen example here https://codepen.io/popmotion/pen/xWrbNm?editors=0010 https://codepen.io/popmotion/pen/xWrbNm?editors=0010