glymotif
A glycan motif matcher trading convenience wrappers for speed, strictness and explicit specs.
Comparison · Analytics
vellumverse vs vellumwidget
A side-by-side editorial comparison of vellumverse and vellumwidget — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-graphics
vellumverse vs vellumwidget: at a glance
What is vellumverse?
A meta-package whose entire changelog is a version pin, tracking an ecosystem moving faster than it is.
vellumverse attaches the vellum graphics ecosystem in one library() call, reports which versions loaded, lists the bundled packages and surfaces functions masked across them. It is deliberately dependency-light, having dropped rlang and declared only what the conflict reporter actually uses. Since 0.2.0 every release has been a version pin bump rather than new behaviour of its own.
What is vellumwidget?
vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.
vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.
vellumverse vs vellumwidget: editorial side-by-side
vellumverse
5.0ANALYTICS
A meta-package whose entire changelog is a version pin, tracking an ecosystem moving faster than it is.
◆ Current state
vellumverse attaches the vellum graphics ecosystem in one library() call, reports which versions loaded, lists the bundled packages and surfaces functions masked across them. It is deliberately dependency-light, having dropped rlang and declared only what the conflict reporter actually uses. Since 0.2.0 every release has been a version pin bump rather than new behaviour of its own.
◆ Where it's heading
The release record is an index of other packages' work: four of the last six entries do nothing but raise the floor on vellum, vellumplot and vellumwidget. The cadence tells the real story, with pins moving roughly weekly and each bump chasing a minor release somewhere downstream, so the meta-package is currently a distribution convenience rather than a component. The one genuinely structural release in the window was 0.2.1, which trimmed the dependency surface to keep an attach-only package cheap to install.
◆ Prediction
Expect the pin bumps to keep pace with the ecosystem's weekly releases rather than any feature of its own, and the pin on vellumplot to move again as the interaction grammar the widget now depends on continues to land. Whether vellumverse ever grows beyond attach-and-report is not visible in these entries.
vellumwidget
6.3ANALYTICS
vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.
◆ Current state
vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.
◆ Where it's heading
The direction is declarative. 0.7.0 removed the interaction-intent arguments from as_widget() outright, dropping the signature from roughly 36 arguments to 24 and moving highlight, filter and cross-filter into vellumplot's spec via select_point(), condition() and filter_by(). Each release since has enacted more of that compiled spec on the frozen scene, from conditional encodings to single-view filters to cross-view cross-filtering, leaving the widget as an interpreter of the plot rather than a configuration surface of its own. The bug fixes track the same theme the engine's do: measured geometry and rendered geometry must not drift.
◆ Prediction
The notes name the remaining hold-outs explicitly, saying hover_mode, crosshair, legend_click, select_mode and the tooltip-appearance arguments remain only until their spec equivalents land, so the next releases most likely move those into vellumplot and shrink as_widget() further. The scale binds flagged as following the filter work are the other stated next step.
Alternatives to vellumverse and vellumwidget
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either vellumverse or vellumwidget.
glyrepr
The type system the rest of the glycan stack is built on, being hardened one breaking change at a time.
glyanno
Glycan annotation stops depending on the database having seen the structure before.
glydraw
SNFG glycan cartoons stopped being pictures and became ggplot2 geoms, guides and axis labels.
glyenzy
Glycan biosynthesis as a traceable enzyme graph, now including sulfation and gaps it can bridge.
KLINK
Forensic kinship testing with linked STR markers, now peer-reviewed and taking data from anywhere.
See all vellumverse alternatives → · See all vellumwidget alternatives →
Recent activity from vellumverse and vellumwidget
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 14d agovellumversePins raised to vellum 0.6.6, vellumplot 0.9.0, vellumwidget 0.8.0
- 14d agovellumwidget2x raster base image for HiDPI, and exact element hit-testing
- 20d agovellumversePins raised to vellumplot 0.8.0 and vellumwidget 0.7.0
- 20d agovellumwidgetInteraction moves into the plot spec; as_widget() sheds a third of its arguments ⚡
- 27d agovellumversePins raised to vellum 0.5.0, vellumplot 0.6.0, vellumwidget 0.6.0
- 27d agovellumwidgetAxis-aware zoom re-ticks the axes instead of scaling the whole scene
- 1mo agovellumversePins raised to vellum 0.4.0, vellumplot 0.5.0, vellumwidget 0.5.0
- 1mo agovellumwidgetSelectable native SVG text, and crisp canvas redraw when zooming raster
- 1mo agovellumverseDependency surface trimmed to keep the meta-package light
- 1mo agovellumwidgetServer-side proxy drives a rendered widget without re-rendering it
- 1mo agovellumverseAdopts vellum's renamed vl_* graphics primitives
- 1mo agovellumwidgetShiny input read-back, and keyboard plus screen-reader access by default
Frequently asked questions
What is the difference between vellumverse and vellumwidget?
Both compete on the same themes — r-graphics — within Analytics. vellumwidget is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is vellumverse better than vellumwidget?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellumwidget is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to vellumverse?
Top vellumverse alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumverse alternatives" section above for the current picks, or visit /alternatives/vellumverse for the full list with editorial commentary on each.
What are the best alternatives to vellumwidget?
Top vellumwidget alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumwidget alternatives" section above for the current picks, or visit /alternatives/vellumwidget for the full list with editorial commentary on each.