Next Feature in DK Wrangle

Hey folks,

finally we can start doing what I intended this tier to be. To decide the next steps in the wrangle tool.

The wrangle seems to be a tool with much potential but there is alot to do to make it easy to use and versatile.

Here are some ideas:

A text search:

Either for the entry names or even better full text. For example type "intersect" and you get all snippets loaded into the dropdowns that use intersect in it

Merge libraries:

Tom Cushwa recently asked for it and I think that is a good idea. For example you builld your own library and I realease another version of mine. Rather than going through it by hand it would be good if you could just merge them together. With the option to either only load unknown Context, Categories and Snippets OR override already existing once with the new file.

Python Library:

I definitely plan to branch of into python. Here it would be very helpfull to have the first Dropdown to hold a class and the next one has the methods of that class. The default python window could be embedded in the same asset or created as a separate one.

Save Nodes as Code:

There is an option to save whole nodetrees as a python file. And you can load these back up. These files are a bit bigger, like 200 kb for 4-5 nodes when saved as a whole obj node.

You could use the JSON library as sort of a library of nodetree setups. It just saves the name, category and locations of these files. That would allow you to load them into your project with the same dropdown -> insert mechanic.

Kind of interesting but would be susceptible to changes like missing files or version changes. In python you use exact node names. So if you saved a nodetree with poly bevel in H18.0 you would not load the current Bevel when using H18.5 since it got updated.

But still - it could be usefull.

So get your voting fingers ready!

Cheers

Dave