Created by: portnov
This adds:
- Support for "Standard" presets, which are supposed to be distributed with Sverchok (some kind of example settings).
- Support for "Per-node presets", i.e. presets which store settings of one and only one node. Such presets are displayed in the node's N panel, so when the node is selected it is possible to switch it between several pre-saved settings. Some node classes already had similar functionality (I remember Spiral and Regular Solid).
"Per-node" presets are saved in special preset categories, which are distinguished with "/Node/" title prefix. For example, category "/Node/ Box" can only store presets for the "Box" node. Such categories are created automatically when you first create a preset for the certain type of node from the node's N panel. It is possible to use the usual Presets panel under the T panel to manage such presets.
Also the list of all presets defined for the node is available in the node tree editor by Shift-P shortcut.
Difference between standard presets and Examples
Historically, our Examples menu contained examples of more or less complete setups, consisting of several nodes. Some of those examples are relatively complex. So, Examples is for examples of what can one do with Sverchok.
Per-node Presets, which are to be distributed with Sverchok, are just some combinations of settings of specific complex node, which developer thinks will be frequently used.
Standard Presets that are not per-node may be some small parts of logic that developer thinks may be frequently used. Probably it worth wrapping such pieces into Monads before packing as presets. As an example of such preset, I included Lloyd 2D monad.
Preflight checklist
Put an x letter in each brackets when you're done this item:
-
Code changes complete. -
Code documentation complete. -
Documentation for users complete (or not required, if user never sees these changes). -
Manual testing done. -
Unit-tests implemented. -
Ready for merge.