tui: image rendering — sixel backend #13
Labels
No labels
area:agents
area:ai
area:config
area:dashboard
area:design
area:design-review
area:devtools
area:entities
area:gallery
area:generate
area:image
area:infra
area:meta
area:model-browser
area:navigation
area:presets
area:security
area:sessions
area:settings
area:sharing
area:test
area:ux
area:webhook
area:workdir
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/loom#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
User story
As a user on a sixel-capable terminal (xterm -ti 340, mlterm, wezterm, foot), I want loom-tui to display images using the sixel protocol when Kitty is unavailable, so that I still get colour images without falling back to block art.
Acceptance criteria
Sixel renderer
SixelRendererstruct implementsImageRenderer(trait from the Kitty ticket)sixelcrate for encoding; fallback: shell out toimg2sixelwhen the crate is unavailable on the target, behind a cargo featureRectdimensions (respecting terminal cell-to-pixel ratio, queried via crossterm /ioctl TIOCGWINSZ)protocol_name()returns"sixel"\x1bPq)Caching
(source, width, height)cache key semantics as the Kitty backendOut of scope
References