Renderer Inspector: Exposing `object` + `key` ?

[marwie]

Description

I'm currently working on a chrome extension for inspecting three.js scenes with an interactive hierarchy and inspector panel (related tweet with videos)

I was briefly chatting with @RenaudRohlinger who suggested to add support for the newly added Renderer Inspector which sounded like a good idea - if there's already a core API in three that lets people expose controls to certain parts of their web app it would be great to be able to also display controls in the chrome extension to properly embed it.

I've parsed through some code here where the parameter input elements are created but it seems like the target object and key are not accessible anymore. I would prefer if these were accessible so I could build my own UI and not move or copy external elements over.

Interested to hear other thoughts

Solution

Make object and key accessible as part of the parameters

Alternatives

Moving the inspector HTML elements into the extension UI might be possible

Additional context

No response

[sunag]

Feel free to create a PR about it :)

The inspector is now linked to the renderer, so I believe it would simply be a matter of storing the object/key at the time the parameters are created to be accessed in your chrome extension.