-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrating Quarto in shiny apps #213
Comments
cc @gadenbuie as you pointed towards here 😉 We are talking about I do think including a .qmd in a shiny app will require a fragment HTML, right ? Quarto does not have (yet) a How both you are seeing this in a shiny app context ? |
Maybe Anyway, I can broadly see the utility of this feature request but I also don't have a good sense of the scope of the feature or how people want to "integrate quarto docs inside shiny apps". My redirection came mostly from knowing that the quarto R package would be a better home for such a feature than |
This is definitely feasiblAe. Not sure what would be the benefice of making it inside quarto R package. But that is true on both side.
This is more complex because to make it correctly we would probably need a quarto format for this. Though I can make one specifically in this package by using Problem of fragment is about the feature that would be used for the quarto document. To make them work, we need the head part. We could argue some of them could be available in shiny app already, but this implies both versions should really be in sync. Hope I am clear about my current thinking... 🤔
At the end, I guess in the fragment case, I see why it would make sense for it to be in the package. This would be a quarto-r specific current format (like vignette engine). Anyhow, thanks for the feature request @davidrsch. Having more information of context and usage for such feature will help us make it happen. Thanks |
I have the idea of this feature while working on an app where I explain certain concepts about machine learning. For the explanation of these concepts I am using quarto docs. Right now I am integrating this into the app by rendering the quarto docs and embedding it's output inside an iframe. The idea of this feature it's to avoid rendering the quarto docs before building or updating the app. If I change the content of the quarto documents but I do not update the rendered version of them the content displayed won't be updated. So it would be nice to have a way to automatically include the output of quarto render into shiny apps. Right now I am using it with html outputs but I can see this being used also for revealjs presentations and other formats. |
@davidrsch in your case I understand inserting into shinyapps as an iframe is ok, and the pain point is the process for rendering.
I think the .qmd will still need to be rendered at some point. I am not sure how that would work with shiny. Do you want to edit you .qmd and then when running the shiny app, it re-rerender the doc ? I am trying to get a sense of the use case and how that would work to know which function to add in this package. |
This is the idea yes:
But now I see how there may be some downsides to this like the quarto documents rendering may slow down the app initiation |
Yes it will I think. |
From rstudio/shiny#4123 (comment). I think that adding a function includeQuarto like includeMarkdown is a good idea to make easier to integrate quarto docs inside shinyapps
The text was updated successfully, but these errors were encountered: