Move what possible from Sverchok-Extra (WIP)

[portnov]

In this PR, I'm moving things that do not have any external dependencies, from Sverchok-Extra to Sverchok:

• Abstract classes for Curve, Surface, Field.
• Some nodes from Curve category.
• Some nodes from Surface category.
• Some nodes from Field category.

It is supposed that in the end, Sverchok-Extra will contain only things that are not possible without external dependencies.

At the moment, this PR branch is supposed to work with sverchok_move branch of Sverchok-Extra.

Preflight checklist

Put an x letter in each brackets when you're done this item:

• Core code changes complete.
• Rename SvEx* classes to Sv
• Implement __repr__() methods
• Code documentation complete.
• Documentation for users complete:
• • Curve category
• • Surface category
• • Field category
• Manual testing done.
• Unit-tests implemented.
• Ready for merge.

[portnov]

@zeffii / @vicdoval you may wish to review this :) I understand that there is a lot of code, but maybe there will be some general remarks or maybe your eye will catch something.

I'll start writing documentation...

[portnov]

[zeffii]

yikes, that's a big PR :)

i'm taking a break from Sverchok for a while, to see if I can maybe learn a compiled language before the end of the world as we know it :)

[portnov]

[Durman]

Should another shape of sockets really used? Is not using different colors is enough?

[portnov]

Why not? :)

[Durman]

Have a look at this post:
#2720 (comment)

I think it would be nice to keep the same logic as it going be in everything nodes project.
I just don't what is format of output sockets in your nodes what make them to have different shape.

[portnov]

[portnov]

[portnov]

[vicdoval]

This is awesome @portnov i looked the code (just some parts :D) an looks as good as usual,
Some ideas:
_ ensure_nesting_level does not understand numpy (until i commit #2997). It would be nice if this nodes could accept and produce numpy arrays. Maybe after my commit you want to merge it in your branch or add the line to data_structure.py (and manage later the git conflicts) to test this branch with numpy inputs

_ In the curve range node the ouputs should have one extra [ ] ?

_it would be awesome to add some routine to the stethsocope to read the new geometry types better than

[vicdoval]

Another suggestion:
Changing the imported classes suffix from 'SvEx' to 'Sv'

[portnov]

[portnov]

[zeffii]

i was looking at the Stethoscope implementation last week, and got the itch to move stethoscope specific drawing stuff back out of the nodeview callback and back into the node's own .py file.. or maybe a module. I agree with @vicdoval it would be useful to add more information / repr to objects of the SvEx classes.

[portnov]

Yes, I'll add __repr__() definition to classes.

[portnov]

[portnov]

[portnov]

[portnov]

[enzyme69]

@portnov Ilya, where should I start if I want to try all these special nodes? is there on list of every nodes like this? Is it easy to use?

[portnov]

If you're using Sverchok from git, you can do

git fetch origin
git checkout -b extra_move origin/extra_move

and then run blender as usual. After that, use git checkout master to switch to the master branch back.

Or you can just wait when this PR is merged.
I'm already thinking about merging without all the documentation and adding documentation later in the following PRs, but at least most useful nodes must be documented.

[portnov]

[portnov]

[portnov]

[portnov]

[portnov]

[portnov]

[portnov]

[portnov]

Wow. At least most of the documentation is ready. It could be of better quality, but let's leave that for future PRs..

[zeffii]

epic effort @portnov

[vicdoval]

The curve range had also a missing [ ]

[portnov]

That's already fixed.

[portnov]

[portnov]

[portnov]

Well, I guess the only way for wider testing is to merge this...

[vicdoval]

awesomeness all around... :) Are you going to publish it in Facebook, Twitter and/or Blender Artists??

[portnov]

@vicdoval I think I'll publish it in russian community in VK. Also probably in the thread on the blenderartists. You're free to publish in other sources :)

[Durman]

@portnov Great work!

[portnov]

https://gist.github.com/d9716b5f7ee1f8907b873cefcd721f03

[enzyme69]

I made #Alien Unlimited Worship Sculpture Generator using the new node :) Just less than 10 nodes.

[enzyme69]

I think we are missing Surface UV Flip node and also we need ability to output Surface with UV, like Blender Surface?

I have bunch of Circles Curves, list join, and make surface, but when I enable Cyclic, it was in the wrong direction and I was like stuck.

[enzyme69]

Question:
Can force field curve projected or affected by 3D surface or 3D volume?

[portnov]

No, there is no such funcitonality in Sverchok currently. If you install sverchok-extra, there are "minimal vector field" and "mesh nearest normal" nodes, may be they appear what do you want. Sorry, no documentation for them yet.

[portnov]

missing Surface UV Flip node
Yes, it's missing currently.

About UV maps... it would require some kind of "output" node that would output Blender's Surface objects instead of mesh object. I didn't try to make such thing, yet.

[portnov]

@enzyme69

Can force field curve projected or affected by 3D surface or 3D volume?

Maybe you are talking about "Bend along Curve Field" / "Bend Along Surface Feild" nodes?...

[DolphinDream]

Awesome job, @portnov ! This is pretty impressive. I’m looking forward to check it out.