Add an IPython Widget? about qgrid HOT 8 CLOSED

cc @ellisonbg @fperez @SylvainCorlay

from qgrid.

@blink1073 this looks awesome! Making QGrid a widget is definitely something we're interested in. In fact, my first inclination would be to say that the widget view should be the default interaction mode. Do you imagine use-cases where you wouldn't want the interactive components? Does the widget view incur substantial performance overhead?

At any rate, I'd love to see a PR with what you have so far.

from qgrid.

cc @TimShawver

from qgrid.

This is really cool!

from qgrid.

@ssanderson, it has about the same overhead, but widget outputs are not stored within the notebook file, which means you lose the ability to interact with the data in a static view.

from qgrid.

but widget outputs are not stored within the notebook file,

Ah, that makes sense. There are cases where that's desirable though: notebooks with QGrid outputs can be much larger than normal notebooks, because we're rendering thousands of rows of data as in-line javascript object literals. I imagine that this could be made substantially more efficient by sending the data over a socket in a more appropriate serialization format and then doing the conversion to objects in Javascript.

w/r/t preserving the outputs, I wonder if what this wants is something like an Embed or a Render button that renders the output statically and writes it as HTML. That way you could work with the widget view interactively, and when you have an output you want to share/persist, you could hit Embed and have the widget view HTML/JS replaced with a static view of the data at the point when you hit the button.

I don't have a great sense of how hard that would be with the current state of the widget system, but it seems like it should work conceptually?

from qgrid.

See #27.

from qgrid.

PR has been merged to master.

from qgrid.