What version of fresco first supported Vito?

[snijsure]

Description

I have looked through fresco release notes and unfortunately haven't found first release where Vito support was first added.

I am looking to migrate large project from Glide to Fresco. The simpleviewee change is going to complicate things. Then watched one of the old droidcon presentations that mentioned Vito. So very much interested in knowing what version fresco first supported Vito.

Also lot of documentation still refers to simpleviewee, is there documentation around use of Vito?

Thanks for any help!!

Additional Information

• Fresco version: [FILL THIS OUT]
• Platform version: [FILL THIS OUT: specific to a particular Android version? Device?]

[oprisnik]

Hey! Thanks for reaching out.

The first Vito version was part of 2.5.0, but as an alpha: https://repo.maven.apache.org/maven2/com/facebook/fresco/vito-view/

So you'd have to specify the version as [2.5.0-alpha/](https://repo.maven.apache.org/maven2/com/facebook/fresco/vito-view/2.5.0-alpha/)

I would recommend to use more recent versions since we made significant improvements to Vito since then.

Regarding migrating from Drawee to Vito, we've started to update our sample apps, and you can look at the migration changes for example for Showcase. such as this one: 0bb6fee

[snijsure]

Thanks for the pointer. Curious to know how calls like these will look like when using Vito objects. I will keep an eye on the samples.

            val roundingParams = RoundingParams.asCircle()
            imageView.hierarchy.roundingParams = roundingParams

Also to execute image request like this when using Vito.

            val imageRequestBuilder =
                ImageRequestBuilder
                    .newBuilderWithSource(Uri.parse(url))
                    .setProgressiveRenderingEnabled(true)

            val imageRequest = imageRequestBuilder.build()
            val controller =
                Fresco
                    .newDraweeControllerBuilder()
                    .setImageRequest(imageRequest)
                    .setOldController(imageView.controller)
                    .setTapToRetryEnabled(true)
                    .build()
            imageView.setController(controller)

[oprisnik]

For the first case, rounding options:

val imageOptions = ImageOptions.create().round(RoundingOptions.asCircle()).build()

VitoView.show(uri, imageOptions, imageView)

For the second case:

// Ideally you'd only create this once and pass the same imageOptions object to all images
val imageOptions = ImageOptions.create().progressiveRendering(true).build()

VitoView.show(Uri.parse(url), imageOptions, imageView)

With the caveat that the tap to retry handling is only available for Litho at the moment via FrescoVitoTapToRetryImageSpec:

fresco/vito/litho/src/main/java/com/facebook/fresco/vito/litho/FrescoVitoTapToRetryImageSpec.kt

Line 4 in b45dcb0

* This source code is licensed under the MIT license found in the

Since Vito is directly operating on ImageView.

However, adding a custom ImageListener as shown in FrescoVitoTapToRetryImageSpec and tracking whether the image is loaded and handling the tap accordingly should be straightforward. If you'd like to contribute, this is a good opportunity to create a simple TapToRetryImageView based on the Litho variant.