Aha, my bad. Yes, for certain scenarios it makes sense to have a drag/drop paradigm, for some a REPL++ like Jupyter, and sometimes an Editor. That's exactly why we decided to integrate Jupyter w Azure ML. This is going the other way around and makes total sense. The ideal as you've noted is figuring out how to integrate the three canvases intelligently so that you don't have to "alt-tab" between disjoint worlds constantly. Meanwhile I've added it to the feature list:
Comments
Aha, my bad. Yes, for certain scenarios it makes sense to have a drag/drop paradigm, for some a REPL++ like Jupyter, and sometimes an Editor. That's exactly why we decided to integrate Jupyter w Azure ML. This is going the other way around and makes total sense. The ideal as you've noted is figuring out how to integrate the three canvases intelligently so that you don't have to "alt-tab" between disjoint worlds constantly. Meanwhile I've added it to the feature list:
https://github.com/Microsoft/RTVS/issues/1237