- Add documentation about
idparameter (#103)
- BREAKING CHANGE API functions now work in shiny modules without having to specify the namespace. This means that if you previously explicitly used a namespace when calling API functions, you need to remove the namespace function (#90)
- Add
timezoneparameter totimevis()- supports showing the timeline in a different timezone than your local machine (#67) - Add
setCustomTime()andsetCurrentTime()functions (#20) - Add
<timeline>_visibleShiny input that sends the items that are currently visible in the timeline to Shiny as an input (#22) - Fixed bug: using
setSelection()did not trigger the Shiny selected input (#82) - Add documentation about how to add custom style to timevis (#45)
- Add documentation about how to use BCE dates (#99)
- Add documentation tab to the demo app
tibbles converted todata.frames (Fixes issue #53, @muschellij2).- added documentation for how to extend the timevis object in JavaScript
- added an option to not load the javascript dependencies (#25)
- Fix issue #47: Leading whitespace when getting selected item Id as a string
- Show correct timezone in demo app
- Add demo advanced data
timevisDataandtimevisDataGroups
- timevis and visNetwork can work together in the same app (the bug is fixed on timevis' end, so it will only work if a timevis widget is defined before a visNetwork one until visNetwork also fix the bug) (#11)
- re-defining the data input handler does not cause a warning
- Added VignetteBuilder field to DESCRIPTION file as per CRAN's request
- added support for groups (#1) (parameter order for
timevis()has changed)
- add
fitparam totimevis()that determines if to fit the items on the timeline by default or not - timevis can now be included inside regular R markdown documents
- all the API functions can now work on timeline widgets that are not yet initialized, which means they can work in rmarkdown documents or in the console
- all the API functions can now work with pipes (
%>%pipelines) - the API functions can accept either an ID of a widget or a widget object. This is useful because now the API functions can either be called from the server of a Shiny app at any point, or they can be called directly using the widget when it is being initialized
- when re-rendering a timeline, the old data are not removed (#3)
- can now use a dataframe that results from merging/binding two dataframes as input (#7)
- zoom buttons show up when using a custom
shinytheme()(#9)
- removed the
getDatagetWindowgetIdsgetSelectedparameters and instead just return that info always (#4) - refactor and modularize Shiny app code
- UI improvements to Shiny app
- added source code to Shiny app
- added social media meta tags to Shiny app
- add a lot of responsive CSS to make the app look well in smaller screens
Initial CRAN release