[compiz] Move KDE Plasma Integration to KDE Git Infrastructure

[Sam Spilsbury]

Hi All,

Sorry I haven't gotten into this earlier, I have been busy fixing bugs
and doing other things. Most points have been covered though, so I'll
just add some things which could be interesting to consider. I agree
with the general premise of where the discussion is going, and think
that the best time to look into this is after 0.9.4 when I start to
look at the modularization of compiz code again.

> I don't agree with this conclusion, though: Releasing KWD with KDE just
> moves the code-is-broken-due-to-unsynced-release problem from 'KWD is broken
> when KDE code is changed' to 'KWD is broken when Compiz code is changed'.
> I'm not sure how that improves things, especially given that Compiz 0.8
> (which is still widely used) and Compiz 0.9 have different decoration APIs
> (to accomodate non-composited rendering and reparenting in 0.9).
>

As a small aside, I think it should be possible to merge the 0.8 and
0.9 decorators and change functionality depending on which decoration
API is supported (we announce it in the property). I'll look into this
once I get back to looking at further modularization of git
components. I have a working version of this in fact, but nobody
really looked at it so it never got merged in.


>
>> 3. Part of KWin. That is same as option 2, plus you could use KWin
>> internal
>> code. E.g. no need to duplicate decoration code any more, make use of KWin
>> parts separated from core (e.g. Alt+Tab). This is probably the best
>> integration you could get.
>
> Taking aside the point that Alt+Tab is implemented in the plugins, not the
> decorator (which only renders the tabbox frame), I must say that personally
> the look of Kwin's Alt+Tab implementation is one of the things that makes me
> use compiz on KDE ;-)
>
>> Personally I would prefer option 3 from an integration point of view. My
>> current plans are to modulize KWin which would allow to make use of more
>> KWin
>> features.
>

I think it would be interesting to discuss at the Desktop Summit and
beforehand on wm-spec a standard for pushing UI componentry into the
compositing manager (with wayland and such in mind here), in a
standard way (like Ayatana is doing now with libappindicator and
libdbusmenu + dee). Pretty much everyone is doing it differently now,
and this fragmentation is probably going to become problematic soon I
think.

Cheers,

Sam



-- 
Sam Spilsbury