You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we now provide two different editor themes which still share most of their CSS rules, I think it would make a lot of sense to separate/modularize the CSS code (e.g. into multiple files). This would have the following benefits:
Providing the help pane styling I wrote for Tomorrow Night Bright (rscodeio) for the default rscodeio, too.
Easily allow to add new editor theme variants enlarging the available range of syntax highlighting styles. There seems to be some demand for this.
Avoiding any unwanted deviations between rscodeio's different editor theme variants and easing future maintenance of this package.
I'm everything else than skilled in "CSS land", so I don't know much about more sophisticated tools/technologies like PostCSS or SCSS/Sass. But I have a feeling that it might make a lot of sense to e.g. directly switch to a Sass pipeline.
Addendum: I just noticed there's the sass R package from RStudio that allows to compile Sass to CSS from within R. It also provides a short introduction into Sass.
Addendum 2: It might be beneficial to examine how the rsthemes package solves this. Its author was apparently crazy enough to expose all relevant CSS selectors in the rsthemes::rstheme() function assisting in the creation of new editor themes.
Since we now provide two different editor themes which still share most of their CSS rules, I think it would make a lot of sense to separate/modularize the CSS code (e.g. into multiple files). This would have the following benefits:
Providing the help pane styling I wrote for
Tomorrow Night Bright (rscodeio)
for the defaultrscodeio
, too.Easily allow to add new editor theme variants enlarging the available range of syntax highlighting styles. There seems to be some demand for this.
Avoiding any unwanted deviations between rscodeio's different editor theme variants and easing future maintenance of this package.
I'm everything else than skilled in "CSS land", so I don't know much about more sophisticated tools/technologies like PostCSS or SCSS/Sass. But I have a feeling that it might make a lot of sense to e.g. directly switch to a Sass pipeline.
Addendum: I just noticed there's the sass R package from RStudio that allows to compile Sass to CSS from within R. It also provides a short introduction into Sass.
Addendum 2: It might be beneficial to examine how the rsthemes package solves this. Its author was apparently crazy enough to expose all relevant CSS selectors in the
rsthemes::rstheme()
function assisting in the creation of new editor themes.@anthonynorth What do you think about this?
The text was updated successfully, but these errors were encountered: