add a 3d vector class (new one or extend the current `me.Vector2d()` one

[obiot]

to be used to provide a true 2.5D implementation, as the vector z property could be used to replace object.z property in a more standard way, and will be then more useful for the webGL implementation.

[parasyte]

👍👍 Because +1 is not enough

[obiot]

here they are ! I'm not really sure though on when or not to include the z value for the more advanced mathematical functions. Any advice/opinion ?

Also I did not use them yet, i'm waiting until we are clear on the here above question.

[obiot]

i was thinking as well that maybe we should make the z parameter optional for every function, just to make it easier when using vector2 with vector3d object ?

typically to manage this case :
https://github.com/melonjs/melonJS/blob/master/src/physics/body.js#L495

[parasyte]

What I like about Vector3d is that we can move the z property off of Renderable and into pos

[obiot]

Same for me, i have the exact same goal :p

On 29 mai 2015, at 21:48, Jay Oster notifications@github.com wrote:

What I like about Vector3d is that we can move the z property off of Renderable and into pos

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