| library(rhandsontable) | |
| library(htmltools) | |
| browsable(tagList( | |
| rhandsontable( | |
| data = mtcars, | |
| rowHeaders = NULL, | |
| # see http://jsfiddle.net/pn3rv48p/ for another example with afterGetColHeader | |
| afterGetColHeader = htmlwidgets::JS(htmltools::HTML( | |
| sprintf( |
| license: mit |
| license: mit |
In response to visNetwork issue #6, here is some code to demonstrate how we might interactively visualize an arules object in R using the new htmlwidget visNetwork. Fortunately, arulesViz has already done a lot of the plumbing for us.
# visNetwork view of arules
library(arules)
library(arulesViz)
library(visNetwork)
Shiny Shiny.shinyapp.$inputValues acts like a store of state. I thought it would be fun to let vuejs react to changes in Shiny input values. This example is intentionally very simple to hopefully self-explain.
I have assembled vueR package, like d3r and reactR, to offer helpers for vuejs. For this example please install vueR, or just add tags$script(src = "https://unpkg.com/vue@2.2.6") to the tagList().
devtools::install_github("timelyportfolio/vueR")`
| #devtools::install("jeroenooms/V8") | |
| library("V8") | |
| library(pipeR) | |
| ct = new_context("window") | |
| # min.js gives me a call stack size error but non-min works fine | |
| ct$source( | |
| "https://raw.githubusercontent.com/morganherlocker/turf/master/turf.js" | |
| ) | |
| # one of the examples from turf API docs |
| require(lattice) | |
| require(latticeExtra) | |
| require(reshape2) | |
| require(quantmod) | |
| #set up horizon plots as a function | |
| horizonplot <- function(prices,horizon.type="offset",scale=0.05,title=NA,alpha=0.4){ | |
| #get change in prices since beginning or 1st row | |
| prices.change <- prices[,4]/as.numeric(prices[1,4])-1 | |
| #get as a data.frame so it will work well with melt and lattice |
| license: mit |
| license: mit |
Just playing around with svg from svglite, and I wondered if the svg output would work as reactiveValue in Shiny. Of course, it does. Then, I wanted to confirm that functions could be used for render*Output, and yes they can.
Is this useful? svg works really well in responsive contexts, so this might be helpful in that situation. Also, we could dynamically render svg spinners or animations on load or for other feedback. Let me know if you think of use cases.
functions for render*Output can help immensely.
library(htmltools)