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

Now it's time to move to Lottie 3.4, which solve the performance issue #7

Merged
merged 6 commits into from
Jul 8, 2022

Conversation

dreampiggy
Copy link
Contributor

Pick back the code, and implements the bitmap frame extract using the new API (That LottieCompositionLayer)

And during the development, I found a bad design that SDAnimatedImageView.sd_setImage(with:) hardcode the .animatedImageClass to SDAnimatedImage.self. It's not easy to use.

This will be fixed in SDWebImage v5.13.1 as well.

Pick back the code, and implements the bitmap frame extract using the new API
@dreampiggy dreampiggy force-pushed the 1.x branch 4 times, most recently from 6704ef2 to 2dc5856 Compare July 8, 2022 16:19
@dreampiggy dreampiggy added the enhancement New feature or request label Jul 8, 2022
@dreampiggy dreampiggy added this to the 1.0.0 milestone Jul 8, 2022
@dreampiggy
Copy link
Contributor Author

dreampiggy commented Jul 8, 2022

LGTM now. Have no time to fix the GitHub Action CI, just test locally

  • iOS Demo: ✅
  • macOS Demo: ✅
  • iOS Unit Test: ✅
  • Pod Lint: ✅
  • SwiftPM Build: ✅
  • Carthage ❌(macOS)

This was linked to issues Jul 8, 2022
@dreampiggy dreampiggy merged commit b483305 into master Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SPM support Lottie 2 vs Lottie 3
1 participant