The great namning debacle about sverchok HOT 18 CLOSED

like in OpenGL

• vec2
• vec3
• vec4
• color3
• color4

from sverchok.

There is a certain undeniable practicality to that.

The Base type for all the vectors type is called Number4f partly inspired by OpenGL like thinking. This type is only used internally and isn't matched to any socket type.

from sverchok.

it's mostly about Vector and Matrix?

from sverchok.

Yeah

from sverchok.

Mat44 Mat33 Vec3List..

from sverchok.

aside from those being rather ugly, it's close to some shader languages i believe

from sverchok.

Hmm, I will think a bit about it.

from sverchok.

rxMatrix

from sverchok.

or hint that people should do from mathutils import Matrix as bMatrix

from sverchok.

mostly likely we won't be using Matrix from mathutils at all.. or definitely not nearly as often as 0.59 (which needs a codename at this point..)

from sverchok.

i'm happy to call Sverchok 0.5.9 " N1 " iteration 1

from sverchok.

I was also thinking that you wouldn't have to use mathutils.Vector or mathutils.Matrix as much but the bmesh api uses and exposes them a lot.

The easiest is something like slapping a prefix on all types, like rx as suggested.

The 0.5.9 will forever be reaching towards 0.6 but never quite getting there... :)

from sverchok.

I won't do the renaming for a day or two anyway so there is time to consider it enough not have to do it again.

from sverchok.

By this time next week I would like to have a basically usable system.

from sverchok.

but the bmesh api uses and exposes them a lot.

like return values from function... i'd still go for naming the return values bVector and bMatrix

from sverchok.

only because out main math system won't be mathutils.. really.

from sverchok.

that is certainly true, but still living inside blender context it is better to not clash with common names there.

from sverchok.

Will resolve this tomorrow.

from sverchok.