Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using the animation feature of kitty graphics protocol #15

Closed
AnonymouX47 opened this issue May 17, 2023 · 0 comments
Closed

Using the animation feature of kitty graphics protocol #15

AnonymouX47 opened this issue May 17, 2023 · 0 comments

Comments

@AnonymouX47
Copy link

AnonymouX47 commented May 17, 2023

Hello!

Found out about your project recently and I seem to like what you're doing so far.

I just dropped by to say some others and I recently had a discussion at hpjansson/chafa#104 on using the animation feature of Kitty graphics protocol and thought it could be really useful and applicable to what you're doing here.

Last I checked, every frame was being transmitted as a separate image (and seems to still be the case)... which isn't really the best (except the images are being deleted) for a streaming (indefinite end) source. I think using the animation feature of the protocol, if supported (currently, only kitty does), would be better.

Another (actually simpler but maybe not as appropriate) approach would be to use two alternating IDs and then delete the image with one ID immediately after displaying the image with the other ID. This would work on any terminal emulator that at least implements image deletion by ID.

By the way, the animation feature also provides a lot of functionality that can improve performance of updates between frames such as "differential" updates.

Thanks and well done! 👍🏾

I feel this would've been more appropriate in a "discussion" but that doesn't seem to be enabled.

Repository owner locked and limited conversation to collaborators May 17, 2023
@chase chase converted this issue into discussion #16 May 17, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant