Proposal: Share several properties in Generators between nodes

[satabol]

Some nodes in Generators has very usefull properties to general control of geometry:

I have proposal to share these properties into all nodes (where sockets and parameters has its sense). For example:

• param "direction/orientation" X/Y/Z, XY/YZ/ZX
• param "origin" to all
• param "join mode" (separate/join) for multiple objects
• input socket "scale" to all
• input socket "matrix" to all

These parameters can simplify control of source geometry in scene without using special nodes (for beginner and advanced users).

I think I can do this )))

[Durman]

My opinion is that the simpler node the better. Such cleverness has its own disadvantages:

• Every extra logic has its own impact on the node performance. There is one precise example of this when main function of the node works only 5% of the node execution time and all other time is spent in functions which add conveniens to the node usage - #4487.
• Each extra option adds complexity to the code which makes support more hard and time consuming. For example if we want to cover nodes logic with tests to cover all possible variants of node behaviour each option will multiply number of test cases at least on two. For example Line node already has at least 40 test cases (combination of its options). Adding to it proposed origin option will multiply number of test cases to 120.

I believe it's possible to find not less interesting and in the same time much more usefull areas to contribute to the code (new nodes, performance, bug fixing etc.).

[satabol]

@Durman I see problem and understand it. It may be hard. I want do it not just for me. I want do it for any current and new users too. When I use Sverchok now with my skills I know what to do but this takes very long time. Users do not want to spend so match time. So I think these changes in Generators let users spend less time to get more result at start of using Sverchok. Generators is a top used nodes in many cases - as learning of general parametrisation of Sverchok, use nodes for tests to preview some shapes and other. But many changes that they expect do with Geometry shapes now can be getted only with additional nodes. Ex. Now if you want reorient geometry other axis then you have take a "cannon" : matrix ("Matrix apply verts" or "Transform->Move/Rotate/Scale"):

This is very hard to force self do that node mesh at the start of using Sverchok. The problem that many users do not know how to use matrixes and where to find them? They just want to press a couple params to see changes and play with what they see. For example Plane node is my most favorite node: I can do many graphical changes without another nodes and this is very exciting! Just click a buttons. In background this node use matrixes with python. You understand this. But user do not know this for a while. Lets take this opportunities to another generator nodes and users will love it! And many of them may try to look and use another nodes. It's a trap. )))

For advanced user it will useful too. When I do some tests I create some cases of using with reorientation. New properties let me do some tests more quickly. But users can do their shapes more quickly too.

This is not all examples about convenience of using properties after sharing them on nodes.

This is my broad vision about attracting users to Sverchok.

[satabol]

Torus example.

• Without additional nodes:

• With additional nodes:

If parameters are placed BEFORE Torus node (to the left side of the node) is it better for understanding it?

What do you think?

[Durman]

Ok, I think it has sense to unify interfaces of all generators. But without MK next version it should be done carefully without breaking old layouts (default values should keep default behavior).

[satabol]

What names for origins is better?

Proposal 1 - use orientation XY/YZ/ZX Proposal 2 - to select origins quickly try use mouse Ctrl-Scroll and object will jump to new position around center.

[Durman]

I think it would be more meaningful to use first letters of words: Left, Center, Right.

[satabol]

@Durman But this method move objects by Z too. )

[satabol]

That params look good for instantiating:

(names for origin one can replace later)

[zeffii]

rather than sticking Orientation/Origin/Join mode as a feature on each generator, and bloating all interfaces, it makes more sense to me to add a dedicated node for those features, keeping the generator UI simple is more in line with Blender's own attitude. It could be a new version of the Mesh Join node, MeshJoin+

[Durman]

For origin mode there is Align Mesh by Mesh node.