derlando / femmeshpy Goto Github PK

I kind of hoped it would not be necessary, but for meaningful visual debugging it would certainly help to have indices start at 0 and don't skip unused indices.

Since we have linkage between verts and faces now, we should be able to implement it rather conveniently.

While reading through the docs of other projects that use rhino und c-based python libraries together, I saw the approach of starting a server that runs a lib backend which can execute c-based python and streams objects via json.
This could be a nice solution to allow to run simple scripts from rhino itself.

Query results and mesh elements are all iterables over either indices or concrete types.

Instead of returning lists everywhere, we should switch to generators, where that makes sense, to allow for lazy evaluation

When testing nn-queries and data-relations of mesh elements, a visual debug representation could help a lot to find problems on more complex meshes.

I'm thinking of implementing another RhinoIO method that writes the mesh to a rhino file and stores all connectivity information as textdots on the faces / edges / nodes.

I probably con't use System.Drawing.Color in normal python, though...

Write better tests for face planes, for a subdivided polygon, all face-planes have their origin as (0,0,0), which is obviously wrong