issue_comments: 357347198
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/pull/1820#issuecomment-357347198 | https://api.github.com/repos/pydata/xarray/issues/1820 | 357347198 | MDEyOklzc3VlQ29tbWVudDM1NzM0NzE5OA== | 4160723 | 2018-01-12T20:36:20Z | 2018-01-12T20:39:21Z | MEMBER |
Yes we could, but I was indeed thinking more about the expandable/hide-able part. With pure html/css the hidden/shown container must be child or sibling of its controller, and I don't know how to achieve that with our current layout design using a table.
Even considering that tkinter is already shipped with CPython as part of the standard library? My concern with an arbitraily fixed column-width is that it should be wide enough to cover a reasonable range of use cases, but when the variable names are really short (it occurs often in examples, e.g., 'foo', 'x', 'y'...) it won't look very nice (I haven't tested it yet, though). I guess we can also calculate the width by hand considering the worst case scenario in order to have a good margin...
That solution (JS included) would be nice if we can support all notebook front-ends without any extra installation or configuration step. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
287844110 |