On Tuesday, June 18, 2013 04:52:56 PM Robert Ancell wrote:
> On Tue, Jun 18, 2013 at 4:33 PM, Scott Kitterman
<ubuntu@kitterman.com>wrote:
> > On Monday, June 17, 2013 09:52:49 PM Oliver Ries wrote:
> > > On Fri, Jun 14, 2013 at 11:12 AM, Scott Kitterman
> >
> > <ubuntu@kitterman.com>wrote:
> > Part of the problem is that no one outside Canonical know enough to really
> > have an informed opinion. Here are some immediate questions that come to
> >
> > mind:
> > - How invasive would Mir integration be? Is it isolated enough that it
> >
> > could
> > be integrated upstream based on our testing?
>
> It depends on how KWin plans to support non-X display servers.
>
> Options that I know of are:
> a) KWin implements a Wayland display server component from scratch (a lot
> of work)
> b) KWin is a plugin to Weston
> c) KWin uses an existing Wayland display server library (none exist that I
> know of)
>
> In case a) you would need to implement a Mir backend as well as a Wayland
> backend
> In case b) you would need a libmirserver backend in Weston
> In case c) you would have to modify the library or it would need to allow
> backends to be added
Wayland support (at the for developers only , don't file bugs that don't come
with a patch level of maturity) is supposed to be built into the source for
Kwin for KDE SC 4.11 (of which we have in beta one of in saucy right now), so
it'll be A or B. Someone who understands such things might have a look at the
source and see, I expect from your description it'll be reasonably obvious to
someone who knows much about this (i.e. not me).
Scott K
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
