Review Request: an overlay effect element for framesvg

[Marco Martin]

On Monday 12 January 2009, Aaron J. Seigo wrote:
> On Monday 12 January 2009, Marco Martin wrote:
> > On Monday 12 January 2009, Aaron J. Seigo wrote:
> > > * random position whenever a widget is created. this would result in
> > > every widget having a (potentially) unique position, and this position
> > > would change between launches of plasma.
> >
> > hmm, fear it would look messy and most important it would kill the cache
>
> ah, btw, the cache issue is probably nothing to be concerned about. just
> cache the background *and* the overlay separately and render them together
> on paint. obviously this will be slower than having a small number (for
> various values of "small") completely pre-rendered backgrounds. but it
> would not blow the cache.
ok so an update on the thing...
last version of the patch still uses the name but i've separed the overlay 
generation to be cached separately...
but i'm not really convinced on that, for instance framePixmap() would became 
sooo slower (and maybe memory consumption is higher too, since i always have 
the overlay in memory cache?) ..

if the possible positions are not that much (lets say something like on the 4 
corners) maybe using a single pixmap for caching would still be possible?
or maybe just if the position is consistent across instances the impact on 
cache would still be acceptable hmm

buut maybe i'm making up problems that there arent...


for the randomness: i would say still indicize in the cache for the applet 
name but attach it to random numbers that controls the actual positioning.
the correspondence saved in a config file? like the one for element rects?
(hmm the thing is becoming complex...)