Re: [Interest] QtQuick2 image rendering and custom shader overhead

2013-05-06 Thread Preet
> Using ShaderEffectSource or "Item.layer: true" does mean going through an > FBO. Using ShaderEffect alone or with a plain Image element can be almost > the same as using a plain Image element. I say "can" as the content of the > shader greatly impacts the resulting performance. > > If you do: > >

Re: [Interest] QtQuick2 image rendering and custom shader overhead

2013-05-06 Thread Sean Harmer
On Monday 06 May 2013 06:39:06 Sletta Gunnar wrote: > On May 5, 2013, at 11:47 AM, Sean Harmer wrote: > > On 04/05/2013 19:30, Preet wrote: > >> Hi, > > ... > > >> 2. > >> I'd like to use ShaderEffects to apply a somewhat trivial shader to most > >> of the images in my application. The images ar

Re: [Interest] QtQuick2 image rendering and custom shader overhead

2013-05-05 Thread Sletta Gunnar
On May 5, 2013, at 11:47 AM, Sean Harmer wrote: > On 04/05/2013 19:30, Preet wrote: >> Hi, ... >> >> 2. >> I'd like to use ShaderEffects to apply a somewhat trivial shader to most of >> the images in my application. The images are black and white icons, and I'd >> like to use shaders to cha

Re: [Interest] QtQuick2 image rendering and custom shader overhead

2013-05-05 Thread Sean Harmer
On 04/05/2013 19:30, Preet wrote: Hi, I have a couple of questions regarding images in QtQuick2. 1. For a resolution independent application, I tried using several images (all 128x128px) that I scaled as appropriate for target devices. In QtQuick1 this didn't work out so well -- scaling the i

[Interest] QtQuick2 image rendering and custom shader overhead

2013-05-04 Thread Preet
Hi, I have a couple of questions regarding images in QtQuick2. 1. For a resolution independent application, I tried using several images (all 128x128px) that I scaled as appropriate for target devices. In QtQuick1 this didn't work out so well -- scaling the images was expensive and made the appli