Wonderfl has a cool feature that allows you to edit ActionScript code and compile Flash in-browser. This encourages experimentation without the step of a download.
The other cool feature of that site is forking, which keeps track of where your code came from. This could be implemented simply on this site by adding a "forked from:" comment with url when you download a .cfdg file. More complex uses of this would keep track of how often a composition is forked and link parent compositions to children, etc.
gallery forks, render in-browser
Moderators: MtnViewJohn, chris, mtnviewmark
see wiki for version 3
Funnily enough, in response to MVJ's request for suggestions to CF3, I added a similar suggestion. Join in the discussion on the documentation wiki. (Documentation -> Recent changes is the quickest way in)
Re: gallery forks, render in-browser
This is actually off-topic from me:forresto wrote:Wonderfl has a cool feature that allows you to edit ActionScript code and compile Flash in-browser.
Since Adobe has decided not to include the ActionScript compiler in the Flash plugin, I'd hazard that the Flash application uploads your code and compiles it on the server, after which it just sends a link to the compiled swf (and all the build messages etc).
How ever, this would be a nice way to "evolve" a cfdg. Unfortunately it would put some strain on the server (depending on how many people actually use it).