-
Notifications
You must be signed in to change notification settings - Fork 54
Suggestion: Merge with lottie-flutter #13
Comments
Hey, thanks for the suggestion. Long story short: Given that the implementation is completely different, merging both together doesn't seem beneficial to me. However, I'll watch this issue and the one on lottie-flutter and see if there are any good points that speak in favor of merging them together in the near-future. If it turns out to be a good idea, I certainly wouldn't mind it and would be glad to help in that process. |
I also just realized that this fork already implements everything except for dashed paths, but also has dashed paths checked in it's todo list. @dnfield Can you please clarify whether that feature is already available? |
My fork of Lottie Flutter renders a good number of Lottie files correctly, however, I wouldn't quite regard it as production ready, for at least the following reasons:
I want to see Lottie work on Flutter, but I'm leaning more towards piecing together a solution involving more direct Skia usage than this - but there's a bigger backstory to make that work. That said, if you'd like to somehow merge these efforts I have nothing against that either. |
I'm posting this suggestion on both repositories. I noticed in the official documentation for Lottie they include both fluttie and lottie-flutter with no information about the pros / cons of each.
I think it would be great if the two repositories could join together and have a really solid, highly tested lottie plugin for Flutter hosted within the Flutter Community organisation so contributors to both projects will get credit.
Hope you like this suggestion!
The text was updated successfully, but these errors were encountered: