non-Unity flavours and Mir
thomas.voss at canonical.com
Fri Jun 14 16:41:33 UTC 2013
On Fri, Jun 14, 2013 at 6:27 PM, Jonathan Riddell <jr at jriddell.org> wrote:
> On Fri, Jun 14, 2013 at 11:47:43PM +0800, Ma Xiaojun wrote:
>> KDE, this one is interesting. The one even tries to support
>> proprietary OS. The same also claim their CI has very limited distro
>> coverage so they cannot support distro specific feature. Maybe we
>> replace Kwin with something else then problem solved (KDE run on
>> proprietary OS without Kwin)
> KDE having some applications running on Windows and Mac is irrelevant
> to this conversation.
> We're not going to drop KDE's compositor and window manager.
I wouldn't have assumed that. But from a technical perspective, I'm
trying to understand why kwin couldn't be integrated with Mir. Judging
from the recent development with respect to a Wayland backend in KWin,
I got the impression that kwin's overall architecture is meant to be
pluggable to different windowing systems/compositors. I would be happy
to start looking into this if someone from the KDE/kwin team could
work together with me and guide me through the code.
Do you think that makes sense?
>> I believe that there is nothing technically wrong with Mir or it is
>> fixable. If upstreams have political problems, what can we do?
> It's not a case of technical problems it's a case of Mir being
> different for no paticular advantage. It's a political problem of
> Canonical's making not KDE's. And the question is indeed what can we
> do in Ubuntu.
I cannot give a political answer here but would like to resort to the
technical help offered before and evaluate how we could support KDE
(or more specifically kwin) best on Mir.
> ubuntu-devel mailing list
> ubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
More information about the ubuntu-devel