Book Image

Web Application Development with R Using Shiny Second Edition - Second Edition

By : Chris Beeley
Book Image

Web Application Development with R Using Shiny Second Edition - Second Edition

By: Chris Beeley

Overview of this book

R is a highly flexible and powerful tool for analyzing and visualizing data. Most of the applications built using various libraries with R are desktop-based. But what if you want to go on the web? Here comes Shiny to your rescue! Shiny allows you to create interactive web applications using the excellent analytical and graphical capabilities of R. This book will guide you through basic data management and analysis with R through your first Shiny application, and then show you how to integrate Shiny applications with your own web pages. Finally, you will learn how to finely control the inputs and outputs of your application, along with using other packages to build state-of-the-art applications, including dashboards.
Table of Contents (14 chapters)
Web Application Development with R Using Shiny Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Advanced graphics options


Although renderPlot() makes it very easy to produce reactive outputs, as we've seen, it only works with the standard method of outputting graphics in R. Images from certain packages within R as well as images created outside of R will not be displayed.

Helpfully, Shiny includes a function to render all image files within a Shiny application: renderImage(). The simplest case is where you have a prerendered image that you wish to include. In the server.R file, the renderImage() call is made, returning a list with the path to the image and optionally the content type (to save Shiny from having to guess based on the file extension):

output$imageFile <- renderImage({
  list(src = "foo.png", contentType = "image/png")
}, deleteFile = FALSE)

The deleteFile argument is set to false; otherwise, the file will be removed after display. This is intended for when the image is generated within the call. The file is no longer needed, so it can be deleted after the image is displayed...