brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
67a4cd898e
mutter/.gitignore

131 lines
2.8 KiB
Plaintext
Raw Normal View History

Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
Makefile
Makefile.in
Makefile.in.in
aclocal.m4
autom4te.cache
configure.ac: Modernize autoconf/libtool dependencies and macro usage
2014-06-05 11:11:36 -04:00
build-aux
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
compile
config.guess
config.h
config.h.in
config.log
config.status
config.sub
configure
depcomp
install-sh
Update the Git ignore file
2010-01-18 21:06:31 -05:00
intltool-extract.in
intltool-merge.in
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
libtool
ltmain.sh
missing
.deps
Update .gitignore These aren't generated in the data/ subdir.
2014-06-11 09:24:59 -04:00
50-mutter-navigation.xml
50-mutter-system.xml
50-mutter-windows.xml
mutter.desktop
mutter-wayland.desktop
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
*.o
*.a
*.lo
*.la
.libs
*.swp
Update the Git ignore file
2010-01-18 21:06:31 -05:00
*.gir
*.typelib
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
stamp-h1
*.gmo
*.make
Update .gitignore The cogl/clutter merge made the .gitignore files in the respective directories incorrect, due to the using absolute paths. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-06 02:26:11 -04:00
*.log
*.trs
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
*~
stamp-it
.intltool-merge-cache
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-21 20:13:54 -04:00
ABOUT-NLS
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
POTFILES
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-21 20:13:54 -04:00
Makevars.template
po/*.header
.gitignore: Ignore generated POT file (po/*.pot)
2011-09-27 02:48:13 -04:00
po/*.pot
build: Say good-bye to intltool intltool is unmaintained nowadays while upstream gettext gained support for formats like GSettings schemas and .desktop files, and offers a mechanism to teach it about other XML formats not yet supported out of the box which we can use for the rest. So there's nothing stopping us, just make the switch ... https://bugzilla.gnome.org/show_bug.cgi?id=769073
2016-07-21 20:13:54 -04:00
po/*.sed
po/*.sin
Rules-quot
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
libmutter.pc
mutter
Update .gitignore
2014-07-17 14:49:09 -04:00
mutter-restart-helper
Add a test framework and stacking tests Add a basic framework for tests of Mutter handling of client behavior; mutter-test-runner is a Mutter-based compositor that forks off instances of mutter-test-client and sends commands to them based on scripts. The scripts also include assertions. mutter-test-runner always runs in nested-Wayland mode since the separate copy of Xwayland is helpful in giving a reliably clean X server to test against. Initially the commands and assertions are designed to test the stacking behavior of Mutter, but the framework should be extensible to test other parts of client behavior like focus. The tests are installed according to: https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests if --enable-installed-tests is passed to configure. You can run them uninstalled with: cd src && make run-tests (Not in 'make check' to avoid breaking 'make distcheck' if Mutter can't be run nested.) https://bugzilla.gnome.org/show_bug.cgi?id=736505
2014-09-11 13:43:32 -04:00
mutter-test-client
mutter-test-runner
Update .gitignore
2016-03-21 17:58:09 -04:00
mutter-test-unit-tests
tests: Add headless start test case Test that mutter starts properly when there are no monitors connected yet, and that things work when a monitor is eventually connected. https://bugzilla.gnome.org/show_bug.cgi?id=730551
2017-08-18 02:27:42 -04:00
mutter-test-headless-start-test
Add missing file from test framework mutter-all.test.in was accidentally not committed.
2014-09-12 13:40:33 -04:00
mutter-all.test
Update .gitignore These aren't generated in the data/ subdir.
2014-06-11 09:24:59 -04:00
org.gnome.mutter.gschema.valid
org.gnome.mutter.gschema.xml
org.gnome.mutter.wayland.gschema.valid
org.gnome.mutter.wayland.gschema.xml
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
testasyncgetprop
testboxes
testgradient
Update .gitignore
2013-09-16 16:55:31 -04:00
m4/*
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
INSTALL
mkinstalldirs
Install enum types
2015-07-06 00:58:45 -04:00
meta-enum-types.[ch]
src/stamp-meta-enum-types.h
Remove "xrandr" from the name of the generated DBus files It's about generic display config, not XRandR specifically.
2014-03-31 23:33:01 -04:00
src/meta-dbus-display-config.[ch]
Update .gitignore
2013-08-23 18:23:01 -04:00
src/meta-dbus-idle-monitor.[ch]
launcher: Replace mutter-launch with logind integration This uses David Herrmann's new logind sessions interface to retrieve fds for input devices, rather than using a custom setuid helper to do the management. This vastly simplifies the interface. This requires systemd v210, at least. https://bugzilla.gnome.org/show_bug.cgi?id=724604
2013-12-31 17:44:45 -05:00
src/meta-dbus-login1.[ch]
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
2017-06-21 02:23:44 -04:00
src/meta-dbus-remote-desktop.[ch]
src/meta-dbus-screen-cast.[ch]
wayland: Add gtk-primary-selection protocol This protocol is an internal mirror of the primary selection drafts being proposed for wayland-protocols. No changes besides prefix/suffix changes. https://bugzilla.gnome.org/show_bug.cgi?id=762560
2016-02-23 13:51:10 -05:00
src/gtk-primary-selection-protocol.c
src/gtk-primary-selection-server-protocol.h
Update .gitignore
2014-03-18 22:08:04 -04:00
src/gtk-shell-protocol.c
src/gtk-shell-server-protocol.h
Update .gitignore
2015-12-14 18:17:40 -05:00
src/xdg-shell-unstable-v*-protocol.c
src/xdg-shell-unstable-v*-server-protocol.h
src/pointer-gestures-unstable-v*-protocol.c
src/pointer-gestures-unstable-v*-server-protocol.h
wayland: Implement support for wp_relative_pointer Add support for sending relative pointer motion deltas to clients who request such events by creating wp_relative_pointer objects via wp_relative_pointer_manager. This currently implements the unstable version 1 from wayland-protocols. https://bugzilla.gnome.org/show_bug.cgi?id=744104
2015-06-02 04:26:34 -04:00
src/relative-pointer-unstable-v*-protocol.c
src/relative-pointer-unstable-v*-server-protocol.h
Implement support for the wp_pointer_constraints protocol The wp_pointer_constraints protocol is a protocol which enables clients to manipulate the behavior of the pointer cursor associated with a seat. Currently available constraints are locking the pointer to a static position, and confining the pointer to a given region. Currently locking is fully implemented, and confining is implemented for rectangular confinement regions. What else is lacking is less troublesome semantics for enabling the lock or confinement; currently the only requirement implemented is that the window that appears focused is the one that may aquire the lock. This means that a pointer could be 'stolen' by creating a new window that receives active focus, or when using focus-follows-mouse, a pointer passes a window that has requested a lock. This semantics can be changed and the protocol itself allows any semantics as seems fit. https://bugzilla.gnome.org/show_bug.cgi?id=744104
2015-06-17 00:10:52 -04:00
src/pointer-constraints-unstable-v*-protocol.c
src/pointer-constraints-unstable-v*-server-protocol.h
wayland: Add support for the xdg-foreign protocol This commits adds support for exporting xdg_surface handles via xdg_exporter and importing them via xdg_importer. This bumps the required wayland-protocols version to 1.6. https://bugzilla.gnome.org/show_bug.cgi?id=769786
2015-09-23 20:05:25 -04:00
src/xdg-foreign-unstable-v*-protocol.c
src/xdg-foreign-unstable-v*-server-protocol.h
wayland: Add xdg-output support The xdg-output protocol aims at describing outputs in way which is more in line with the concept of an output on desktop oriented systems. For now it just features the position and logical size which describe the output position and size in the global compositor space. This is however much useful for Xwayland to advertise the output size and position to X11 clients which need this to configure their surfaces in the global compositor space as the compositor may apply a different scale from what is advertised by the output scaling property (to achieve fractional scaling, for example). This was added in wayland-protocols 1.10. https://bugzilla.gnome.org/show_bug.cgi?id=787363
2017-09-05 12:53:41 -04:00
src/xdg-output-unstable-v1-protocol.c
src/xdg-output-unstable-v1-server-protocol.h
wayland: Add Xwayland grab keyboard support This protocol is limited to Xwayland only and is not visible/usable by any other client. Mutter uses the following mechanisms to determine if an X11 client should be granted a grab: - is "xwayland-allow-grabs" set? - if set, is the client blacklisted? - otherwise, has the client set the X11 window property _XWAYLAND_MAY_GRAB_KEYBOARD on the window using a client message? - if not, is it a client white-listed either via the default system list or the settings "xwayland-grab-access-rules"? https://bugzilla.gnome.org/show_bug.cgi?id=783342
2016-08-30 03:20:49 -04:00
src/xwayland-keyboard-grab-unstable-v1-protocol.c
src/xwayland-keyboard-grab-unstable-v1-server-protocol.h
.gitignore: Add more things to ignore Various protocol files had not been added. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
2017-12-12 23:16:19 -05:00
src/tablet-unstable-v*-protocol.c
src/tablet-unstable-v*-server-protocol.h
src/keyboard-shortcuts-inhibit-unstable-v*-protocol.c
src/keyboard-shortcuts-inhibit-unstable-v*-server-protocol.h
src/linux-dmabuf-unstable-v*-protocol.c
src/linux-dmabuf-unstable-v*-server-protocol.h
wayland: Add support for stable xdg-shell This commit adds support for xdg_shell (the stable version). This was done by first copying the old xdg-shell unstable v6 implementation into a separate .c .h file pair (including various symbol renaming) then porting the old xdg-shell unstable v6 implementation to the new stable version. https://gitlab.gnome.org/GNOME/mutter/merge_requests/5 https://bugzilla.gnome.org/show_bug.cgi?id=791938
2017-12-22 03:37:44 -05:00
src/xdg-shell-protocol.c
src/xdg-shell-server-protocol.h
meta: Add generated meta-version.h Avoid populating *_VERSION constants through cflags in pkg-config-file which could be overridden by the project using it. Properly prefix the defines with META_ to make gi-scanner happy.
2014-06-05 08:05:16 -04:00
src/meta/meta-version.h
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
src/libmutter-*.pc
Build reference docs https://bugzilla.gnome.org/show_bug.cgi?id=676856
2011-11-02 11:17:43 -04:00
doc/reference/*.args
doc/reference/*.bak
doc/reference/*.hierarchy
doc/reference/*.interfaces
doc/reference/*.prerequisites
doc/reference/*.signals
doc/reference/*.stamp
doc/reference/html/
doc/reference/xml/
docs: Fix cross-reference generation https://bugzilla.gnome.org/show_bug.cgi?id=676856
2013-02-18 08:19:28 -05:00
doc/reference/meta-decl-list.txt
doc/reference/meta-decl.txt
doc/reference/meta-overrides.txt
doc/reference/meta-undeclared.txt
doc/reference/meta-undocumented.txt
doc/reference/meta-unused.txt
Improve a bit the look of the main page of the API docs https://bugzilla.gnome.org/show_bug.cgi?id=695641
2013-03-11 11:49:24 -04:00
doc/reference/meta-docs.sgml
doc/reference/meta.types
Update .gitignore
2014-03-18 13:03:55 -04:00
gtk-doc.m4
intltool.m4
libtool.m4
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
Update .gitignore It seems the new automake likes to litter these files all around.
2014-03-31 23:47:40 -04:00
.dirstamp
project: add **/tags.* to gitignore Builds adds lots of them in the source tree.
2017-08-20 09:37:33 -04:00
**/tags.*
Reference in New Issue Copy Permalink