Is the scene debugger extensible? Have callbacks we can hook into?

I’ve been prototyping a multi-user collaborative scene editor of sorts. Here is a live demo:

(folks are welcome to create a new space and try adding some entities)

The drop down supports adding a few entities/primitives to the scene, then you can click on each primitive and modify a few properties. The changes to the form are broadcast to all clients viewing the same webpage at the same time (over websockets), allowing collaborative editing of the scene.

It kind of works, but I have this nagging feeling that I’m just re-creating scene debugger, which already has a scene graph node viewer and more. Now I’m wondering if I should just make the scene debugger available to clients and somehow detect if the debugger’s form inputs have changed instead. I’m not saying this is a good idea, but I think Blender might be extensible in this way. E.g, Is there an API for the debugger to allow adding or removing of tabs/sections such that I can add a form that allows selecting primitives to insert into the scene?

Just out of curiosity, is any web UI framework (react, vue, backbone etc) used to create the debugger or nme or gui editors? Is it react or just plain javascript and or jquery?

The inspector is a react application and is located on our main repository:

So it’s technically very extensible :slight_smile:

oooh ic. Is there any preferred state management that is being used with React in the inspector and other editors? I didn’t see references to redux in there.

we dont use redux and try as a rule to use as few dependencies as possible.
it’s a simple react app, component based, with a global state object.