NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev
Dashboard cards that behave like amoebas - reshape into polyomino silhouettes, push through each other, and remember their layout.
Latest stable
0.4.1
Last release 1 months ago
14 Oct 2026
Too new to tell
only 2 release windows
Nearly every release is documented
notes for 7 of 7 stable releases
Nothing withdrawn
no release was ever pulled
4 months old
7 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
Fix — the grid now uses the full viewport width. The column count was the number of columns that fit at maxCellExtent, rounded down. That count's idea
maxCellExtent, rounded down. That count's ideal extent is above max, so
cells were clamped to max and up to a whole column of the viewport was left empty on the right
(88px at 1500px wide with max 128 / gap 12). The count now rounds up, to the smallest count
whose cells fit under max, so the columns span the width exactly whenever cells can stay at or
above minCellExtent. When no count can (a very narrow min..max band), it keeps cells at max
with some slack rather than shrinking below min and panning sideways. A filled width also no
longer leaves a ~1e-13px horizontal scroll range from floating-point overshoot. Regression
test: test/grid_metrics_fill_test.dart (sweeps widths across four configs).Breaking — `bodyDragActivation` now defaults to `BodyDragActivation.longPress`. Moving a card by its body takes a ~350ms hold, then a drag. With the o
bodyDragActivation now defaults to BodyDragActivation.longPress. Moving a
card by its body takes a ~350ms hold, then a drag. With the old immediate default every pan
on a body moved the card, so buttons, lists and scrollables inside a card could never win a
drag, and real card content was unusable. Edge and corner handles still drag immediately. To
keep the old behavior (e.g. purely visual cards), pass
bodyDragActivation: BodyDragActivation.immediate.Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
Fix — edge auto-scroll stalled while pushing a card against a viewport edge (#2). Drag events report localPosition through the transform captured at p
Fix — edge auto-scroll stalled while pushing a card against a viewport edge (#2). Drag
events report localPosition through the transform captured at pointer-down, so a still
pointer keeps the same local position while the board scrolls beneath it. The view converted
it with the LIVE scroll offset, so every auto-scroll frame drifted the derived point out of the
edge margin and the scroll stopped after a few frames. Only real jittery pushing exposed it; a
perfectly still hold worked. Drag coordinates now convert against the scroll offset captured at
drag start. Regression tests: test/edge_auto_scroll_gents_repro_test.dart (jitter against the
edge) and test/edge_auto_scroll_test.dart (both directions, both body-drag activation modes).
Docs: README and llms.txt now cover bodyDragActivation, AmoebaShell,
AmoebaListView, AmoebaPadding.clipToShape and the padding overlay. The README's Status
line no longer claims 0.0.1.
New — `AmoebaGridConfig.bodyDragActivation` (BodyDragActivation): controls how a drag on a card *body* begins.
AmoebaGridConfig.bodyDragActivation (BodyDragActivation):
controls how a drag on a card body begins.
immediate (default, unchanged behavior): a pan anywhere on the body
moves the card — even through hit-opaque content.longPress: a body move starts only after a ~350ms hold (then movement),
feeding the same drag-engine path pans use. The card stops competing in
the pan arena, so taps, drag-scrolls, and other gestures inside card
content win instantly. On activation the card raises its lift cue as the
pick-up signal. Edge/corner handles keep immediate drag in both modes —
they are chrome, not content.New — `AmoebaShell`: shape-aware header/body card scaffold. The header pins inside the highest solid span that can fit it (never a notch, never a too-
New — AmoebaShell: shape-aware header/body card scaffold. The header pins
inside the highest solid span that can fit it (never a notch, never a
too-narrow arm); the body receives the full remaining shape below it, so flow
widgets keep re-flowing through notches. Exists because the obvious
compositions both fail — see its dartdoc.
Shape-following padding: CardOutline.trace(extraInset:) erodes the
outline uniformly (convex radii shrink, concave grow);
AmoebaCardGeometry.erodedPath(inset) exposes it. AmoebaPadding now
clips its child to the eroded silhouette by default (clipToShape: false
to opt out) — padding hugs the edge the way rectangle padding hugs a
rectangle, enforced no matter what the child paints. Content can no longer
leak onto the page background through empty bounding-box regions.
AmoebaListView flow correctness:
AmoebaPadding clips to
(contentClip), so the clip can never shear glyphs the layout thought
were safe;Fix — drag-morph chamfering: lerpOutline resampled outlines into a
coarse polyline, flattening every corner arc to a chamfer mid-morph.
Samples now scale with perimeter and reconnect via midpoint quadratics —
corners stay round while dragging.
Developer experience:
AmoebaGridDiagnostics.showPaddingOverlay (+ paddingOverlayInset)
paints every card's padding band translucent red in debug builds;AmoebaListView nested inside AmoebaContentArea (windowed,
notch-free scope) warns in debug that rows will never re-flow;Padding between the card and a
flow widget) warns about broken span alignment.Fix — pressing a card grabbed the WRONG card after a resize/re-layout. RawGestureDetector
constructs its recognizer once and only re-runs the initializer on rebuild, so the GridMetrics
closed over in the recognizer's constructor (the pointer-down hit test) froze at first-build
values while paint used fresh metrics. After the cell extent re-resolved — a window resize, or a
drag/rearrange that changed the occupied bounds — hit-testing and painting used different cell
sizes and a press grabbed a card offset from the pointer (worse the further it was scrolled). The
hit test now reads the controller's live metrics. Regression test:
test/scroll_resize_hittest_test.dart.
Fix — side-handle inward L-gesture. Pulling a side handle IN and then perpendicular used to drop the perpendicular drag entirely (it fell through to a plain strip retract), so "pull in, then down" only ever carved a single row. The inward gesture now mirrors the outward one and removes the full notch block, deepening it along the perpendicular axis.
Fix — submissive resolution reworked to the runner model. When an aggressor overlaps a card
it now: cedes the overlap (trimmed); keeps the LARGER side when bisected; and when fully
smothered becomes a runner that retreats OPPOSITE the aggressor's advance at the smother
frame (not first contact) and takes full space at its original size, shrinks to fit a
partial gap, or drops to a 1x1 (an open adjacent cell, or into the aggressor, which cedes that
cell). A runner never displaces another card and is never killed. This replaces the previous
chained "retreater-becomes-aggressor" behaviour, which could ping-pong two cards until one was
flung across the grid, and could drop the smaller half of a bisect or vanish a cornered card.
Covered by test/submissive_ac_test.dart and test/resize_gesture_test.dart.
New — `AmoebaListView`: a fixed-extent, vertically-scrolling list whose rows RE-FLOW to the card's polyomino shape as they scroll — a row narrows when
New — AmoebaListView: a fixed-extent, vertically-scrolling list whose rows RE-FLOW to
the card's polyomino shape as they scroll — a row narrows when it scrolls up into a notch and
sweeps to the full width where the card is solid. Re-queried every scroll frame, not laid out
once; degrades to a plain list outside a fluid card.
Fix: disposing an AmoebaGridView before any handle had been hovered
threw "Looking up a deactivated widget's ancestor is unsafe". The
_handleReveal AnimationController was a lazy late final, so a view
torn down without a hover lazily constructed it inside dispose(), where
createTicker's ancestor lookup runs on a deactivated element. It is now
created in initState. Regression test added (test/dispose_test.dart).
AmoebaGridView — a field of square units (config counts are minimums; the grid grows to fill wider viewports), pannable in both axes with edge auto-sc
Initial release.