{"action":"created","issue":{"url":"https://api.github.com/repos/lckr/jupyterlab-variableInspector/issues/33","repository_url":"https://api.github.com/repos/lckr/jupyterlab-variableInspector","labels_url":"https://api.github.com/repos/lckr/jupyterlab-variableInspector/issues/33/labels{/name}","comments_url":"https://api.github.com/repos/lckr/jupyterlab-variableInspector/issues/33/comments","events_url":"https://api.github.com/repos/lckr/jupyterlab-variableInspector/issues/33/events","html_url":"https://github.com/lckr/jupyterlab-variableInspector/issues/33","id":343493115,"node_id":"MDU6SXNzdWUzNDM0OTMxMTU=","number":33,"title":"Design: table vs treeview","user":{"login":"fcollonval","id":8435071,"node_id":"MDQ6VXNlcjg0MzUwNzE=","avatar_url":"https://avatars1.githubusercontent.com/u/8435071?v=4","gravatar_id":"","url":"https://api.github.com/users/fcollonval","html_url":"https://github.com/fcollonval","followers_url":"https://api.github.com/users/fcollonval/followers","following_url":"https://api.github.com/users/fcollonval/following{/other_user}","gists_url":"https://api.github.com/users/fcollonval/gists{/gist_id}","starred_url":"https://api.github.com/users/fcollonval/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fcollonval/subscriptions","organizations_url":"https://api.github.com/users/fcollonval/orgs","repos_url":"https://api.github.com/users/fcollonval/repos","events_url":"https://api.github.com/users/fcollonval/events{/privacy}","received_events_url":"https://api.github.com/users/fcollonval/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-23T05:33:39Z","updated_at":"2018-07-23T08:21:28Z","closed_at":null,"author_association":"NONE","body":"I'd like to start a discussion about the layout to use.\r\nI fully understand why Matlab-like softwares use table like layout as they focus on values and originally do not have object-oriented data structure. But this is not the case in general for Python and lots of other languages.\r\nSo a tree view, like the one used in Pycharm could be a more general solution. \r\n![variables pane](\r\nhttps://www.jetbrains.com/help/img/idea/2018.1/py_view_as_array.png)\r\n\r\nIn particular, basic types are directly seen in the tree. And array can be seen in details in side panels as you have done.\r\nThe object attributes will be looked for only when the user is expanding the object leaf. "},"comment":{"url":"https://api.github.com/repos/lckr/jupyterlab-variableInspector/issues/comments/406978592","html_url":"https://github.com/lckr/jupyterlab-variableInspector/issues/33#issuecomment-406978592","issue_url":"https://api.github.com/repos/lckr/jupyterlab-variableInspector/issues/33","id":406978592,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNjk3ODU5Mg==","user":{"login":"chappers","id":2498638,"node_id":"MDQ6VXNlcjI0OTg2Mzg=","avatar_url":"https://avatars3.githubusercontent.com/u/2498638?v=4","gravatar_id":"","url":"https://api.github.com/users/chappers","html_url":"https://github.com/chappers","followers_url":"https://api.github.com/users/chappers/followers","following_url":"https://api.github.com/users/chappers/following{/other_user}","gists_url":"https://api.github.com/users/chappers/gists{/gist_id}","starred_url":"https://api.github.com/users/chappers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chappers/subscriptions","organizations_url":"https://api.github.com/users/chappers/orgs","repos_url":"https://api.github.com/users/chappers/repos","events_url":"https://api.github.com/users/chappers/events{/privacy}","received_events_url":"https://api.github.com/users/chappers/received_events","type":"User","site_admin":false},"created_at":"2018-07-23T08:21:28Z","updated_at":"2018-07-23T08:21:28Z","author_association":"COLLABORATOR","body":"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). \r\n\r\nMy personal view is that although valuable, it is probably less valuable than:  \r\n*  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)\r\n*  Making it easier for the community to extend this variable inspector\r\n\r\nOf course if you know how to extend it yourself, I would absolutely encourage you to submit a PR.\r\n"}}
{"actor":{"display_login":"chappers"}}