You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -210,7 +235,7 @@ Note that creating the `summary` reactive isn't strictly necessary here, as it's
210
235
But it's good practice to keep computing and plotting separate as it makes the flow of the app easier to understand, and will make it easier to generalise in the future.
211
236
212
237
A screenshot of the resulting app is shown in Figure \@ref(fig:prototype).
213
-
You can find the source code at <https://github.com/hadley/mastering-shiny/tree/master/neiss/prototype.R> and try out a live version of the app at XYZ.
238
+
You can find the source code at <https://github.com/hadley/mastering-shiny/tree/master/neiss/prototype.R> and try out a live version of the app at <https://hadley.shinyapps.io/ms-prototype/>.
@@ -246,7 +271,7 @@ I made one other change to improve the aesthetics of the app: I forced all table
246
271
This makes the output more aesthetically pleasing because it reduces the amount of incidental variation.
247
272
248
273
A screenshot of the resulting app is shown in Figure \@ref(fig:polish-tables).
249
-
You can find the source code at <https://github.com/hadley/mastering-shiny/tree/master/neiss/polish-tables.R> and try out a live version of the app at XYZ.
274
+
You can find the source code at <https://github.com/hadley/mastering-shiny/tree/master/neiss/polish-tables.R> and try out a live version of the app at <https://hadley.shinyapps.io/ms-polish-tables>.
250
275
251
276
```{r polish-tables, echo = FALSE, out.width = "100%", fig.cap="The second iteration of the app improves the display by only showing the most frequent rows in the summary tables"}
252
277
case_study_screenshot("polish-tables")
@@ -269,7 +294,7 @@ Then I condition on that input when generating the plot:
269
294
```
270
295
271
296
A screenshot of the resulting app is shown in Figure \@ref(fig:rate-vs-count).
272
-
You can find the source code at <https://github.com/hadley/mastering-shiny/tree/master/neiss/rate-vs-count.R> and try out a live version of the app at XYZ.
297
+
You can find the source code at <https://github.com/hadley/mastering-shiny/tree/master/neiss/rate-vs-count.R> and try out a live version of the app at <https://hadley.shinyapps.io/ms-rate-vs-count>.
273
298
274
299
```{r rate-vs-count, echo = FALSE, out.width = "100%", fig.cap = "In this iteration, we give the user the ability to switch between displaying the count or the population standardised rate on the y-axis."}
275
300
case_study_screenshot("rate-vs-count")
@@ -293,7 +318,7 @@ I then use `eventReactive()` to create a reactive that only updates when the but
293
318
```
294
319
295
320
A screenshot of the resulting app is shown in Figure \@ref(fig:narrative).
296
-
You can find the source code at <https://github.com/hadley/mastering-shiny/tree/master/neiss/narrative.R> and try out a live version of the app at XYZ.
321
+
You can find the source code at <https://github.com/hadley/mastering-shiny/tree/master/neiss/narrative.R> and try out a live version of the app at <https://hadley.shinyapps.io/ms-narrative>.
297
322
298
323
```{r narrative, echo = FALSE, out.width = "100%", fig.cap = "The final iteration adds the ability to pull out a random narrative from the selected rows"}
0 commit comments