Wayland Can Now Handle Virtual Workspaces

[phoronix]

Phoronix: Wayland Can Now Handle Virtual Workspaces

As the latest Wayland progress, patches have emerged so that the reference Weston compositor can handle virtual workspaces...

http://www.phoronix.com/vr.php?view=MTExODQ

[uid313]

Does clipboard work in Wayland?

What happen, if I open a application, copy something, then close it.
Will it still be in the buffer ready for me to paste it, or will it be gone?

[johnc]

It won't be long now until Wayland has a tenth of X's features.

[9a3eedi]

I'm confused here.. I thought workspaces was implemented by the window manager and not the display server.... right? And wasn't Wayland supposed to be a very minimalist approach to a display server?

[89c51]

I'm confused here.. I thought workspaces was implemented by the window manager and not the display server.... right? And wasn't Wayland supposed to be a very minimalist approach to a display server?

The patches are for weston which is the compositing window manager i think (not sure on that). Weston and Wayland are used interchangeably in this case and it creates a bit of confusion.

[asdx]

I'm confused here.. I thought workspaces was implemented by the window manager and not the display server.... right? And wasn't Wayland supposed to be a very minimalist approach to a display server?

The compositor, display server and window manager are the same in Wayland. They're one single entity AFAIK.

http://wayland.freedesktop.org/architecture.html

[TAXI]

The compositor, display server and window manager are the same in Wayland. They're one single entity AFAIK.

You're sure?
What is Weston good for then? And if it's harlinked to Wayland cause it's one single entity, why is it called a reference compositor then?

//EDIT: http://en.wikipedia.org/wiki/Wayland...er_protocol%29
So Wayland is a window manager, but:
"Existing compositing window managers, such as Compiz, KWin, and Mutter are expected to implement Wayland support directly, to become Wayland compositors / display servers."
So Weston is just for testing Wayland and will not be used on desktops when Wayland will replace X, I think.

[asdx]

You're sure?
What is Weston good for then? And if it's harlinked to Wayland cause it's one single entity, why is it called a reference compositor then?

//EDIT: http://en.wikipedia.org/wiki/Wayland...er_protocol%29
So Wayland is a window manager, but:
"Existing compositing window managers, such as Compiz, KWin, and Mutter are expected to implement Wayland support directly, to become Wayland compositors / display servers."
So Weston is just for testing Wayland and will not be used on desktops when Wayland will replace X, I think.

Wayland is the protocol.

Weston is a WM/compositor/display server that uses the Wayland protocol, isn't it?

[Teho]

So Weston is just for testing Wayland and will not be used on desktops when Wayland will replace X, I think.

It will most likely remain as fully featured and very extensible compositor. Like we now have multiple X.org window managers in the future we will have many Wayland compositor and Weston will be one them along side Mutter, KWin, Compiz and others.

[drag]

Weston will probably be to Wayland what TWM is to X Windows.

http://en.wikipedia.org/wiki/Twm