search

rstudio / flexdashboard

Easy interactive dashboards for R
https://pkgs.rstudio.com/flexdashboard/
Other
814 stars 300 forks source link

Generate more than one html when more than one page #54

Open tosigus opened 8 years ago

tosigus commented 8 years ago

For a bigger project (more than 10 pages with heavy content and many plots) it would help when RStudio would knit more than one html output file. So that the navbar would display the page names and reference the corresponding html files (like). Now multipages only references into the html file (see). The loading times for one big html file are very high. Any hints to address this problem?

jjallaire commented 8 years ago

I agree that this would be desirable.

In the meantime you could set self_contained: false so that at least your plots will be loaded incrementally (this assumes you are distributing the dashboard on a web server not as a self contained HTML file).

On Wed, Jun 8, 2016 at 9:14 AM, Torsten Osigus notifications@github.com wrote:

For a bigger project (more than 10 pages with heavy content and many plots) it would help when RStudio would knit more than one html output file. So that the navbar would display the page names and reference the corresponding html files (like http://rmarkdown.rstudio.com/flexdashboard/index.html). Now multipages only references into the html file (see https://beta.rstudioconnect.com/jjallaire/htmlwidgets-ggplotly-geoms/#geom_density). The loading times for one big html file are very high. Any hints to address this problem?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rstudio/flexdashboard/issues/54, or mute the thread https://github.com/notifications/unsubscribe/AAGXxyCGwZSH1EybAGvvztpaMCEjDFZeks5qJsBMgaJpZM4Iw8e0 .

tosigus commented 8 years ago

Thanks, that could help.

epijim commented 8 years ago

This would be great. I have a static dashboard with a lot of D3 and plotly plots, which leads to one very large html file - splitting the pages in the dashboard into different files would make it run a lot better.

renejuan commented 8 years ago

I opened an issue (#72) related to this although not precisely the same but navigation for flexdashboard can be a little bit clunky once you try to add multiple pages. It will be great to have multiple Rmd files instead of a single long file. If is possible to create the navigation bar using the navbar argument to handle multiple pages (http://rmarkdown.rstudio.com/flexdashboard/using.html#page_navigation) then documentation for flex_dashboard navbar argument should be improved to reflect this capability.

struckma commented 2 years ago

I think, there is a need for this, because we also have use-cases here. Of course, one could move away from flexdashboard to some Rmd-web-site library like blogdown, but this would imply to completely rewrite the existing Rmd file by breaking it down to single files. By doing so, the "single-file" option is lost, only sites would be possible with the new set of Rmds.

I would like to have a solution, that works for smaller and larger dynamic outputs from the very same Rmd file only depending on the data to avoid having different sets of Rmds for analogous output only in different favours of single-page-html vs. site-html.

I think about writing kind of a decorator for the flexdashboard-package, which would pre-process a flexdashboard file. It would split the original flex.Rmd into a set of sub-flexdashboards plus a _site.yml file processable by rmarkdown. Anchor-links would be corrected in the split-files to point to the correct derived sub-file by building a dictionary of anchors and the sub-file where the anchor lives after the split.

How realistic is the implementation of this existing old issue #54 not being touched for more than 5 years now? Does somebody know of an existing solution? Is someone willing to help implementing some solution? Any alternative proposals of how to do this?

koldLight commented 8 months ago

Same here, this enhancement would be desirable. I had several projects with problems of size and performance (mainly because each page contains multiple interactive charts and maps) that could be easily resolved by dividing each page in an independant html.

I have some availability to do a PR, if there's any maintainer that can give me some guidelines about the way to include this change.