CAAT future

[ixdi]

Hi,

Is there a CAAT roadmap ? or some features you want to add ?

Thanks

[hyperandroid]

Short term:

• a decent font support
• 9 patch support for frame graphics
• change audio support for a better abstraction between WebAudio and Audio objects
• change css renderer to use Matrices instead of the .top/.left rotatate, etc.
• extract the UI code in ActorContainer (layout) to a UI specific package.
• build a decent widget system on top of the UI package
• finish, or at least have a decent implementation of the tiles engine
• demo for a camera-like behavior, so i can properly show usage for built-in quadtree/spatialhash
• fix documentation generation. with the inclusion of the module and class manager, jsdoc is no more able to understand code's context
• enhance documentation. some objects have missing documentation.

Medium term:

• for Cocos2D Builder to create a CAAT exporter
• create a bones animation editor (they've support in caat as some demo shows)
• write some game templates

...

suggestions ? :)

[KraigWalker]

Ambitious!

On 7 Feb 2013, at 07:44, Ibon Tolosana notifications@github.com wrote:

Short term:

a decent font support 9 patch support for frame graphics change audio support for a better abstraction between WebAudio and Audio objects change css renderer to add Matrices instead of the .top/.left rotatate, etc. extract the UI code in ActorContainer (layout) to a UI specific package. build a decent widget system on top of the UI package finish, or at least have a decent implementation of the tiles engine demo for a camera-like behavior, so i can properly show usage for built-in quadtree/spatialhash fix documentation generation. with the inclusion of the module and class manager, jsdoc is no more able to understand code's context Medium term:

for Cocos2D Builder to create a CAAT exporter create a bones animation editor (they've support in caat as some demo shows) write some game templates ...

suggestions ? :)

— Reply to this email directly or view it on GitHub.

[ixdi]

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)

[ddon]

Great plans! Any plans to support retina screens? Or I missed it and it was done already?

[hyperandroid]

CAAT.RETINA_DISPLAY_ENABLED=true will do the magic. at least, creating a bigger canvas and downscaling it with css. it will be on your side selecting a different assets set to conform to the new resolution, etc.

• i

[arnuschky]

Hey,

• fix documentation generation. with the inclusion of the module and class manager, jsdoc is no more able to understand code's context

Yes, that is something I noticed as well. I guess it's the new object/inheritance method that was introduced in 0.5. I noticed it because my IDE basically can't resolve anything anymore. Is there any way to fix this?

Arne