| Re: [ease-dev] Jupyter Kernels |
Hi Martin, the launch configuration should use the engine that is already registered in the ipynb file. As it contains script code targeted for a dedicated engine already users should not be able to choose anymore at that step. Potentially we could store the language type only in the notebook file, then users could choose between different JS engines or between different python implementations. Christian From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] On Behalf Of Martin Klösch Hi, I am currently working on some convenience stuff for the Jupyter kernels. Most of it is related to simple UI functionality for launching Jupyter notebooks directly from the workspace. I added a new launch configuration for ipynb (notebook) files that lets users choose the script engine they want to use. Further I will implement a simple wizard for creating new notebook files. The launch will start Jupyter and open the notebook in a browser view. After an offline discussion with Christian we decided that for the first implementation we require users to have Jupyter installed manually and assure that the Jupyter command is available. In the future it might make sense to add a configuration page for Jupyter installations but this is out of scope for the GSOC project. I hope this is okay for all of you. I will keep you posted on the progress, |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature