Drag cells from console to notebook

[vidartf]

After playing around in the console trying to figure out how to do something correctly, it would be nice to be able to drag and drop the cells (at least the input) back into a notebook.

Similar to #3221.

[ian-r-rose]

I think this might be a good issue for an advanced new contributor. It would involve listening for drag events on the console cells, and when one starts, setting the jupyterlab cell mime data in the drag mimebundle. The notebook itself already has listeners for dropping the cells, so it could be done entirely on the console side, I think.

For reference, the reimplementing the notebook function _startDrag in the console would be a good place to start.

[sivakar12]

I'd like it give this a try. Is anyone already working on it?

[blink1073]

Please do!

[askerry]

@sivakar12 are you actively working on this? was thinking I'd pick it up if you aren't.

[ellisonbg]

Ohh, this would be awesome!

…

On Fri, Oct 26, 2018 at 2:58 PM askerry ***@***.***> wrote: @sivakar12 <https://github.com/sivakar12> are you actively working on this? was thinking I'd pick it up if you aren't. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4847 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABr0DtvWVTIQks2BX-S2_vL2n7frkPyks5uo4WMgaJpZM4VGTjE> .

-- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub bgranger@calpoly.edu and ellisonbg@gmail.com

[sivakar12]

@askerry I'm not. You go ahead

[bollwyvl]

Recently wanted this, too. Having inspector, sidecar and console open could be a totally different, and refreshing experience. Both directions would actually be great, if that made any sense: dragging a cell from a notebook could immediately run it, or just update the current text. Similarly, if dragging multiple cells, it could run all but the last one. This could play out in commands: not sure if "new console for notebook" copies the current cell, or if they know about each other start the fact, but this seems like a "special" relationship. Anyhow, "append last console as new cell", "append console history as new cells" with appropriate shortcuts would round this out at the keyboard level, sort of the inverse of scratchpad. Another super fly feature would be if inspector code blocks/selections could be dragged in as new cells... Beautiful to imagine docstrings being easily reusable that way. Indeed, it might make sense to reimagine docs _as notebooks_.

[Madhu94]

@askerry I'm sorry I didn't see this thread for some days and I got something working here-#5585. My mistake, I should have checked before I began work on this.