← Back to home
Comparison · Analytics

forestly vs textshaping

A side-by-side editorial comparison of forestly and textshaping — release velocity, themes, recent moves, and the top alternatives to consider.

forestly vs textshaping: at a glance

Featureforestlytextshaping
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-safety, adverse-events, data-visualization, r-languagetypography, text-shaping, bidi, graphics-stack
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is forestly?

forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.

forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.

Read the full forestly trajectory →

What is textshaping?

Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.

textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.

Read the full textshaping trajectory →

forestly vs textshaping: editorial side-by-side

F
forestly
ANALYTICS
0.0

forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.

◆ Current state

forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.

◆ Where it's heading

The arc runs from a fixed interactive widget toward a configurable one with two output modes. Nearly every new argument in the last two releases exists to remove something from the display or relabel it, which suggests the users driving development are producing outputs for others to review under conventions they do not control. The x-axis range, column header, figure header and slider range arguments point the same way — this is a tool being fitted into standardised reporting rather than used ad hoc.

◆ Prediction

Given that the last two releases have consisted almost entirely of display-control arguments, the next is likely more of the same, applied to whichever parts of the interactive layout are still fixed.

T
textshaping
ANALYTICS
0.0

Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.

◆ Current state

textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.

◆ Where it's heading

The package has moved from Latin-first layout to script-agnostic layout in two rewrites, 0.4.0 and 1.0.0, and is now in the long correctness tail that follows. The bug reports arriving from ggplot2, ragg and marquee issue numbers show how it works in practice: textshaping bugs surface as rendering defects in the packages above it, which is why so many fixes here cite another package's issue tracker.

◆ Prediction

Expect continued fixes driven by downstream rendering reports rather than new layout features, as the 1.0.x series stabilises. The font fallback path has produced two of the recent bugs and is the most likely source of the next.

Alternatives to forestly and textshaping

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 forestly or textshaping.

See all forestly alternatives → · See all textshaping alternatives →

Recent activity from forestly and textshaping

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agotextshapingFixes reverting between font fallbacks
  2. 5mo agoforestlyDownload button, AE filter label and diff toggle become optional
  3. 9mo agotextshapingGuards against freetype version mismatches with systemfonts
  4. 11mo agoforestlyStatic RTF forest plots join the interactive output
  5. 11mo agotextshapingFixes a signed integer overflow in the previous fix
  6. 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
  7. 1y agotextshapingFixes hard line breaks across multiple embeddings
  8. 1y agotextshapingShaping engine rewritten to honour global text direction
  9. 1y agoforestlyreactR 0.6.0 rendering fix and slider label control
  10. 2y agoforestlyTreatment group selection and rough-edge fixes
  11. 3y agoforestlyFirst release on GitHub and CRAN

Frequently asked questions

What is the difference between forestly and textshaping?

They serve adjacent needs but don't currently overlap on shipped themes. forestly and textshaping are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is forestly better than textshaping?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. forestly and textshaping are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to forestly?

Top forestly alternatives in Analytics are ranked by recent ship velocity. Browse the "forestly alternatives" section above for the current picks, or visit /alternatives/forestly for the full list with editorial commentary on each.

What are the best alternatives to textshaping?

Top textshaping alternatives in Analytics are ranked by recent ship velocity. Browse the "textshaping alternatives" section above for the current picks, or visit /alternatives/textshaping for the full list with editorial commentary on each.