Skip to content
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

Introduce a custom image source provider to enable third-party image processors to utilize AnimatedImageView. #2094

Merged
merged 3 commits into from
Jun 13, 2023

Conversation

yeatse
Copy link
Contributor

@yeatse yeatse commented Jun 12, 2023

Before this update, third-party image processors were unable to create animated images without relying on UIImage.animatedImage, which is only available on iOS and can consume a significant amount of memory.

This pull request addresses the problem by introducing a new protocol called ImageFrameSource and refactoring AnimatedImageView to utilize it.

Relevant issue:
yeatse/KingfisherWebP#41
yeatse/KingfisherWebP#39

@onevcat
Copy link
Owner

onevcat commented Jun 12, 2023

At the first glance, it is coooool.

Thanks for this. I will take a detail look at it ASAP.

@yeatse
Copy link
Contributor Author

yeatse commented Jun 12, 2023

It appears that the check failed because of a network connection issue. I tested it on my machine and all tests were passed successfully.

@onevcat
Copy link
Owner

onevcat commented Jun 12, 2023

Don't worry about it! I guess it is something related to the low spec of GH's node and the shared resource. It sometimes fails at the first time.

@onevcat
Copy link
Owner

onevcat commented Jun 13, 2023

@onevcat onevcat merged commit 1b0f606 into onevcat:master Jun 13, 2023
@yeatse yeatse deleted the feature/animated-image branch June 13, 2023 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants