Types about sverchok HOT 13 CLOSED

So having played around and tested this it out a bit, it is time to re think slightly. Also some renaming to avoid name clashes would probably be clever.

from sverchok.

So the generator decorator solved this problem in a fine way.

Will turn this into a doc on wiki, closing since it is slightly outdated.

from sverchok.

Of course this is just a rough draft

from sverchok.

What do you mean by TopoData? Is it just a tuple of (vertices, edges, faces) like in current sverchok, or?...

from sverchok.

A virtual(?) type when both edge data or faces data could be accepted.

class TopoData(SvBaseType):
     pass

class Faces(TopoData):

class Edges(TopoData):

Edges and Faces are then in turn represented using np.array, dtype=np.uint

from sverchok.

Ah, so it's something like "edg/pol" socket that some nodes have in current sverchok. Ok.

from sverchok.

Yes, exactly.

from sverchok.

Also the idea is to start using the type data in an intelligent fashion.

from sverchok.

why not use topo data instead of faces+edges. less sockets more clear

from sverchok.

The main reason is that faces and edges are fundamentally different. It will be quite easy to remove that if feels unnecessary but more work to add it afterwards.
And also note that they are the same socket, but different types.

from sverchok.

Probably we will have to add switch with two positions (into each node): 1) use separate verts/edges/faces sockets; 2) use one mesh socket. Conversion between representations better be handled by engine.

from sverchok.

vector is originally two points, start and finish, as (1,2,3)(4,5,6) form.
Vertex can become point as (1,2,3)
maybe N4 not needed in vector and point (lets call it as point to avoid misunderstanding Vector-Vertex)

from sverchok.

or we just use 4 everywhere internally?

from sverchok.