https://github.com/homerhanumat/shinyCustom
Customized versions of Shiny widgets
https://github.com/homerhanumat/shinyCustom
Last synced: 4 months ago
JSON representation
Customized versions of Shiny widgets
- Host: GitHub
- URL: https://github.com/homerhanumat/shinyCustom
- Owner: homerhanumat
- Created: 2016-01-05T16:42:49.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2018-01-08T17:54:29.000Z (over 7 years ago)
- Last Synced: 2024-08-13T07:15:06.871Z (8 months ago)
- Language: R
- Size: 27.3 KB
- Stars: 8
- Watchers: 4
- Forks: 5
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- jimsghstars - homerhanumat/shinyCustom - Customized versions of Shiny widgets (R)
README
# shinyCustom
## Introduction
This package is under development. It automates, to some extent, the creation of custom objects for the RStudio's Shiny framework.
To see an example, try:
```
install.packages("htmltools")
devtools::install_github("homerhanumat/shinyCustom")
shiny::runApp(system.file("examples/shinyapp", package = "shinyCustom"),
display.mode = "showcase")
```
At the present time the package supports three custom inputs, all of which are intended to keep the Shiny server from having to perform expensive computations that the user probably did not need. Typically this is accomplished by means of a "Submit"" action button, but in some apps the users may wish to perform so many computations that constant use of a Submit button becomes tiresome. The inputs provided in this package solve the problem by restricting the conditions under which the input sends update-messages to the server, and/or by a rate policy that the author of the app can set.
The supported inputs are:
* `customTextInput()`
* `customNumericInput()`
* `customSliderInput()`
The first two inputs are "patient", in the sense that they update if and only if the user presses the Enter key or shifts focus away from the input control.
All three inputs permit the rate policy to be customized. (For an explanation of rate policies, see [this RStudio article](http://shiny.rstudio.com/articles/building-inputs.html).
## Usage
### In a Standard Shiny App
The procedure for invoking the features of the package is inspired by Dean Attali's [`shinyjs`](https://github.com/daattali/shinyjs). Simply insert a call to `useShinyCustom()` within the UI, preferably near the top. Here's an example:
```
library(shiny)
library(shinyCustom)
ui <- fluidPage(
useShinyCustom(slider_delay = "1500"),
customSliderInput(inputId = "slow", label = "I'm a Lazy Slider!",
min = 0, max = 100, value = 0),
verbatimTextOutput("slowout")
)
server <- function(input, output) {
output$slowout <- renderText({
input$slow
})
}
shinyApp(ui, server)
```
### In an Interactive R Markdown Document
Simply place the call to `useShinyCustom()` at the beginning of the code chunk that contains your first interactive element. Make sure to set the `rmd` argument to `TRUE`.
```
useShinyCustom(rmd = TRUE)
inputPanel(
customNumericInput("number", label = "Patient Numeric Input",
min = 0, max = 100, step = 1, value = 50)
)
renderText({
as.character(input$number)
})
```
## Limitations
Currently the package cannot be with used apps in which the entire user interface is built in an `index.html` file.
This package has not undergone much testing. If you happen upon it feel free to give it a try, but do please post an issue when you find something going wrong.