You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
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?
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.
The text was updated successfully, but these errors were encountered:
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.animated-webp
orimagepipeline-okhttp3
?vito-view
and got compilation errors just from using it until I also addedvito-source
andvito-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.The text was updated successfully, but these errors were encountered: