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

Vito migration guide #2822

Open
RoiEXLab opened this issue Jan 18, 2025 · 0 comments
Open

Vito migration guide #2822

RoiEXLab opened this issue Jan 18, 2025 · 0 comments

Comments

@RoiEXLab
Copy link

RoiEXLab commented Jan 18, 2025

So I updated the fresco dependency the other day, and it seems like SimpleDraweeView is now deprecated, recommending to use vito instead. However, the information in the documentation is rather vague so after looking it up I found #2781 which helped clarify things a bit, but a lot of questions still remain.

  1. It seems like vito is completely orthogonal to regular fresco. It seems to use different classes, different everything like a rewrite. Is that the case?
  2. Which dependencies am I supposed to depend on. There are dozens of vito-* dependencies. How do they relate to other dependencies like animated-webp or imagepipeline-okhttp3?
  3. Why do I get compilation errors when I include too few dependencies? I started with vito-view and got compilation errors just from using it until I also added vito-source and vito-options.

This is all really confusing to me, especially because the fresco website with all of the documentation continues to use SimpleDraweeView, even though this class is deprecated. I'm looking forward to get some answers from you.

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

No branches or pull requests

1 participant