BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//compute-paris-2026//talk//DADPJC
BEGIN:VTIMEZONE
TZID:Europe/Paris
BEGIN:STANDARD
DTSTART:20251125T000000
TZNAME:CET
TZOFFSETFROM:+0100
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T030000
RDATE:20270328T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261025T030000
RDATE:20271031T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Beyond One-Shot Rendering: Interactive R htmlwidgets in Jupyter - 
 Romain François
DTSTART;TZID=Europe/Paris:20261125T100500
DTEND;TZID=Europe/Paris:20261125T103500
DTSTAMP:20261111T073050Z
UID:pretalx-compute-paris-2026-DADPJC@pretalx.com
DESCRIPTION:R has a rich ecosystem of interactive visualizations built on 
 {htmlwidgets}\, including packages such as {leaflet}\, {plotly}\, and {DT}
 . In Jupyter notebooks\, however\, these widgets are typically rendered as
  self-contained HTML documents. While they remain interactive in the brows
 er\, their connection to the R session is lost after rendering.\n\nThe {ju
 pyter.htmlwidgets} project takes a different approach\, leveraging the xeu
 s-r kernel and Jupyter’s communication infrastructure to establish bidir
 ectional communication between R and JavaScript.\n\nThis opens up a middle
  ground between one-shot rendering and a full Shiny application: existing 
 htmlwidgets can become connected components of a notebook\, responding to 
 commands from R and sending user interactions back to the kernel\, without
  introducing a full reactive framework. This approach preserves the explor
 atory\, cell-driven workflow and rhythm of notebooks.\n\nThrough live demo
 nstrations and a look at the underlying architecture\, we’ll explore how
  this approach works\, how it builds on the existing R ecosystem\, and wha
 t it could mean for interactive computing in Jupyter.
LOCATION:Room 106
URL:https://pretalx.com/compute-paris-2026/talk/DADPJC/
END:VEVENT
END:VCALENDAR