Wayland Becomes A FreeDesktop.org Project

[Zapp!]

It is possible, KWin have been ported to Windows (I don't know if it still work or if the work have even been merged). I don't know that much about Wayland, but KWin is not that dependent on X11.

I wonder where you got that from (maybe this aprils fools joke?).
KWin is a X window manager with optional compositing support, nothing else. Thus it heavily depends on X technology.

Qt has its own form of window management built in, which wayland is being ported to.

Some details about it here. I wonder how this will work/look in the end...

[Wielkie G]

Wayland doesn't use something called "window manager". With X11, apps only draw contents of windows, and frame + title bar is drawn by window manager. With Wayland, like e.g. MS Windows, apps draw not only contents, but also the title bar, etc. This is why screenshots of gtk+/qt on Wayland show windows without title bar (it's simply not drawn at all by these toolkits on X11).

But about *compositing* managers... I'm not that much into Wayland

[89c51]

can somebody explain the situation with the window managers compositors etc on Wayland??

things like Kwin Metacity/Mutter Enlightenment Compiz just have to slightly modify the code to target wayland right??

[V!NCENT]

Wayland is realy starting to take off

If it could have a remote desktop X11 replacement extention then that would be great!

[xir_]

So if wayland is a compositor then does that mean it will have problems with running compiz? (thinking that it would be hard to port gnome 3 and the like)

[pingufunkybeat]

KWin is an X window manager. Of course it does all sorts of things highly tied to the X Window System.

KWin does use Qt, but it's not ALL it uses.

[89c51]

It is possible, KWin have been ported to Windows (I don't know if it still work or if the work have even been merged). I don't know that much about Wayland, but KWin is not that dependent on X11.

doesn't porting a toolkit to wayland automaticaly means that the apps using it can run on it???

ie KWin is written in Qt (as i read in wikipedia) and qt is being ported to wayland as we speak

[smitty3268]

It is possible, KWin have been ported to Windows (I don't know if it still work or if the work have even been merged). I don't know that much about Wayland, but KWin is not that dependent on X11.

Are you sure about that? I don't think KWin was ever ported, it was just the plasma shell (running with the normal windows window manager) and I thought I remembered reading at the time that there was no plan to port over Kwin because it was heavily, heavily dependent on X, and because most people just would want plasma anyway.

[staalmannen]

This is exciting. If someone made some kind of WayBuntu, I'd totally use it. GTK/Qt strict application compatibility? Fine, That's how I roll anyways because of my global menu bar and RGBA translucency usage. Incompatability with nVidia proprietary drivers? I'm using Nouveau with Gallium3D right now.

I want to see what kind of power consumption can be managed playing 3d games with less context switching and strict render-on-page-flipping. Why render 230 FPS with tearing when you can render 1/2x or 1x refresh rate with no tearing and lower power usage?

I wonder if it is time for the Wine developers to consider moving from X to a portable backend like Qt or Cairo, which not only would enable games on Wayland, directfb or whatever while still possible to run on X11. It would also enable running "standard" Wine on OSX with no X11 dependencies.

[ethana2]

Woah

This is exciting. If someone made some kind of WayBuntu, I'd totally use it. GTK/Qt strict application compatibility? Fine, That's how I roll anyways because of my global menu bar and RGBA translucency usage. Incompatability with nVidia proprietary drivers? I'm using Nouveau with Gallium3D right now.

I want to see what kind of power consumption can be managed playing 3d games with less context switching and strict render-on-page-flipping. Why render 230 FPS with tearing when you can render 1/2x or 1x refresh rate with no tearing and lower power usage?