nirguk

# credit Joe Cheng / jcheng5 / https://gist.github.com/jcheng5/1283baec96c05a65778d931a8b7c7314
# for mirai cancel concept
library(shiny)
library(mirai)
library(promises)
library(bslib)
library(R6)
# SETUP ####
# Define a subclass that inherits from ExtendedTask
MiraiExtendedTask <- R6::R6Class(

jcheng5

Accepting POST requests from Shiny

(This post was motivated by a talk by @jnolis at CascadiaRConf 2021)

Recent versions of Shiny have an undocumented feature for handling POST requests that are not associated with any specific Shiny session. (Note that this functionality is missing our normal level of polish; it's a fairly low-level hook that I needed to make some things possible, but doesn't make anything easy.)

In a nutshell, it works by replacing your traditional ui object with a function(req), and then marking that function with an attribute indicating that it knows how to handle both GET and POST:

library(shiny)

stla

var groupedBarChartBinding = new Shiny.InputBinding();

$.extend(groupedBarChartBinding, {
	find: function(scope) {
		return $(scope).find(".amGroupedBarChart");
	},
	getValue: function(el) {
		return $(el).data("data");
	},
	getType: function(el) {

jcheng5

library(shiny)

# WARNING: This sketch does not make proper use of the "state" parameter.
# Doing so usually involves using cookies, which can be done with the
# Rook package but I have not done that here. If you choose to use this
# approach in production, please check the state parameter properly!

APP_URL <- if (interactive()) {
  # This might be useful for local development. If not, just hardcode APP_URL
  # to the deployed URL that you'll provide a few lines below.

mine-cetinkaya-rundel

# An example based on http://shiny.rstudio.com/articles/dynamic-ui.html

library(shiny)

ui = basicPage(
  fluidRow(
    actionButton(inputId = "add_buttons", label = "Add 5 Buttons")
  ),
  uiOutput("more_buttons") # this is where the dynamically added buttons will go.
)

bborgesr

# -------------------------------------------------------------------
# ------------------ REACTIVES INSIDE FOR LOOPS ---------------------
# -------------------------------------------------------------------

# -------------------------------------------------------------------
# --- EXAMPLE 1: this works fine, because there are no reactives in -
# --- the for lopp --------------------------------------------------
# -------------------------------------------------------------------
library(shiny)

hrbrmstr

#
# This Shiny web application demonstrates the use of custom image files
# in place of icons for value boxes in Shiny Dashboard by overriding two
# functions:
#
# 'icon' from the shiny package and 'valueBox' from the shinydashboard package.
#
# Each function adds minimal, specific additional handling of image files.
# Note: A custom css file must also be included so that value boxes can
# display the icons. For that reason, do not expect images in place of icons to

leonawicz

#
# This Shiny web application demonstrates the use of custom image files
# in place of icons for value boxes in Shiny Dashboard by overriding two
# functions:
#
# 'icon' from the shiny package and 'valueBox' from the shinydashboard package.
#
# Each function adds minimal, specific additional handling of image files.
# Note: A custom css file must also be included so that value boxes can
# display the icons. For that reason, do not expect images in place of icons to

tbadams45

testUI <- function(id, label = "CSV file") {
  # Create a namespace function using the provided id
  ns <- NS(id)
  
  tagList(
    
    selectizeInput(
      ns('mySelect'), 'Test Select', choices = state.name,
      options = list(
        placeholder = 'Please select an option below',

tchakravarty

    user www-data;
    worker_processes 4;
    pid /run/nginx.pid;
    
    events {
    	worker_connections 768;
    	# multi_accept on;
    }
    
    http {