start work on ioslides deck

Author: jmcphers

images/texturebg.png

@@ -5,7 +5,7 @@ date: "January 18, 2016"
 output: 
   html_document: 
     highlight: textmate
-    theme: flatly
+    theme: journal
 ---
 
 # Introduction
@@ -18,7 +18,7 @@ We'll cover three main approaches:
 
 1. **Debugging**
 
-    Pausing execution of your program, at a place you choose, to inspect its state. Best used when you suspect where a problem lies or need to verify the state around a particular section of code.
+    Pausing execution of your program, at a place you choose, to inspect its state as each following statement is executed. Best used when you suspect where a problem lies or need to verify the state around a particular section of code.
 
 2. **Tracing**
 

shiny-debug-doc.Rmd

@@ -1,32 +1,96 @@
 ---
-title: "Untitled"
-author: "Jonathan McPherson""
+author: "Jonathan McPherson"
 title: Debugging with Shiny
-output: ioslides_presentation
+output: 
+  ioslides_presentation:
+    css: shiny-slides.css
+    highlight: textmate
+    self_contained: no
 ---
 
 # Overview
 
-We'll cover four main areas:
-- Tracing Execution
-- Tracing Errors
+## Outline
+
+We'll cover three main areas:
+
 - Debugging
+- Tracing 
+- Errors
+
+# Debugging
+
+"Finding your bug is a process of confirming the many things that you believe are true — until you find one which is not true."
+
+-- Norm Matloff 
+
+Author of *The Art of R Programming* and *The Art of Debugging*
+
+## Breakpoints
+
+![breakpoints](images/breakpoint.png)
+
+*Breakpoint (armed)*
+
+## Breakpoints
+
+![breakpoints](images/breakpoint-hit.png)
+
+*Stepping after execution*
+
+## Breakpoints {.build}
+
+### Pros
 
-# Showcase mode
+- Doesn't change code
+- Can inspect local values/stack
+- Can step through following code
 
-# The Reactive Graph
+### Cons
 
-# JavaScript error console
+- Only works inside `shinyServer`
+- Can't tell you why something isn't happening
+- Interrupts program flow; not conditional
 
-# Shiny traces
+## browser()
 
-# Deployed Apps
+![browser](images/browser.png)
 
-options()
+## browser() {.build}
 
-```{r}
-# Check JavaScript error console (btw it would be great to have a decent experience for doing this in RStudio someday)
-# options(shiny.trace = TRUE) to see what messages are going back and forth between the browser and server. This is mostly useful when you're writing your own custom bindings, or if you're not sure why something's not updating.
-# options(shiny.error) and options(shiny.observer.error). Honestly I'm not sure if these are working correctly. That was something I was hoping one of us (you, Winston, or I) could look into.
-# Collecting tracebacks when errors occur in observers/reactives. Again, not exactly sure what the answer is here, also needs investigation by one of us.
+### Pros
+
+- Similar advantages to breakpoints
+- Valid anywhere an R expression is valid
+- Can be made conditional
+
+### Cons
+ 
+- Changes your code!
+- Interrupts program flow
+- Can't tell you why something isn't happening
+
+# Tracing
+
+## Showcase Mode
+
+![showcase mode](images/kmeans-showcase.gif)
+
+```{r eval=FALSE}
+runApp(..., display.mode="showcase")
+```
+
+## Reactive Log
+
+![reactive log](images/reactlog.png)
+
+```{r eval=FALSE}
+options(shiny.reactlog=TRUE)
+runApp(...)
+showReactLog()
 ```
+
+# Error Handling
+
+
+

shiny-debugging.Rmd

@@ -0,0 +1,8 @@
+slides > slide.dark {
+  background-image: url(images/texturebg.png);
+}
+
+slide img {
+  max-width: 768px;
+  max-height: 350px;
+}