From 44237f4ecd3c50f6355ab5e8633529fbf230737d Mon Sep 17 00:00:00 2001
From: cpsievert Chang W, Cheng J, Allaire J, Sievert C, Schloerke B, Xie Y, Allen J, McPherson J, Dipert A, Borges B (2022).
shiny: Web Application Framework for R.
-R package version 1.7.3.9000, https://shiny.rstudio.com/.
+R package version 1.7.3.9001, https://shiny.rstudio.com/.
Internal: Added clearer and strict TypeScript type definitions (#3644) Closed #3345: Shiny now correctly renders Closed #3345: Shiny now correctly renders Fixed #2666 and #2670: Closed #3374: Exported Addressed #1348 and #1437 by adding two new arguments to Addressed #1348 and #1437 by adding two new arguments to Updated Fixed #1565, which meant that resources with spaces in their names return HTTP 404. (#1566) Exported Shiny 0.11 switches away from the Bootstrap 2 web framework to the next version, Bootstrap 3. This is in part because Bootstrap 2 is no longer being developed, and in part because it allows us to tap into the ecosystem of Bootstrap 3 themes. Added Fixed #557: updateSelectizeInput(choices, server = TRUE) did not work when Searching in DataTables is case-insensitive and the search strings are not treated as regular expressions by default now. If you want case-sensitive searching or regular expressions, you can use the configuration options Added support for Exported Custom output bindings can now render Added support for Exported Custom output bindings can now render Updated selectize.js to version 0.11.2. (#596) Added Added Unicode support for Windows. Shiny apps running on Windows must use the UTF-8 encoding for ui.R and server.R (also the optional global.R) if they contain non-ASCII characters. See this article for details and examples: http://shiny.rstudio.com/gallery/unicode-characters.html (#516) Added an Added an Added support for option groups in the select/selectize inputs. When the The Added Showcase mode, which displays the R code for an app right in the app itself. You can invoke Showcase mode by passing Upgraded to Bootstrap 2.3.2 and jQuery 1.11.0. Make Make Files are now sourced with the Support user-defined input parsers for data coming in from JavaScript using the parseShinyInput method. Fixed the bug #299: renderDataTable() can deal with 0-row data frames now. (reported by Harlan Harris) Added Added Added Added Added Automatically concatenate duplicate attributes in tag definitions Added Added The Added click and hover events for static plots; see Added optional logging of the execution states of a reactive program, and tools for visualizing the log data. To use, start a new R session and call Added Added Reactive expressions now have class=“reactive” attribute. Also added New Added the Speed increases for Added Added The HTTP request object that created the websocket is now accessible from the Fix Add shiny.sharedSecret option, to require the HTTP header Shiny-Shared-Secret to be set to the given value. Fix bug where multiple file uploads with 3 or more files result in incorrect data. Add Add Add dateInput and dateRangeInput. Add functions to update values of existing inputs on a page, instead of replacing them entirely. Render a reactive output variable as HTML within an application page. The
-text will be included within an HTML @Manual{,
title = {shiny: Web Application Framework for R},
author = {Winston Chang and Joe Cheng and JJ Allaire and Carson Sievert and Barret Schloerke and Yihui Xie and Jeff Allen and Jonathan McPherson and Alan Dipert and Barbara Borges},
year = {2022},
- note = {R package version 1.7.3.9000},
+ note = {R package version 1.7.3.9001},
url = {https://shiny.rstudio.com/},
}
diff --git a/favicon-16x16.png b/favicon-16x16.png
index ff6afbd265fc9fea8c3cba0c824674d4c8854d68..7c5defb488545a418f242c45bcff305dc048e5fb 100644
GIT binary patch
delta 65
zcmaFQ@t$MD1SWO?bIt93X}+7MGpR8O8Jby{np&9{Y8x0>85nr1H~cdBJhMESu;r&t
Ik4Y@~0E%f7HUIzs
delta 65
zcmaFQ@t$MD1SWPy76zH(ps>x;nba7C3=FLdOsotHv<(b^q)4^Mi^=Di<New features and improvements
-
@@ -141,7 +143,7 @@
plotOutput(), imageOutput(), and uiOutput() gain a fill argument. If TRUE (the default for plotOutput()), the output container is allowed to grow/shrink to fit a fill container (created via htmltools::bindFillRole()) with an opinionated height. This means plotOutput() will grow/shrink by default inside of bslib::card_body_fill(), but imageOutput() and uiOutput() will have to opt-in to similar behavior with fill = TRUE. (#3715)Bug fixes
-htmltools::htmlDependency()(s) with a list() of script attributes when used in a dynamic UI context. This fairly new htmlDependency() feature was added in htmltools v0.5.1. (#3395)htmltools::htmlDependency()(s) with a list() of script attributes when used in a dynamic UI context. This fairly new htmlDependency() feature was added in htmltools v0.5.1. (#3395)nearPoints() and brushedPoints() weren’t properly account for missing values (#2666 was introduced in v1.4.0). (#2668)quoToFunction() now works correctly with nested quosures; and as a result, quasi-quotation with rendering function (e.g., renderPrint(), renderPlot(), etc) now works as expected with nested quosures. (#3373)register_devmode_option(). This method was described in the documentation for devmode() but was never exported. See ?devmode() for more details on how to register Shiny Developer options using register_devmode_option(). (#3364)Minor new features and improvements
radioButtons() and checkboxGroupInput(): choiceNames (list or vector) and choiceValues (list or vector). These can be passed in as an alternative to choices, with the added benefit that the elements in choiceNames can be arbitrary UI (i.e. anything created by HTML() and the tags() functions, like icons and images). While the underlying values for each choice (passed in through choiceValues) must still be simple text, their visual representation on the app (what the user actually clicks to select a different option) can be any valid HTML element. See ?radioButtons for a small example. (#1521)radioButtons() and checkboxGroupInput(): choiceNames (list or vector) and choiceValues (list or vector). These can be passed in as an alternative to choices, with the added benefit that the elements in choiceNames can be arbitrary UI (i.e. anything created by HTML() and the tags() functions, like icons and images). While the underlying values for each choice (passed in through choiceValues) must still be simple text, their visual representation on the app (what the user actually clicks to select a different option) can be any valid HTML element. See ?radioButtons for a small example. (#1521)tools/README.md with more detailed instructions. (#1616)session$user (if it exists) to the client-side; it’s accessible in the Shiny object: Shiny.user. (#1563)Known issues for migration
-<img> tags are no longer automatically scaled to the width of their container. If you use img() in your UI code, or <img> tags in your raw HTML source, it’s possible that they will be too large in the new version of Shiny. To address this you can add the img-responsive class:```r
+<img> tags are no longer automatically scaled to the width of their container. If you use img() in your UI code, or <img> tags in your raw HTML source, it’s possible that they will be too large in the new version of Shiny. To address this you can add the img-responsive class:```r
img(src = "picture.png", class = "img-responsive")
```
@@ -972,9 +974,9 @@
Progress and withProgress, to display the progress of computation on the client browser.choices is a character vector.search$caseInsensitive and search$regex, e.g. renderDataTable(..., options = list(search = list(caseInsensitve = FALSE, regex = TRUE))).htmltools::htmlDependency’s new attachment parameter to renderUI/uiOutput.createWebDependency. It takes an htmltools::htmlDependency object and makes it available over Shiny’s built-in web server.htmltools::htmlDependency objects at runtime using Shiny.renderDependencies().htmltools::htmlDependency’s new attachment parameter to renderUI/uiOutput.createWebDependency. It takes an htmltools::htmlDependency object and makes it available over Shiny’s built-in web server.htmltools::htmlDependency objects at runtime using Shiny.renderDependencies().position parameter to navbarPage.runGitHub() also allows the ‘username/repo’ syntax now, which is equivalent to runGitHub('repo', 'username'). (#427)navbarPage() now accepts a windowTitle parameter to set the web browser page title to something other than the title displayed in the navbar.inline argument to textOutput(), imageOutput(), plotOutput(), and htmlOutput(). When inline = TRUE, these outputs will be put in span() instead of the default div(). This occurs automatically when these outputs are created via the inline expressions (e.g. r renderText(expr)) in R Markdown documents. See an R Markdown example at http://shiny.rstudio.com/gallery/inline-output.html (#512)inline argument to textOutput(), imageOutput(), plotOutput(), and htmlOutput(). When inline = TRUE, these outputs will be put in span() instead of the default div(). This occurs automatically when these outputs are created via the inline expressions (e.g. r renderText(expr)) in R Markdown documents. See an R Markdown example at http://shiny.rstudio.com/gallery/inline-output.html (#512)choices argument for selectInput()/selectizeInput() is a list of sub-lists and any sub-list is of length greater than 1, the HTML tag <optgroup> will be used. See an example at http://shiny.rstudio.com/gallery/option-groups-for-selectize-input.html (#542)selectInput() function also gained a new argument selectize = TRUE to makes use of selectize.js by default. If you want to revert back to the original select input, you have to call selectInput(…, selectize = FALSE).display.mode="showcase" to the runApp() function. Or, if an app is designed to run in Showcase mode by default, add a DESCRIPTION file in the app dir with Title, Author, and License fields; with “Type: Shiny”; and with “DisplayMode: Showcase”.tags$head() and singleton() behave correctly when used with renderUI() and uiOutput(). Previously, “hoisting content to the head” and “only rendering items a single time” were features that worked only when the page was initially loading, not in dynamic rendering.tags$head() and singleton() behave correctly when used with renderUI() and uiOutput(). Previously, “hoisting content to the head” and “only rendering items a single time” were features that worked only when the page was initially loading, not in dynamic rendering.keep.source option, to help with debugging and profiling.type parameter to tabsetPanel() to enable the use of pill style tabs in addition to the standard ones.position paramter to tabsetPanel() to enable positioning of tabs above, below, left, or right of tab content.fluidPage() and fixedPage() functions as well as related row and column layout functions for creating arbitrary bootstrap grid layouts.hr() builder function for creating horizontal rules.hr() builder function for creating horizontal rules.responsive parameter to page building functions for opting-out of bootstrap responsive css.theme parameter to page building functions for specifying alternate bootstrap css styles.input and output objects are now also accessible via session$input and session$output.?plotOutput for details.options(shiny.reactlog=TRUE). Then launch a Shiny app and interact with it. Press Ctrl+F3 (or for Mac, Cmd+F3) in the browser to launch an interactive visualization of the reactivity that has occurred. See ?showReactLog for more information.includeScript() and includeCSS() functions.includeScript() and includeCSS() functions.is.reactive() and is.reactivevalues() functions.stopApp() function, which stops an app and returns a value to the caller of runApp().shiny.usecairo option, which can be used to tell Shiny not to use Cairo for PNG output even when it is installed. (Defaults to TRUE.)selectInput() and radioButtons(), and their corresponding updater functions, for when they have many options.tagSetChildren() and tagAppendChildren() functions.tagSetChildren() and tagAppendChildren() functions.session object, as session$request. This is a Rook-like request environment that can be used to access HTTP headers, among other things. (Note: When running in a Shiny Server environment, the request will reflect the proxy HTTP request that was made from the Shiny Server process to the R process, not the request that was made from the web browser to Shiny Server.)getComputedStyle issue, for IE8 browser compatibility (#196). Note: Shiny Server is still required for IE8/9 compatibility.shiny 0.6.02013-06-05
tabsetPanel() can be directed to start with a specific tab selected.withTags() function.withTags() function.shinyServer() now takes an optional session argument, which is used for communication with the session object.div tag, and is presumed to
-contain HTML content which should not be escaped.div tag, and is presumed to contain
+HTML content which should not be escaped.
use an inline (span()) or block container (div())
+
use an inline (span()) or block container (div())
for the output
a function to generate an HTML element to contain the text
If TRUE, the result of container is treated as both a fill
+item and container (see htmltools::bindFillRole()), which means both the
+container as well as its immediate children (i.e., the result of
+renderUI()) are allowed to grow/shrink to fit a fill container with an
+opinionated height. Set fill = "item" or fill = "container" to treat
+container as just a fill item or a fill container.
Other arguments to pass to the container tag function. This is useful for providing additional classes for the tag.
uiOutput is intended to be used with renderUI on the server
-side. It is currently just an alias for htmlOutput.
uiOutput is intended to be used with renderUI on the server side. It is
+currently just an alias for htmlOutput.
Arguments passed to the <i> tag of htmltools::tags.
Arguments passed to the <i> tag of htmltools::tags.