sounds great

// wishes :)

publish/subscribe -> trigger events that know anything about each other and are capable to send data also (like time in fireEvent()). No need to search for deep nesting references to publish/subscribe with fireEvent(). An event type list where entities subscribe (~ hasmap extending of fireEvent() ? )
SVG image parser -> no need to have different image sizes or big one that is resized before first paint. Screen view can be mobile or TV. I think actual resize function that keep relative positions is great
Director capable to manage more than one scene at same time (displaying both). I know is possible to have two directors but I think then it's necessary to control directors from outside CAAT, two canvas, etc. I want scene playground and stats. When scene transition is done then ActorContainer with stats needs to be rebuild. ->
Perhaps there is a solution to this I don't know ??

// maybe useless (as browsers and hardware are continually evolving)

associate actors to canvas layers so don't need to repaint all entities when complex and big ActorContainers superpose (better performance), like setZOrder with layers (many functions pass ctx as a parameter, so maybe is not as difficult as it should be).

// dreams

video actor (I think performance will go down if it's not in
record animation to video (save an image on each render depending on fps to have an image sequence). Usefull on whammy.js or Node+CAAT+ffmpeg at server

One question: is possible to override easily a paint function outside module ? like bezier path paint for example.

(sorry if there are mistakes in my english)

CAAT future #124

Description