The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

Custom controls

Julien Barnier

2023-02-15

Customizing labels

If you want to keep the default controls but just changing the default labels, you can use the previous_label and next_label arguments of glide(). You can pass them any HTML or shiny tags combinations. For example :

ui <- fluidPage(
  titlePanel("Basic shinyglide app"),
  glide(
    next_label = paste("Next screen", icon("play", lib = "glyphicon")),
    previous_label = span(style = "opacity: 0.5;", "Go back"),
    
    screen(
      p("Please choose a value for n :"),
      numericInput("n", "n :", value = 100)
    ),
    screen(
      p("Here is your plot :"),
      plotOutput("plot")
    )
  )
)

server <- function(input, output, session) {
  output$plot <- renderPlot({
    hist(rnorm(input$n), main = paste("n =", input$n))
  })
}

shinyApp(ui, server)

You can also use the controls_position argument to place at the "top" or at the "bottom" of the glide.

Custom controls

If you want to change more than the controls labels, you’ll have to use your own custom controls. This is done by passing their definition to the custom_controls argument of the glide() function.

To define custom controls, you can use one of the helpers functions :

There is no obligation to use these helpers function, you can build your own layout and controls. The only constraint is that the “back” control must have a prev-screen CSS class, and the “next” control a next-screen CSS class. Note that the labels of these controls are defined via the next_label and previous_label arguments of glide().

Here is an example which uses the glideControls() helper. Note that it is not necessary to add the required prev-screen class when using prevButton().

controls <- 

ui <- fluidPage(
  titlePanel("Basic shinyglide app"),
  glide(
    custom_controls = glideControls(
      prevButton(class = "btn btn-warning"),
      tags$button(class = "btn btn-success next-screen")
    ),
    
    screen(
      p("Please choose a value for n :"),
      numericInput("n", "n :", value = 100)
    ),
    screen(
      p("Here is your plot :"),
      plotOutput("plot")
    )
  )
)

server <- function(input, output, session) {
  output$plot <- renderPlot({
    hist(rnorm(input$n), main = paste("n =", input$n))
  })
}

shinyApp(ui, server)

And here is another example with a custom layout :

controls <- fluidRow(
  div(class="col-xs-6 text-right",
    prevButton(class = "btn btn-warning")
  ),
  div(class="col-xs-6 text-left",
    nextButton(class = "btn btn-success")
  )
)

ui <- fluidPage(
  titlePanel("Basic shinyglide app"),
  glide(
    custom_controls = controls,
    controls_position = "top",
    next_label = "Go next",
    previous_label = "Go back",
    
    screen(
      p("This is a sample custom controls app")
    ),
    screen(
      p("Please choose a value for n :"),
      numericInput("n", "n :", value = 100)
    ),
    screen(
      p("Here is your plot :"),
      plotOutput("plot")
    )
  )
)

server <- function(input, output, session) {
  output$plot <- renderPlot({
    hist(rnorm(input$n), main = paste("n =", input$n))
  })
}

shinyApp(ui, server)

You can also take a look at the sample custom controls app and at its source code to see a way to implement a rather different controls styling and positioning.

First and last buttons

When using custom controls, you can define controls that will be shown only on the first and last screens. In general they are used in place of the Back and Next controls which are hidden on those screens.

To do this, either manually define an element with a first-screen or last-screen CSS class, or use one of the two firstButton() or lastButton() helper functions.

Here is an example :

controls <- glideControls(
  list(
    prevButton(class = "btn btn-warning"),
    firstButton(class = "btn btn-danger", "First screen !")
  ),
  list(
    nextButton(),
    lastButton(
      class = "btn btn-success", 
      HTML(paste("Last screen...", icon("ok", lib = "glyphicon")))
    )
  )
)

ui <- fluidPage(
  titlePanel("Basic shinyglide app"),
  glide(
    custom_controls = controls,
    
    screen(
      p("Please choose a value for n :"),
      numericInput("n", "n :", value = 100)
    ),
    screen(
      p("Here is your plot :"),
      plotOutput("plot")
    )
  )
)

server <- function(input, output, session) {
  output$plot <- renderPlot({
    hist(rnorm(input$n), main = paste("n =", input$n))
  })
}

shinyApp(ui, server)

Custom controls in modal

You can use a glide inside a Shiny modal dialog. This can be useful to create a sort of “assistant-like” interface is the modal is automatically shown at startup.

In this case, when defining the custom modals for your modal glide, it is recommended to create a control with a `data-dismiss=“modal”` attribute in order to close the modal at the start or at the end of the glide.

Here is an example modal controls :

modal_controls <- glideControls(
      list(
        prevButton(),
        firstButton(
          class = "btn btn-danger",
          `data-dismiss`="modal",
          "No, thanks !"
        )
      ),
      list(
        nextButton(),
        lastButton(
          class = "btn btn-success",
          `data-dismiss`="modal",
          "Done"
      )
    )
)

You can take a look at the sample modal app and at its source code to see a full way to implement it.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.