Feature request: add notebook anywidget support

[Billyzhang1229]

Hi all, I’d like to propose adding anywidget support for notebook workflows (Jupyter/marimo), with an API like:

w = d3arg.to_anywidget()
w

Why

• Better notebook-native embedding than side-effect display(...) flows
• Works well in modern notebook apps (including marimo)
• Cleaner composition with other widget-based UIs

Proposal

• Add D3ARG.to_anywidget(...) that returns an anywidget.AnyWidget
• Reuse existing visualizer.js + visualizer.css rendering logic
• Use iframe srcdoc for isolation and compatibility

Notes from prototyping

• iframe/body sizing and overflow need small CSS guards to avoid duplicate-looking scrollbars
• anywidget implies Python >=3.8 compatibility (metadata should match)

Questions for maintainers

1. Does this API shape (to_anywidget) look acceptable for upstream?
2. Should anywidget be a hard dependency, or optional extra (e.g. [widgets])?
3. Any preference on implementation style:
   • wrapper around existing render pipeline (minimal change), or
   • deeper renderer refactor for shared frontend entrypoints?

I have created a PR for this feature. Let me know what you think. #244

[kitchensjn]

Hi @Billyzhang1229, thank you for looking into this! I have heard of anywidget but haven't used it before. This seems like a cool direction that could maybe open up more interactivity.

Should this be separate from draw()? Are their advantages to the current D3ARG.draw() function that the new D3ARG.to_anywidget() function doesn't cover (from a brief look, seems to have everything)? Building off your comment about anywidget compatibility, have you ever run into an instance where anywidget doesn't work? Keeping up with all of the different notebook environments (and even things like reveal.js presentations) has been a challenge.