4 ms·

Thanks for your answer. We changed our icon set in Spyder 3.0 to use FontAwesome, which renders well in High DPI screens. How Spyder looks in each platform dep

Thanks for your answer. We changed our icon set in Spyder 3.0 to use FontAwesome, which renders well in High DPI screens. How Spyder looks in each platform depends on Qt, but we have some additional customizations to make it look better at least on macOS. We'll try to add something like knitr as a third-party plugin in the future. We didn't know it's so important to have it.

jbmorgado 10y ago
How that's great. I saw something in the roadmap of Spyder some months ago about markdown, so supporting knitr would be perfect. But from what I know knitr already is supposed to work with python, it's just a question of adding the special keywords knitr uses when you have markdown in Spyder. Also, since you mention you didn't had idea about knitr importance: It's normally one of the strong points presented when discussing Python vs R for data science. Knitr makes it much easier to present (and now the RStudio notebooks make it also much easier to explore data) your work and to adopt a literate programming approach since you don't have to keep a Jupyter Notebook and then hack a Markdown/Latex document on the side where you are inserting just some plots and just some code and just some output from your Jypyter notebook that's actually relevant for the presentation or publication you are doing (and then having to remember to change parts of it whenever you change something in the code and the output changes).
- ccordoba12 10y ago
  Very interesting, thanks a lot for your input! But you're probably aware that you can also generate PDFs from Jupyter notebooks. So I guess the advantage of knitr over notebooks is the ability to easily version control markdown docs. Are there other advantages you'd like to share?
  - jbmorgado 10y ago
    I think the great advantage is not really that. (With a bit of trouble you could already output HTML/PDF from an iPython notebook and remove the output in order to make version control easier (although that's fully automatised with markdown/knitr in RStudio)). But the big selling point is that you can choose which parts of your notebook to include in the HTML/PDF output. Input, output, plots, you can write a document for a scientific paper, presentation or even a book and not have to show all the code, or all the output or all the plots like you must do with iPython. That's the really strong point with knitr.
    - ccordoba12 10y ago
      Ok, I understand things better now. Thanks a lot for taking the time to go through this :) There have been long discussions about hiding output or code from Jupyter notebooks throughout the years but (unfortunately) they haven't derived on a final decision from the Jupyter team. In any case, your feedback is a very strong motivation to start working on this in Spyder. Thanks a lot for it! We have several things planned already for the next six months, but we'll try to have an initial implementation of a knitr equivalent before the summer of next year :)
      - jbmorgado 10y ago
        These are really great news. Thank you. I would still suggest that you would look into knitr before, since it already supports other languages besides R (although I can't understand if so extensively as R) so perhaps it would be easier to just build from that.

jbmorgado 10y ago

How that's great. I saw something in the roadmap of Spyder some months ago about markdown, so supporting knitr would be perfect. But from what I know knitr already is supposed to work with python, it's just a question of adding the special keywords knitr uses when you have markdown in Spyder. Also, since you mention you didn't had idea about knitr importance: It's normally one of the strong points presented when discussing Python vs R for data science. Knitr makes it much easier to present (and now the RStudio notebooks make it also much easier to explore data) your work and to adopt a literate programming approach since you don't have to keep a Jupyter Notebook and then hack a Markdown/Latex document on the side where you are inserting just some plots and just some code and just some output from your Jypyter notebook that's actually relevant for the presentation or publication you are doing (and then having to remember to change parts of it whenever you change something in the code and the output changes).

ccordoba12 10y ago
Very interesting, thanks a lot for your input! But you're probably aware that you can also generate PDFs from Jupyter notebooks. So I guess the advantage of knitr over notebooks is the ability to easily version control markdown docs. Are there other advantages you'd like to share?
- jbmorgado 10y ago
  I think the great advantage is not really that. (With a bit of trouble you could already output HTML/PDF from an iPython notebook and remove the output in order to make version control easier (although that's fully automatised with markdown/knitr in RStudio)). But the big selling point is that you can choose which parts of your notebook to include in the HTML/PDF output. Input, output, plots, you can write a document for a scientific paper, presentation or even a book and not have to show all the code, or all the output or all the plots like you must do with iPython. That's the really strong point with knitr.
  - ccordoba12 10y ago
    Ok, I understand things better now. Thanks a lot for taking the time to go through this :) There have been long discussions about hiding output or code from Jupyter notebooks throughout the years but (unfortunately) they haven't derived on a final decision from the Jupyter team. In any case, your feedback is a very strong motivation to start working on this in Spyder. Thanks a lot for it! We have several things planned already for the next six months, but we'll try to have an initial implementation of a knitr equivalent before the summer of next year :)
    - jbmorgado 10y ago
      These are really great news. Thank you. I would still suggest that you would look into knitr before, since it already supports other languages besides R (although I can't understand if so extensively as R) so perhaps it would be easier to just build from that.