* - Convert all example apps to single file app.R file
- Make relevant updates to Readmes to match up with app.R structure
- Add color to plots (RStudio blue)
- In 04_mpg example: Show outliers by default, as opposed to hide, since this is more routine
- In 06_tabsets and 08_html examples: Don't name random data vector "data"
- Add extensive comments to app.R files and use consistent formatting of comments across examples
- In 09_upload example: Use req() to check for NULL entry
* add news entry summarizing changes
* use true RStudio blue, #75AADB
* Conver shinyApp calls at the end to drop argument name in examples 3-11, except for the custom HTML example. Kept them in for examples 1&2 for completeness in first exporuse to function.
* Pull news items that got added before this PR was merged
* Update comment for shinyApp function -- it creates an app object, doesn't run the app
application/x-www-form-urlencoded;charset=UTF-8 is the default, which shinyapps.io
cares about for some reason and tries to parse the data as such. By setting the
content type to the more accurate application/octet-stream, no middleware should
be tempted to futz with the contents.
* trigger a new `shiny:invalidated` event when an output gets invalidated, at the same time that the `recalculating` CSS class is added (fixes#1688)
* add attribution to @andrewsali
* change event name from 'shiny:invalidated' to 'shiny:outputinvalidated'
* add binding and name to the new event 'shiny:outputinvalidated'
* added a shiny:sessionInit JS event that is triggered at the end of the session's initialize method
* new entry
* update NEWS
* correct version number in NEWS.md
* fix typo
If the width is made very wide in showcase mode with side-by-side
arrangement, the app shrinks to almost nothing. For some reason the
zoom CSS property (which we set using jQuery.animate) is set to
"1%" instead of "1".
Numbers and percentages are equally valid here, and the issue goes
away if we use percentage.