Hello again!

After managing to run examples i'm seriously thinking of using cocos
for my project(will write about it later, have few questions if u
don't mind;).

First thing which making me nervous is that all examples using static
sprites. I know that it is possible to use gif, but it's still static
in a way. Can i compose sprites from different elements, mixing files
and primitives for example? Also, i've found svg implementation for
pyglet, i saw your messages there, Lucio, so, is it possible to use
svg in cocos? I think it will be very good thing for this library, in
a way it looks like it's enough strong and at the same time easy to
use not only for games, but for reach graphical interfaces for
example, like special libraries like clutter or pigment(i was trying
to install their python bindings, no luck), and vector graphics
support will make it even more useful. I'm planning to make some kind
of experimental audio-visual software if say true, interface will be
physics driven, and i also like to port it to iphone later, so cocos2d
almost winner already...

For better svg support will be nice to have methods for getting child
elements from file and be able to transform them inside of sprite (in
this case svg will act like container for shapes, o elements, also
good for games i think).

Thank you!

p.s. i probably need to read programming guide first, but really
excited want to know all that stuff:) I was trying Processing and
Nodebox, but both limited in different ways...i think you guys must
check clutter, your library really looks somehow similar, may be we
can try to create version for more RGI(not sure if term excists, haha).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"cocos2d discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/cocos-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to