> nice clean protocol for these in much the same vein as a proper systray
> > spec, would be nice.
>
> agreed, though i'm not really sure what the real world benefits of these
> "windicators" will be; for them to be really compelling, imho, a good amount
> of d
uot;seamless" frame+title+app+bg experience. (the rest is just mechanics on
> > agreeing on atom names to use, where to stick properties and what they
> > mean and which data to expose/fetch where in what way).
> >
> > am i on the same page?
> No :-) The idea is to get a standard on how clients and wm can activate
> effects, animations and so on.
>
> I put a very first, very KDE-centric draft online:
> http://blog.martin-graesslin.com/blog/wp-
> content/uploads/2010/08/compositing.pdf.tar.gz
--
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
exists and can be provided, and then how the app will
request it for the purpose of getting a "seamless" frame+title+app+bg
experience. (the rest is just mechanics on agreeing on atom names to use, where
to stick properties and what they mean and which data to expose/fetch where in
what wa
