Ffimageloading: Should we include Transformations in a `Xamarin.FFImageLoading` nuget package?

[daniel-luberda]

Should we include Transformations in a Xamarin.FFImageLoading nuget package and depreciate Xamarin.FFImageLoading.Transformations? Those dlls are quite small actually (~20KB dll for each platform)

VOTE: https://goo.gl/cBYbjE

[hardcodet]

Not sure whether it's beyond the scope of thisrefactoring, but it looks like you had great code for general image processing here (e.g. scaling, rotating, getting image information etc.). Exposing that functionality for generic use during a refactoring would be awesome.

One of many scenarios: Rather than just downscaling a profile picture in the control, using your library code to actually scale it down before storing it on the backend.

[daniel-luberda]

@hardcodet Actually, it is now supported (latest prerelease). You can now do something like this:

C# var output = await ImageService.Instance .LoadCompiledResource("image.png") .Transform(new SomeTransformation()) .AsPNGStreamAsync();

[softwaremills]

I would be fine with including Transformations in the base package. What I wish was that iOS WebP support was a separate package, since that's a 1.2MB dependency I don't use.

[daniel-luberda]

@softwaremills I made another issue for your WebP package request: https://github.com/luberda-molinet/FFImageLoading/issues/710

[softwaremills]

Thanks a bunch, Daniel! I appreciate it!

[daniel-luberda]

https://github.com/luberda-molinet/FFImageLoading/issues/859