jcheng5

  590  pkgutil -i wget
  603  pkgutil -i gcc5gfortran
  609  pkgutil -i -y libiconv_dev
  613  pkgutil -i -y zlib_dev
  615  pkgutil -i -y libz_dev
  620  pkgutil -i -y liblzma_dev
  622  pkgutil -i -y libpcre_dev
  624  pkgutil -i -y libcurl_dev
  634  pkgutil -i -y libcurl4_dev
  647  pkgutil -y -i gmake

jcheng5

library(shiny)

ui <- fluidPage(
  numericInput("temp_c", "Celsius", NA),
  numericInput("temp_f", "Fahrenheit", NA)
)

server <- function(input, output, session) {
  c_to_f <- function(c, decimals = 1) {
    round((c * 9 / 5) + 32, decimals)

jcheng5

# BE SURE TO set your Mapbox access token with:
# options(mapbox.accessToken = "...")

library(htmltools)
library(leaflet)

mapboxgl_deps <- list(
  htmlDependency(
    "mapbox-gl-js", "0.53.0", c(href = "https://api.mapbox.com/mapbox-gl-js/v0.53.0/"),
    script = "mapbox-gl.js",

jcheng5

num_suffix <- function(x, base = 1000, suffixes = c("K", "M", "B", "T")) {
  
  if (length(suffixes) == 0) {
    tibble(
      scale_by = rep_len(1, length(x)),
      suffix = rep_len("", length(x))
    )
  }
  
  i <- floor(log(abs(x), base = base))

jcheng5

library(shiny)
library(leaflet)

#' Add a tile layer whose source is an R function
#'
#' @param tileFunc A function(x, y, z) that returns a 256x256 image object
#'   suitable for passing to `png::writePNG`.
#' @seealso [leaflet::addTiles()] for other parameters
addDynamicTiles <- function(map, tileFunc,
  layerId = paste0("leafletRaster", sample.int(9999999, 1)),

jcheng5

library(ggplot2)
library(shiny)

ui <- fluidPage(
  varSelectInput("color_by", "Color by:", diamonds, selected = "cut"),
  plotOutput("plot")
)

server <- function(input, output, session) {
  output$plot <- renderPlot({

jcheng5

# Examples:
# shiny              # Launch the Shiny app in the current directory
# shiny path/to/app  # Launch the Shiny app at the specified path
# shiny . launch.browser=F,port=8000   # Launch Shiny in the current dir with given options
function shiny {
  R --vanilla -q -e "shiny::runApp(\"${1:-.}\", launch.browser=TRUE, $2)"
}

jcheng5

library(shiny)

bigvec <- paste0("a", 1:1e5)
named_bigvec <- setNames(bigvec, bigvec)
nested_biglist <- lapply(named_bigvec, function(item) setNames(list(item), item))

test_set <- list(
  "Unnamed vector" = c(1, 2),
  "Named vector" = c(a = 1, B = 2),
  "Partially named vector" = c(a = 1, B = 2, 3),

jcheng5

To opt into a more recent version of jQuery, you can add an htmlDependency object pointing to your desired version, somewhere (anywhere) in your UI:

htmltools::htmlDependency("jquery", "3.3.1",
  src = c(href = "https://code.jquery.com/"),
  script = "jquery-3.3.1.min.js")

This example will serve jQuery 3.3.1 from the jQuery CDN. If your app needs to work with clients that won't be able to connect to the wider internet, you'll need to download the jquery-3.3.1.min.js file, put it in an app subdirectory (say, jquery), and point to the directory using the src argument.

jcheng5

1. Why use modules?
   • Reuse
   • Organization/wrangling complexity (small pieces reliably composed)
2. Functions vs. modules
   • Namespacing Shiny inputs/outputs
3. Passing values in/getting values out
   • Reactives by name vs. by value
   • ^ in both directions (arguments and return values)
4. Connecting modules

• How can module UI compose? ("higher-order" modules)