David Deraedt

Following a thread on google+ created by the famous MrDoob, I thought it could be useful to share some thoughts regarding the file size on Edge Animate projects (aka compositions).

Understanding a composition file stucture

If you're not familiar with the file structure of an Edge Animate project, I strongly encourage you to read the first part of my Edge Animate for web developer series.

But as a reminder, here's roughly what it looks like: (assuming your page was named index).

Didn't catch the live stream? Don't want to read super long official announcements?

Here's the short story. We announced:

• CSS Filter lab an experimental showcase for our contributions on CSS filters

• Adobe Edge Animate, the animation tool for the web, is now officially released and temporarly available for free

• Adobe Edge Reflow, a new tool for responsive webdesign. Preview later this year.

This is a follow-up to my previous post, Edge Animate for developers, in which we covered the technical foundation of an Edge animate composition. In this post, we'll take a closer look at the scripting features of Edge Animate with the basics of Actions and symbol manipulation.

Actions scope

Edge Animate users create code snippets called Actions to be executed in response to some events. Events can be dispacthed by an DOM element (e.g. click), a symbol (e.g. creationComplete). Some events are dispatched by the timeline when the playhead hits a certain point. Those events are called Triggers.

Now that it's almost ready for launch, I think it's time to take a little more in-depth look at Edge Animate, from a technical perspective. As it's very likely to change over time, I'll try to maintain a (totally unofficial) reference over at my github, much like I did for Brackets.