An R package for creating rich, interactive timeline visualizations in Shiny apps and R Markdown documents.
timevis is an R package that allows users to create interactive timeline visualizations directly from R. It solves the problem of visualizing temporal data in an engaging, dynamic way within Shiny apps or R Markdown reports. The package provides a rich API to manipulate timelines programmatically and retrieve user interactions back into R.
R developers and data scientists building Shiny applications or dynamic reports in R Markdown who need to present time-based data interactively.
Developers choose timevis for its seamless integration with the R ecosystem, extensive interactivity features, and the ability to customize and control timelines extensively through both UI and programmatic APIs.
📅 Create interactive timeline visualizations in R
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides seamless embedding in Shiny with reactive input variables like input$mytime_data for data retrieval, as detailed in the 'Retrieving data from the widget' section.
Offers functions like addItem() and setWindow() to programmatically control timelines, usable both in R console and Shiny apps, with chaining support via %>%.
Supports groups and nested groups for organizing items into multi-resource timelines, demonstrated with examples in the README.
Enables linked brushing with other widgets through crosstalk, allowing synchronized selections across visualizations, as shown in the example with DT::datatable.
Allows full styling via CSS to match app themes, with examples provided for custom looks, such as the World Cup timeline with HTML content.
Inherits all constraints of the underlying vis.js library, requiring direct JavaScript manipulation for unsupported features, as admitted in the 'Extending timevis' section.
Locked into the R ecosystem, making it impractical for projects that need to share visualizations outside R or integrate with non-R tools.
Client-side rendering can become sluggish with very large datasets, a common issue with JavaScript-based visualizations not addressed in the documentation.