NodeGraphProcessor VS Unity-Http-Debugger

Yup! This is what I've used before for behavior trees /u/realfishwind. Though, from what I know GraphView has been abandoned in favor of a new system being built into the engine that is releasing soon. So for the past couple of years I've used a project based on GraphView called NodeGraphProcessor that currently seems abandoned. NodeGraphProcessor was maintained by one of the Unity dev iirc, so they could be working on Graph Tools Foundation, which is essentially the updated version of GraphView that is currently in preview (to my understanding). I personally have not used it, so I do not know how good it is compared to the old GraphView or NodeGraphProcessor.

It’s made from scratch for fun, using EditorGUI and Handles libraries provided by unity. If I had to do it again I would use this library : https://github.com/alelievr/NodeGraphProcessor

There's an plugin build on top of the graph package https://github.com/alelievr/NodeGraphProcessor I think it's a great start point of makiing custom node based tool.

If you wanted a separate node editor system, have you looked into extending an already existing UI setup, such as NodeGraphProcessor?

For the underlying framework are you using https://github.com/alelievr/NodeGraphProcessor or https://github.com/Siccity/xNode ? (and if not - how why did you choose to roll your own? )

🔗Repo Would love to hear some thoughts!

🔗Repo UI is mostly a copy of Insomnia but I created this tool mainly to log all of the requests in my app. There is a "Stash" tab where you can save and test REST API calls. And there is a "Playmode" tab where you can see all of the logged requests. This tool already has most of the basic functionality implemented but is not finished. I would like to hear if anybody would find this useful and if so how would they use it in their projects? Is it worth finalizing and polishing up?