`demo/` folder to host your example files about detourr HOT 7 CLOSED

Can you write a small demo of {detourr} with Shiny?

from detourr.

I'll look in to it

from detourr.

Using detourr with Shiny will require a few changes:

• the renderValue method will need to be modified to prevent duplicate elements from being drawn each time it's called
• shiny bindings will need to be added. I'll need to find a way of doing this that's generic across widgets.
• Using shiny gives some alignment issues between axes and axis labels

from detourr.

I've run in to a slight problem with Shiny, and I'm not sure the best way to work around it.

In order to get the widgets to work with both shiny and crosstalk, I need to write some shiny bindings. For example, for d3scatter, the following bindings are used, both of which get called from a shiny app:

d3scatterOutput <- function(outputId, width = '100%', height = '400px'){
  htmltools::attachDependencies(
    tagList(
      shinyWidgetOutput(outputId, 'd3scatter', width, height, package = 'd3scatter')
    ),
    crosstalk::crosstalkLibs()
  )
}

renderD3scatter <- function(expr, env = parent.frame(), quoted = FALSE) {
  if (!quoted) { expr <- substitute(expr) } # force quoted
  shinyRenderWidget(expr, d3scatterOutput, env, quoted = TRUE)
}

The problem I'm having is that the first function requires the widget name, but we don't know the widget name until we know the display method and dimension of the tour.

This can be inferred in the second function because we have expr, which is the call to animate_tour, and we can extract these values. But the first function only has the output_id which isn't enough to infer the widget name we are using.

@earowang Do you have any experience with writing shiny bindings, and can you suggest how to work around this issue? Ideally the widget name would remain hidden from the user.

The shiny example I'm going by is here: https://rstudio.github.io/crosstalk/shiny.html#:~:text=Adding%20reactive%20outputs

from detourr.

Looks like shinyWidgetOutput() requires one function corresponding to one widget. I don't have any examples in my mind that can help with this. Maybe decompose animate_tour() to two functions?

from detourr.

Any updates on this?

from detourr.

For shiny, I'll create wrapper functions that require passing in the widget name, e.g. display_scatter_3d. I intend to work on that this weekend

from detourr.