Design: table vs treeview about jupyterlab-variableinspector HOT 4 OPEN

I think it is a good idea to provide a way to further inspect objects in the explorer.
We would have to think about how to provide such a method in a language independent way, i.e., that is not tailored towards one specific lang but usable in all supported languages.

But I also agree with @chappers, that this is not our immediate focus.

from jupyterlab-variableinspector.

Yes, this is very similar to the RStudio variable explorer as well, where objects can be expanded. I'll leave for lckr to give their view. I think its something we can implement into the future, with an eye on how we might do it (basically its picking up the dir output of everything variable).

My personal view is that although valuable, it is probably less valuable than:

• Sorting out support and generalising for other languages (what about Matlab/Octave kernel? this context wouldn't be useful there as you've pointed out)
• Making it easier for the community to extend this variable inspector

Of course if you know how to extend it yourself, I would absolutely encourage you to submit a PR.

from jupyterlab-variableinspector.

from jupyterlab-variableinspector.

Given who we are in this project, I doubt we have the clout to influence future architectural decisions related to Jupyter...

Since that project is talking about large architectural decisions (potentially breaking this extension + many other extensions) and roadmaps years down the track - I'll be leaving it alone for now.

from jupyterlab-variableinspector.