1# llimphi-widget-hero23Shared-element transitions, Flutter-Hero style.
45The Llimphi runtime keeps a `HeroRegistry` retained between frames: if the same
6`key` appears in a different rect across two consecutive frames, the runtime
7interpolates `transform` so the node "flies" from the previous rect to the
8current one. This widget is the canonical wrapper that marks the `child` as a
9hero with the given `key` — an app composing with it never has to touch
10`View::hero` by hand.
1112The previous signatures (`hero_view`, `hero_quick`) are kept so callers do not
13break. They used to wrap only with `animated_inout` (fade); now they compose
14`hero` + `animated_inout`, so a caller reusing the same `key` across routes gets
15the real fly **and** the landing fade together.
1617---
1819Part of **llimphi** — see [llimphi](../../README.md).
README.md
llimphi-widget-hero
Shared-element transitions, Flutter-Hero style.
The Llimphi runtime keeps a HeroRegistry retained between frames: if the same
key appears in a different rect across two consecutive frames, the runtime
interpolates transform so the node "flies" from the previous rect to the
current one. This widget is the canonical wrapper that marks the child as a
hero with the given key — an app composing with it never has to touch
View::hero by hand.
The previous signatures (hero_view, hero_quick) are kept so callers do not
break. They used to wrap only with animated_inout (fade); now they compose
hero + animated_inout, so a caller reusing the same key across routes gets
the real fly and the landing fade together.