[newhaus1994]

This feels weird at first glance, but the IDE is staying as RStudio. I love the company and all they’ve done to make data analysis more accessible, so good on them and may they succeed even more in the future.

Still not sure what Quarto is above and beyond a normal RStudio notebook, though.

[pplonski86]

Quatro is a tool for converting notebooks into shareable formats (like PDF, HTML, Docx). Notebooks are very hard to share. You can't send it to your stakeholders, because Python code will scare them. You can use Quatro to convert notebooks into other formats and easily hide the code. It is like nbconvert on steroids.

I'm working on solution for notebooks sharing with non-technical users. Similar to Quatro it has YAML header, but it can also add widgets to the notebook and serve notebook as interactive web app. My framework is called https://github.com/mljar/mercury

[hirenj]

I've been using a library to knit Rmarkdown files to OneNote API compatible HTML (https://github.com/CopenhagenCenterForGlycomics/knoter), which lets me output PDF figures (that I can download to go into Illustrator for the publication process), Excel files (which are great for validation and supplemental tables especially with wet lab scientists), and ad-hoc annotation on the document in one package (highlight text, scribble notes etc).

It would be awesome if there was a little bit more support for adding collapsible sections, and code blocks into OneNote pages so that I can look at everything in one spot.

[kriro]

You can use RISE (https://rise.readthedocs.io/en/stable/) for Jupyter notebooks to use it for presentations and also export to PDF.

[westurner]

FWIW repo2docker installs everything listed in /install.R or /.binder/install.R. I'll just cc this here because of the integration potential:

> repo2docker fetches a repository (from GitHub, GitLab, Zenodo, Figshare, Dataverse installations, a Git repository or a local directory) and builds a container image in which the code can be executed. The image build process is based on the [#REES] configuration files found in the repository.

Docs: https://repo2docker.readthedocs.io/en/latest/

  python3 -m pip freeze | tee requirements.txt

  conda env export -f environment.yml
  conda env export --from-history -f environment.yml

  python3 -m pip install jupyter-repo2docker

  repo2docker .

  # git branch -b mynewbranch; git commit; git push 

  repo2docker https://github.com/binder-examples/conda
  repo2docker https://github.com/binder-examples/requirements
  repo2docker https://github.com/binder-examples/voila #dashboards #ContainDS
 

jupyter-book/.binder/requirements.txt: https://github.com/executablebooks/jupyter-book/blob/master/...

  python -m webbrowser https://mybinder.org/

"#REES #ReproducibleExecutionEnvironmentSpecification" config files that repo2docker will build a container from at least one of: requirements.txt # Pip environment.yml # Conda (mamba) Pipfile install.R postBuild # run during build start # run in ENTRYPOINT runtime.txt Dockerfile

https://repo2docker.readthedocs.io/en/latest/config_files.ht...

repo2jupyterlite (WASM) sure would be useful for presentations, too.