dash-with-golem_header

2019-08-19 / Sébastien Rochette / development, docker, package, server, shiny

Dash with golem: First contact

{golem} has been developed to help building big Shiny application to put in production. What if {golem} could be used to build another popular interactive web application, recently made available to R programmers: Dash ? Dash, a newcomer in interactive web applications A few days ago, Plotly announced Dash now available for R. After reading this announcement, I thought this ...

blogrmdfirst_header

2019-07-09 / Sébastien Rochette / development, package, Rmarkdown, tips

Rmd first: When development starts with documentation

Documentation matters ! Think about future you and others. Whatever is the aim of your script and analyses, you should think about documentation. The way I see it, R package structure is made for that. Let me try to convince you. At use’R 2019 in Toulouse, I did a presentation entitled: ‘The “Rmd first” method: when projects start with documentation’ ...

2019-05-07 / Sébastien Rochette / development, package, tips

{attachment} is on CRAN !

We are pleased to announce that our package {attachment} is now available on CRAN. The goal of attachment is to help to deal with package dependencies during package development. It also gives useful tools to install or list missing packages used inside Rscripts or Rmds. Deal with dependencies during package development If you ever had the following error when checking ...

2019-03-04 / Colin Fay / development, package, shiny

Building Big Shiny Apps — A Workflow 2/2

Second part of the blog transcription of the talk I’ve given during the eposter session of the rstudio::conf(2019). Read the first part here. Building Big Shiny Apps: step by step Step 1: Designing Don’t rush into coding. I know you want to, because it’s what we like to do and what we are good at. But before entering the coding ...

2018-05-16 / Vincent Guyader / development, package, shiny

Our Package template to design a prod-ready Shiny application

In this article, I will introduce the approach we use at ThinkR for Shiny applications we design. This is a relatively strict framework but designed to simplify our life and guarantee to deliver a “prod ready” application (whether it is launched locally, on shinyserver, Rconnect or via ShinyProxy with docker). This framework simplifies application maintenance and collaborative work. Edit: Better read ...