aurum34 : that number is the percentage of confidence. It measures the "similarity" of the gesture you just draw against the gesture in the database.

You need to do some tests yourself to know at what limit you consider the gesture to be the same. It depends on the user, and the kind of gesture.

For example, "a square", with a number above 0.75 means it's very likely to be a square. But, for example, for a circle, perhaps you need to set the number at 0.4 (for the "circle" gesture only).

sqiddster : I didn't try, but I'm pretty sure you are going to have collisions between the two C2's namespace <img src="smileys/smiley2.gif" border="0" align="middle" />...

Since it's better to release early than to not release anything, here's the Recolor Behavior. (Some of you may have found it in the 'Creations' section).

<img src="http://dl.dropbox.com/u/1412774/RecolorDemo/demo.png" border="0">

Because of the way I implemented it, you can only have one recolor behavior per project (yes, I know, I know, it's still beta... <img src="smileys/smiley9.gif" border="0" align="middle">)

The demo : http://dl.dropbox.com/u/1412774/RecolorDemo/index.html

The .capx : http://dl.dropbox.com/u/1412774/RecolorDemo/RecolorDemo.capx

The behavior : http://dl.dropbox.com/u/1412774/RecolorDemo/pode_recolor.0.1.zip

newt asked for it on IRC, and it took me only two minutes, so here's a quick modification I added to the Canvas plugin : Overlap/Collison, like the Sprite plugin. In fact, I copy/pasted the code from the OnCollision and OnOverlap from the Sprite plugin inside the Canvas plugin (really dirty, but I don't have a lot of time to test & debug it...)

<img src="http://dl.dropbox.com/u/1412774/canvasCollisionOverlap/demo.png" border="0">

The demo : http://dl.dropbox.com/u/1412774/canvasCollisionOverlap/index.html

The .capx : http://dl.dropbox.com/u/1412774/canvasCollisionOverlap/canvas_Collision_Overlap_demo.capx

The plugin : http://dl.dropbox.com/u/1412774/canvasCollisionOverlap/canvas_Collision_Overlap.zip

I don't know if R0j0hound has the time to integrate it into the main branch, so don't forget to backup you original Canvas plugin !

All objects are in memory, all the time. If not, you would suffer massive stuttering. However, when an object is invisible, you save ressources on all calculations (when an object is invisible, you don't have to worry about polygons collisions and all that, for example).

Beany : one of the problem of SVG, is that it's a retained-mode (in contrast to Canvas - immediate-mode).

And, when you are starting to have a lot of vectors elements onscreen, browsers are going to stutter. The Flash VM handle this differently (and was built from the ground up to deal with vectors). However, browser are optimized for raster.

Although I'm the developper of the SVG plugin, I don't think a whole game made only with SVG can be good (performance wise). You need to use SVG for effects and GUI, for example, in that context.

I'm planning to add more functionnalities to the plugin, anyway.

I'm I crazy, or did I answered a message that vanished ?

Nuberudi : you don't have to do it by hand. When you have a string like yours :

584,185|584,185|584,185|584,185|577,185

you can use the method "add new template" with that string. You have nothing to do with

new Template("xxxx", new Array(new Point(91,185),new Point(93,185),new Point(95,185)

because it's javascript code !

Joannesalfa : your question is strange, because isn't it already what's C2 is doing ?

Beany : Ugotsta is right (thanks Ugotsta for the detailled answer !).

You can paste whole SVG files inside var.

You can ask — if he can do something about the newline problem.

Beany : what important feature do you feel isn't in the SVG plugin and you want to see ?

Beany : You can find some answers to your question here : http://www.scirra.com/forum/plugin-svg-canvas-vector-graphics_topic49410_post323007.html#323007