Planning ? SVG, HTML, Video tags about caat HOT 2 OPEN

Hi Tuan,

this is probably the biggest wish list ever on CAAT.
As a rule of thumb, CAAT is intended to be used on gaming, though I'm in
favor of any other kind of usage. I mean I'll accept any kind of
contribution on CAAT as long as it focuses or leverages its gaming
capabilities.
About SVG, I agree it could be a big improvement for asset handling and/or
scene authoring to give support for SVG but probably i'd rather go with
integrating fabric at least to have SVG paths exported as a CAAT.Path
object abstraction. CAAT has good pathing features added out-of-the-box but
definitely a SVG parser will be interesting.
A.HTML one note about CAAT is that it should be fully compatible with
CocoonJS wrapper. The CSS renderer is about to integrate a custom TextActor
(different from one from canvas renderer) which is intended to cover text
layout topic.

Could you suggest a gaming scenario for Video, Image Filters and External
Canvas plugins ?

About point B, there's already the abbility of having multi-layer render if
using Canvas/GL or CSS, but not them alltogether. This is because the way
is built. Different renderers have different implementation for the same
objects. I can think of some solution off-the-top of my head, but right
now, CSS must run only with CSS. CAAT is multi-director oriented, so you
can layer different CSS directors and different Canvas/GL directors at your
will.

Point C definitely is something I've thought about many times. But do you
mean exporting flash assets, or rebuilding the flash stage object on JS ? I
think both of them are compelling enough. CAAT animation sequence can
perfectly support flash's one. Both manage a scene graph based on a
timeline, have hierarchically applicable affine transformations, abstract
input and paths...
Definitely will like to get deeper into this one.

About how to contribute, I accept any kind of contribution via pull
request. But unless it is a bug patch or a pending issue, I'd like to know
in advance what the suggested contribution will be about. In the other
hand, CAAT is opensource and MIT licensed, so I encourage any developer out
there to fork and start their own CAAT version ;)

Thanks for all those awesome working subjects.
Regards,
-ibon

El 11 de marzo de 2012 14:15, Tuan Kuranes <
[email protected]

escribi:

Couldn't find any planning about next feature or demos/samples, so I'll
ask here my list :

A)
SVG => using svg as Image. (or/and SVG import/export as in fabric js
canvas lib)
HTML => using foreign object inside SVG (would allow complex and automatic
text layout)
Video => ... using image/audio kind of class (streaming, events, filters),
with a Ios case that render video as div overlay.
Image Filters => on bitmap/cache/image/video/etc.
"External Canvas" plugin => ability to insert other libs (canvas latex
render, music notation render, etc/)

B) Any plans for multi-layer render (mix of css, webgl, canvas each on its
own "overlay" div), that would allow maximum flexibility, compatibility and
performance ? (like explained in Stanislas Lem google doodle making of.)

C) After the Webgl and Css, any Flash Renderer planned ?
(driving flash media from javascript)

So about each of these, would like to know if planned, or accepted as
patch (with some guidelines) :

---

Reply to this email directly or view it on GitHub:
#49

from caat.

Thanks for the detailed answer.

Could you suggest a gaming scenario for Video, Image Filters and External
Canvas plugins ?

Videos => rts units comm display, why not sprites, trailers for other games,
Filters => in game effects: damage, drugged, sleep, player success screenshot social sharing with effects
External Canvas => player stats graphics, easy other existing lib as plugin (complex text effects, fabric svg, etc), user provided plugins not forced to use caat

A => is kinda the same as External Canvas, allowing external data source (here webpages)
B => great, multidirector looks like exactly what I need. I'll check into that
C => that too, but I guess I was more speaking about a Flash Director, where flash is just a "view" controller by js (the easiest way to support legacy browsers like IE I guess)

Btw, forgot about that one, what about serialisation/deserialisation as json ?

from caat.