The Viewer Nodes

[zeffii]

Maybe a crazy idea but perhaps only the nodes that produce Virtual geometry via bgl should get the moniker Viewer (Stethoscope, IdxViewer, meshViewer), whereas Nodes that produce proper Blender Objects (Mesh, Curve ..Text) should be called Outputs.

OR . more streamlined is we have no more distinction, They all becomes Output nodes, with a mode switch to show BGL or Blender Objects..

I'm interested in getting a few prototype nodes working, and they should all inherit from a base ObjectOutput node which has common functions that Sverchok has duplicated in the all the nodes.. like

• make_unique_identifier
• parent_objects_to_unique_empty
• delete_orphaned
• apply material
• selection_update
• visibility_update
• hide_render_update
• ... etc

I find grouping to be useless, compared to parenting.. but it's easy to implement...but i'd rather not.

[ly29]

Groups in blender are just strange and awkward.

The question of handling state for these cases is also an interesting problem. There is a lot to think about regarding how to implement it. Many choices.

For example a server client structure where the acutal node code only informs some server object that manages open gl.

Or doing it in the node code and having some different class like object that is notified when execution starts and finishes.

[zeffii]

I also propose the IndexViewer is no longer a separate node, but can be switched on in those nodes where it makes sense.

[nortikin]

minimisation is cool. So if node output see what kind of data is he showing it?

[zeffii]

https://www.youtube.com/watch?v=DhS3QWKsOrw