Re: [Development] Image and PreserveAspectCrop

2016-08-02 Thread Gunnar Sletta
> On 02 Aug 2016, at 18:03, Albert Astals Cid > wrote: > > On Tue, Aug 2, 2016 at 1:56 PM, Gunnar Sletta wrote: >> Hi, >> >> I think the most sensible solution is to handle this inside the image >> provder. When I've seen this problem previously, it has was solved using a >> custom image pr

Re: [Development] Image and PreserveAspectCrop

2016-08-02 Thread Ben Lau
On 2 August 2016 at 19:56, Gunnar Sletta wrote: > Hi, > > I think the most sensible solution is to handle this inside the image > provder. When I've seen this problem previously, it has was solved using a > custom image provider for local files, but as you say, when the resources > are scattered

Re: [Development] Image and PreserveAspectCrop

2016-08-02 Thread Albert Astals Cid
On Tue, Aug 2, 2016 at 1:56 PM, Gunnar Sletta wrote: > Hi, > > I think the most sensible solution is to handle this inside the image > provder. When I've seen this problem previously, it has was solved using a > custom image provider for local files, but as you say, when the resources are > sca

Re: [Development] Image and PreserveAspectCrop

2016-08-02 Thread Shawn Rutledge
> On 02 Aug 2016, at 13:56, Gunnar Sletta wrote: > > A bit unfortunate that we have to add a V2 version of the image provider, > though. Would be nice if we could extend what is already there somehow. > However you end up solving it, it needs to be a bit more flexible than what > you do in th

Re: [Development] Image and PreserveAspectCrop

2016-08-02 Thread Gunnar Sletta
Hi, I think the most sensible solution is to handle this inside the image provder. When I've seen this problem previously, it has was solved using a custom image provider for local files, but as you say, when the resources are scattered across the local and network alike, then you want the defa

Re: [Development] Image and PreserveAspectCrop

2016-08-02 Thread Albert Astals Cid
Ping anyone? On Mon, Jul 18, 2016 at 10:24 AM, Albert Astals Cid wrote: > There is a problem when trying to optimally[*] show an Image with > PreserveAspectCrop fillMode. > [*]optimally => as best looking as possible while using as litte > memory as possible > > You can see that problem in the sc

[Development] Image and PreserveAspectCrop

2016-07-18 Thread Albert Astals Cid
There is a problem when trying to optimally[*] show an Image with PreserveAspectCrop fillMode. [*]optimally => as best looking as possible while using as litte memory as possible You can see that problem in the screenshot at http://i.imgur.com/LSSlFEB.png that corresponds with the code at http://p