23 Dec
2011
23 Dec
'11
5:48 p.m.
On Thursday 22 December 2011 15:17:13 Calvin Morrison wrote:
As for the packaging issue, I'd rather let users
install the standard Kwin
repository provided by their distribution.
Oh I think having a different KWin with
less dependencies just for Trinity
would be just fine. That's what we do for Plasma Active, where KWin is
compiled with completely different compile flags (e.g. no Window Decorations).
Also in 4.8 the standard KWin is built twice with different dependencies: once
the classic KWin with OpenGL and once as kwin_gles with OpenGL ES 2.0.
So having some build options to e.g. disable Nepomuk integration and Plasma
integration should be possible and could result in a kwin_trinity binary or
something in that direction.
Maybe we could get a command
line setting to disable Akonadi/Nepomuk (or whatever way we can configure
it easily) even if it is available? I think that would be a good way to
avoid the overhead while still using the upstream packages.
At least Akonadi is
never used by KWin. Nepomuk is indirectly used through
Activities. I have never tried running KWin standalone since Activities were
introduced, so I don't know whether the daemon is started. But I think it's
not.
I want to reiterate how time limited the project is
already. I think almost
all new features are being pushed back to R14.
Exactly! And that's one of the
reasons why I want to push for KWin in Trinity.
It takes away the burden to develop a window manager and hands it of to those
who do it anyway. And as I said in the end only the users matter :-)
Thank you for taking the time to work with us,
Thanks as well for considering
working together with KDE. I really hope that
those two siblings can come closer together again in 2012 :-)
Merry Christmas
Martin Gräßlin