how about an answer to just the first one?
- The compositionReady event only fires once, so you know you can stick in initialization code in that place and it will execute that code before it begins the timeline. If you put code in at 0:00, it is still a valid time on the timeline, so the trigger will execute if you jump to that place in the timeline. So, depending on when you want your code to execute (just once, or multiple times during the life of the animation), you can choose either the beginning of the timeline or compositionReady.
- The responsive layout feature is simply that - layout that is dependent on the size of the available browser size. The timeline will continue to function in the same manner.
- You can set the logo to resize with the screen size, or you can use an external library like EdgeCommons to use a different asset entirely.
- Reflow just had its first public beta, and our team has also been waiting to see if it works... stay tuned as we figure out integration points! That being said, the way the two products handle responsive design is different.
Thats great. I'll use the compositionReady for doing my run once
configuration and inits.
Im looking forward to seeing some good responsive Animate compositions that have been 'Reflow'ed.
Especially ones with plenty of timeline based interactivity.