konstantin-paulus 1bbe992345 Refactor and enhance transform functionality in the asset management system
- Replaced the `useModifiers` hook with `useTransforms` to better reflect the new transform functionality.
- Updated components to utilize the new `useTransforms` hook, including `ActionBar` and `PromptInputActions`, improving the handling of transformations.
- Introduced new `TransformItem` component for managing transform actions in the UI.
- Refactored asset handling logic to accommodate the new transform types and ensure compatibility with existing features.
- Removed deprecated modifier-related code and documentation, streamlining the codebase and enhancing clarity.
- Updated documentation to reflect changes in transform functionality and usage examples.
2026-09-12 16:31:36 +02:00

1.2 KiB
Raw Permalink Blame History

<image>

A picture: a rect whose intrinsic paint is the media src names (see media.md).

<image src="stills/photo.jpg" x={40} y={40} width={200} height={112} />

Props

All common props, plus:

Prop Type Default Meaning
src string | AssetRef required See media.md.
objectFit "cover" | "contain" | "fill" "cover" How the source maps into the box.
frameRate number 30 Frames per second for a src naming a directory of numbered frames, which plays on <image> as footage does (see media.md). Nothing for a still to read.

Without width/height the box is 1920×1080. A still has no duration to fit, so with no end it takes the 16-second default (see timing.md).

A paint child draws over the media paint created by src (see paints.md); a <shaderPaint> child instead post-processes it, so the image renders through the shader. <stroke>, <shadow>, <effect>, <animation> and <keyframeTrack> children are valid too.