github/shiny
1
1
Fork 0
mirror of https://github.com/rstudio/shiny.git synced 2026-01-10 23:48:01 -05:00
Code Issues Packages Projects Releases Wiki Activity

Remove remaining RJSONIO references

Browse Source
This commit is contained in:
Winston Chang
2015-01-22 13:15:01 -06:00
parent f54a6e8513
commit deffc90531
6 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
R/graph.R
View File

@@ -1,5 +1,5 @@
writeReactLog <- function(file=stdout()) {
cat(RJSONIO::toJSON(.graphStack$as_list(), pretty=TRUE), file=file)
cat(toJSON(.graphStack$as_list(), pretty=TRUE), file=file)
}
#' Reactive Log Visualizer

6
R/server.R
View File

@@ -9,7 +9,7 @@ inputHandlers <- Map$new()
#'
#' Adds an input handler for data of this type. When called, Shiny will use the
#' function provided to refine the data passed back from the client (after being
#' deserialized by RJSONIO) before making it available in the \code{input}
#' deserialized by jsonlite) before making it available in the \code{input}
#' variable of the \code{server.R} file.
#'
#' This function will register the handler for the duration of the R process
@@ -31,7 +31,7 @@ inputHandlers <- Map$new()
#' parameters:
#' \enumerate{
#' \item{The value of this input as provided by the client, deserialized
#' using RJSONIO.}
#' using jsonlite.}
#' \item{The \code{shinysession} in which the input exists.}
#' \item{The name of the input.}
#' }
@@ -64,7 +64,7 @@ registerInputHandler <- function(type, fun, force=FALSE){
#' Deregister an Input Handler
#'
#' Removes an Input Handler. Rather than using the previously specified handler
#' for data of this type, the default RJSONIO serialization will be used.
#' for data of this type, the default jsonlite serialization will be used.
#'
#' @param type The type for which handlers should be removed.
#' @return The handler previously associated with this \code{type}, if one

2
R/shiny.R
View File

@@ -200,7 +200,7 @@ workerId <- local({
#' \item{sendCustomMessage(type, message)}{
#' Sends a custom message to the web page. \code{type} must be a
#' single-element character vector giving the type of message, while
#' \code{message} can be any RJSONIO-encodable value. Custom messages
#' \code{message} can be any jsonlite-encodable value. Custom messages
#' have no meaning to Shiny itself; they are used soley to convey information
#' to custom JavaScript logic in the browser. You can do this by adding
#' JavaScript code to the browser that calls

4
man/registerInputHandler.Rd
View File

@@ -16,7 +16,7 @@ parse the data delivered from the client before it is available in the
parameters:
\enumerate{
\item{The value of this input as provided by the client, deserialized
using RJSONIO.}
using jsonlite.}
\item{The \code{shinysession} in which the input exists.}
\item{The name of the input.}
}}
@@ -28,7 +28,7 @@ a handler defined.}
\description{
Adds an input handler for data of this type. When called, Shiny will use the
function provided to refine the data passed back from the client (after being
deserialized by RJSONIO) before making it available in the \code{input}
deserialized by jsonlite) before making it available in the \code{input}
variable of the \code{server.R} file.
}
\details{

2
man/removeInputHandler.Rd
View File

@@ -15,7 +15,7 @@ The handler previously associated with this \code{type}, if one
}
\description{
Removes an Input Handler. Rather than using the previously specified handler
for data of this type, the default RJSONIO serialization will be used.
for data of this type, the default jsonlite serialization will be used.
}
\seealso{
\code{\link{registerInputHandler}}

2
man/session.Rd
View File

@@ -84,7 +84,7 @@
\item{sendCustomMessage(type, message)}{
Sends a custom message to the web page. \code{type} must be a
single-element character vector giving the type of message, while
\code{message} can be any RJSONIO-encodable value. Custom messages
\code{message} can be any jsonlite-encodable value. Custom messages
have no meaning to Shiny itself; they are used soley to convey information
to custom JavaScript logic in the browser. You can do this by adding
JavaScript code to the browser that calls