Closed datakurre closed 4 years ago
The easiest workaround is to copy paste entire file into a single cell and learn cell splitting keyword to split it into practical chunks.
heh. well, i have been avoiding doing new code work specifically for RobotLab, but...
.robot
and .resource
files, e.g. Open as Notebook
, and do all the plumbing for splitting, etc. in-browser. Of course, it would end up being another parser, though we might be able to re-purpose some of the stuff from the syntax highlighter.Also, apropos of nothing, I might rep RobotLab at the community call tomorrow. Folks would be familiar with Jupyter stuff, but less so with Robot. Part of it would just be "Hey, you can distribute complex Jupyter-y things that aren't just python".
I would expect that there has been similar ideas for imports Python source files 🤔
I agree on that we really should not hurry on cluttering the interface with. we buttons.
I should look into getting robot support into jupytext. That’s definitely higher priority.
Jupytext should do this now in RobotLab 2019.12.0. Although, the resulting notebooks needs joining of cells to make the notebook usable. But that would be an issue for jupytext (for us) to provide better robot => notebook conversion.
Is there a hook in Jupyter that would allow us to import a raw source file?
Sure a good experience would not be trivial, because we should split the source into cells in some sane way. It could require parsing and generating the file.