Cran version 0.11.2

What's Changed

• 73 with mock is going away 2 by @berthetclement in #74
• fix cran NOTE s3 method as.character.Input() by @berthetclement in #75

New Contributors

• @berthetclement made their first contribution in #74

Full Changelog: v0.11.0...v0.11.2

v0.11.0

fix tests on R-devel 4.2

CRAN version 0.10.1

• Changed maintainer

v0.8

update readme

v0.5.1

New Features

• Variable .id is now available when evaluating the initial properties of the input controls. This can be useful in comparison mode, for instance to set different choices for a select input.

Bug fixes

• Fixed a scope problem occuring when manipulateWidget was used inside a function and parameter .updateInputs was used.
• Fixed a crash that could occur when parameters .compare and .updateInputs were used together.

V0.5.0

New Features

• manipulateWidget() can now be used in a R Markdown document with shiny runtime. Input controls are included in the final document so end users can play with their values directly. (contribution by JJ. Allaire)
• manipulateWidget() has two new arguments .compare and .compareLayout to create a comparison interface. When .compare is set, two charts are outputed with some common and some individual input controls (see vignette).
• Now, input controls generated by manipulateWidget() can be dynamically updated thanks to the new argument ".updateInputs".
• New functions staticImage() and staticPlot() to include in a combine widget a static image or a static plot created with base functions, ggplot2, etc.
• In combinedWidgetsobjects, individual widgets are stored in a property called widgets, so users can now access them and modify them.

V 0.4

BREAKING CHANGES:

• Function combineWidgets has been entirely rewritten and now produces a htmlwidget that can be included as is in documents or shiny applications. The general behavior is the same, but some parameters have changed

NEW FEATURES:

• manipulateWidget() can now update an already rendered widget instead of overwriting it each time the user changes an input. This leads to better performance and user experience. Look at the documentation of manipulateWidget for further information.

BUGFIXES:

• manipulateWidgets() now preserves the order of the initial value of select inputs.
• manipulateWidgets() now automatically finds the correct render and output functions. This solves in particular sizing problems.