Allow static widgets to be rendered in Shiny docs
Merge pull request #27 from ramnathv/bugfix/static-in-shiny-mode

Allow static widgets to be rendered in Shiny docs
roxygenize with roxygen2 4.0.2; note @S3method has been deprecated
Merge pull request #29 from yihui/roxygenize

roxygenize with roxygen2 4.0.2; note @S3method has been deprecated
Fix error with widgets being used inline in knitr

Knitr doesn't pass an options argument to knit_print when it's an
inline chunk (at least not at the time of this writing--Yihui is
going to consider adding options in that case too). This fix lets
us at least proceed without an error.
wip1
wip2
Proper non-standard rendering of widget values

We have to work quite hard to temporarily hide widgets while
non-standard values (errors, NULL) are rendered. We do this
to not burden the widget author with having to deal with
state changing between normal and non-standard. If we could
go back and revisit the architecture, maybe it would make
sense to bake the notion of widgets being created and
destroyed into the API itself (meaning initialize would be
split into two callbacks, one for one-time initialization of
a particular output, and another that's called each time we
go from non-standard to standard values).

To see this code in action:

devtools::install_github("rstudio/dygraphs")
shiny::runGist("https://gist.github.com/jcheng5/294fed2dee0d2e607d9a")