Открыто
Задача созд. пользователемnikitronn@nikitronnВладелец

Nodes workflow requirements

Created by: Durman

Problem statement

Creating of new nodes is quite a big part of Sverckok development. It is not optimized now and has some problems. This issue is intend to clear what problems should be solved during nodes coding.

Problems

To do such tests now is nearly impossible or quite hard task. It's not only node should be created in a Blender node tree but also node should be connected with other sockets where fake data should be placed.

  • Simple reuse of node code for example in SNL scripts. #3939 (closed)
  • Porting Sverchok into another environment.

Probably someday we would like to use Sverchok somewhere else. Now with node code tightly bounded with Blender UI it's nearly impossible.

  • Suspensibility of node evaluation (require update system changes)

If we would like to have really comfortable workflow the process of evaluation of each node should be cancelable. It can be done the easier the more breakpoints it has. It also requires changing in update system and most likely they should be done first.

  • Multithreading (require update system changes) #3646 #4323

My guess is that until nodes are using socket.sv_get and socket.sv_set methods it's impossible to do any multithreading. The solution could be to put data management to update system.

  • Vectorization #3954 #4068

Vectorization code is repeated in each node and could be separated from their code.

  • Automatization of node creation (auto generating UI node code) #3437 (closed)

Some part of UI node code probably could be auto generated but as it shows previous experiment it is hard task. Probably it does not worth efforts.

  • Support muting nodes