If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Wayland Demonstration At XDS 2010

09-18-2010, 05:50 AM

Phoronix: Wayland Demonstration At XDS 2010

While the Wayland Display Server is not being discussed officially in any of the talks at the X.Org Developers' Summit in Toulouse, it has been mentioned a few times during other talks and can commonly be heard in discussions between Intel and Nokia developers outside of the event. At the pre-event I also discussed Wayland for a short time with Kristian Høgsberg, the project's founder, where it was learned Intel may deploy Wayland in MeeGo Touch, among other facts. Wayland was also brought up by Kristian during his talk on libxkbcommon, which is a common XKB library for keyboard input that can also be utilized by Wayland...

Comment

Can someone explain what exactly Wayland is? I read that is started in 2007 by Red Hat engineer, as replacement for X. Now it seems like it is some additional protocol to go with X. I suppose that is better idea than replacing X altogether, there are lot of thing that depend on X...

Is there any in-depth explanation of Wayland. how it works and how it interacts with X?

Comment

Can someone explain what exactly Wayland is? I read that is started in 2007 by Red Hat engineer, as replacement for X. Now it seems like it is some additional protocol to go with X. I suppose that is better idea than replacing X altogether, there are lot of thing that depend on X...

Is there any in-depth explanation of Wayland. how it works and how it interacts with X?

It can replace X, but it can also run X applications using a rootles X server and composite them together with the native Wayland apps. A bit like Mac OS X's window system - it doesn't need X but can provide the backward compatibility.

Comment

Wayland would be the bare minimal network protocol for a modern GPU stack?
I really have to look further into it.

Wayland is X, stripped of all the old stuff, geared at the future, acting more or less as R&D in practise. It's not network oriented. To achieve network computing and 'legacy' compatibility it can use Xserver. It's much more abstract. Porting GTK/Qt has been discussed and porting GTK is in the works (or so I believe; news is scarce).

It started as a hobby project by a Red Hat employe. It's not realy that much of a hobby project anymore in the sense that Intel and Nokia are planning to use Wayland for Meamo; it's great for embedded systems.

There is the possibility that, over time, X.org will grow, but not fully, towards Wayland, due to Waylands 'new tech', where proven.

Comment

Wayland is X, stripped of all the old stuff, geared at the future, acting more or less as R&D in practise. It's not network oriented. To achieve network computing and 'legacy' compatibility it can use Xserver. It's much more abstract. Porting GTK/Qt has been discussed and porting GTK is in the works (or so I believe; news is scarce).

It started as a hobby project by a Red Hat employe. It's not realy that much of a hobby project anymore in the sense that Intel and Nokia are planning to use Wayland for Meamo; it's great for embedded systems.

There is the possibility that, over time, X.org will grow, but not fully, towards Wayland, due to Waylands 'new tech', where proven.

What are the differences between wayland and GTK/Clutter ported to use directly libdrm/gallium3d/libxkb?
If they want to use it for meego, it shall be C++/Qt (erk!), wouldn't it?
(I'm sad to see the C dependency swapped for a C++ dependency in meego)