diff options
| author | Jonas Ådahl <jadahl@gmail.com> | 2017-06-21 14:23:44 +0800 |
|---|---|---|
| committer | Jonas Ådahl <jadahl@gmail.com> | 2017-08-29 14:39:04 +0800 |
| commit | 97f2c7c16137355e3c3a64e6e80b7d5512d3b587 (patch) | |
| tree | 8a8b0f5d930d11eea521297749e1bf7fe14705d8 /.gitignore | |
| parent | 38235bc145b13f8d26a0505423b7f7def62e8d22 (diff) | |
| download | mutter-97f2c7c16137355e3c3a64e6e80b7d5512d3b587.tar.gz | |
Add remote desktop and screen cast functionality
This commit adds basic screen casting and remote desktoping
functionalty. This works by exposing two D-Bus API services:
org.gnome.Mutter.ScreenCast and org.gnome.Mutter.RemoteDesktop.
The remote desktop API is used to create remote desktop sessions. For
each session, a D-Bus object is created, and an application can manage
the session by sending messages to the session object. A remote desktop
session the user to emit input events using the D-Bus methods on the
session object. To get framebuffer content, the application should
create an associated screen cast session.
The screen cast API is used to create screen cast sessions. One can so
far either create stand-alone screen cast sessions, or a screen cast
session associated with a remote desktop session. A remote desktop
associated screen cast session is managed by the remote desktop session.
So far only remote desktop managed screen cast sessions are implemented.
Each screen cast session may have one or more streams. A screen cast
stream is a stream of buffers of some part of the compositor content.
So far API exists for creating streams of monitors and windows, but
only monitor streams are implemented.
When a screen cast session is started, the one PipeWire stream is
created for each screen cast stream created for the session. When this
has happened, a PipeWireStreamAdded signal is emitted on the stream
object, passing a unique identifier. The application may use this
identifier to find the associated stream being advertised by the
PipeWire daemon.
The remote desktop and screen cast functionality must be explicitly be
enabled at ./configure time by passing --enable-remote-desktop to
./configure. Doing this will build both screen cast and remote desktop
support.
To actually enable the screen casting and remote desktop, the user must
enable the experimental feature. See
org.gnome.mutter.experimental-features.
https://bugzilla.gnome.org/show_bug.cgi?id=784199
Diffstat (limited to '.gitignore')
| -rw-r--r-- | .gitignore | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore index 56fb267d2..321d7732f 100644 --- a/.gitignore +++ b/.gitignore @@ -71,6 +71,8 @@ src/stamp-meta-enum-types.h src/meta-dbus-display-config.[ch] src/meta-dbus-idle-monitor.[ch] src/meta-dbus-login1.[ch] +src/meta-dbus-remote-desktop.[ch] +src/meta-dbus-screen-cast.[ch] src/gtk-primary-selection-protocol.c src/gtk-primary-selection-server-protocol.h src/gtk-shell-protocol.c |