isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-24 09:00:42 -05:00
Code Issues Packages Projects Releases Wiki Activity
cfb3d10e1b
mutter/src/wayland/protocol/gtk-shell.xml

52 lines
1.6 KiB
XML
Raw Normal View History

Add a private gtk-mutter protocol Add a new interface, gtk_shell, than can be used by gtk to retrieve a surface extension called gtk_surface, which will be used to communicate with mutter all the GTK extensions to EWMH https://bugzilla.gnome.org/show_bug.cgi?id=707128 Add support for GTK application menus To do so, we need to be able to set surface state before creating the MetaWindow, so we introduce MetaWaylandSurfaceInitialState as a staging area. The gtk-shell-surface implementation would either write to the initial state, or directly to the window. At the same, implement set_title and set_class too, because it's easy enough. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 03:40:36 -04:00
<protocol name="gtk">
wayland: Don't invent our own unstable protocol semantics The gtk_shell protocol used some half baked unstable protocol semantics that worked by only allowing binding the exact version of the interface. This hack is a bit too confusing and it makes it impossible to do any compatible changes without breaking things. So, instead rename it to include a number in the interface names. This way we can add requests and events without causing compatibility issues, and we can later remove requests and events by bumping the number in the interface names. https://bugzilla.gnome.org/show_bug.cgi?id=763284
2016-03-06 22:33:03 -05:00
<interface name="gtk_shell1" version="1">
wayland: Kill clients who try to bind an incompatible gtk_shell version gtk_shell is not backward compatible, and clients binding to it should check whether the advertised version is the same as the client supports. https://bugzilla.gnome.org/show_bug.cgi?id=745720
2015-03-05 05:09:35 -05:00
<description summary="gtk specific extensions">
gtk_shell is a protocol extension providing additional features for
wayland: Don't invent our own unstable protocol semantics The gtk_shell protocol used some half baked unstable protocol semantics that worked by only allowing binding the exact version of the interface. This hack is a bit too confusing and it makes it impossible to do any compatible changes without breaking things. So, instead rename it to include a number in the interface names. This way we can add requests and events without causing compatibility issues, and we can later remove requests and events by bumping the number in the interface names. https://bugzilla.gnome.org/show_bug.cgi?id=763284
2016-03-06 22:33:03 -05:00
clients implementing it.
wayland: Kill clients who try to bind an incompatible gtk_shell version gtk_shell is not backward compatible, and clients binding to it should check whether the advertised version is the same as the client supports. https://bugzilla.gnome.org/show_bug.cgi?id=745720
2015-03-05 05:09:35 -05:00
</description>
Add a private gtk-mutter protocol Add a new interface, gtk_shell, than can be used by gtk to retrieve a surface extension called gtk_surface, which will be used to communicate with mutter all the GTK extensions to EWMH https://bugzilla.gnome.org/show_bug.cgi?id=707128 Add support for GTK application menus To do so, we need to be able to set surface state before creating the MetaWindow, so we introduce MetaWaylandSurfaceInitialState as a staging area. The gtk-shell-surface implementation would either write to the initial state, or directly to the window. At the same, implement set_title and set_class too, because it's easy enough. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 03:40:36 -04:00
<enum name="capability">
<entry name="global_app_menu" value="1"/>
<entry name="global_menu_bar" value="2"/>
wayland: Sync protocol/gtk-shell.xml from GTK+ Had added a new capability enum value. https://bugzilla.gnome.org/show_bug.cgi?id=745720
2015-03-05 21:40:07 -05:00
<entry name="desktop_icons" value="3"/>
Add a private gtk-mutter protocol Add a new interface, gtk_shell, than can be used by gtk to retrieve a surface extension called gtk_surface, which will be used to communicate with mutter all the GTK extensions to EWMH https://bugzilla.gnome.org/show_bug.cgi?id=707128 Add support for GTK application menus To do so, we need to be able to set surface state before creating the MetaWindow, so we introduce MetaWaylandSurfaceInitialState as a staging area. The gtk-shell-surface implementation would either write to the initial state, or directly to the window. At the same, implement set_title and set_class too, because it's easy enough. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 03:40:36 -04:00
</enum>
<event name="capabilities">
<arg name="capabilities" type="uint"/>
</event>
<request name="get_gtk_surface">
wayland: Don't invent our own unstable protocol semantics The gtk_shell protocol used some half baked unstable protocol semantics that worked by only allowing binding the exact version of the interface. This hack is a bit too confusing and it makes it impossible to do any compatible changes without breaking things. So, instead rename it to include a number in the interface names. This way we can add requests and events without causing compatibility issues, and we can later remove requests and events by bumping the number in the interface names. https://bugzilla.gnome.org/show_bug.cgi?id=763284
2016-03-06 22:33:03 -05:00
<arg name="gtk_surface" type="new_id" interface="gtk_surface1"/>
Add a private gtk-mutter protocol Add a new interface, gtk_shell, than can be used by gtk to retrieve a surface extension called gtk_surface, which will be used to communicate with mutter all the GTK extensions to EWMH https://bugzilla.gnome.org/show_bug.cgi?id=707128 Add support for GTK application menus To do so, we need to be able to set surface state before creating the MetaWindow, so we introduce MetaWaylandSurfaceInitialState as a staging area. The gtk-shell-surface implementation would either write to the initial state, or directly to the window. At the same, implement set_title and set_class too, because it's easy enough. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 03:40:36 -04:00
<arg name="surface" type="object" interface="wl_surface"/>
</request>
wayland: Update gtk-shell protocol file to v3 Add a gtk_shell.set_startup_id request, so the application can communicate to the compositor the startup id that it received through the DESKTOP_STARTUP_ID envvar, or other means. https://bugzilla.gnome.org/show_bug.cgi?id=762268
2016-02-06 09:02:13 -05:00
wayland: Don't invent our own unstable protocol semantics The gtk_shell protocol used some half baked unstable protocol semantics that worked by only allowing binding the exact version of the interface. This hack is a bit too confusing and it makes it impossible to do any compatible changes without breaking things. So, instead rename it to include a number in the interface names. This way we can add requests and events without causing compatibility issues, and we can later remove requests and events by bumping the number in the interface names. https://bugzilla.gnome.org/show_bug.cgi?id=763284
2016-03-06 22:33:03 -05:00
<request name="set_startup_id">
wayland: Update gtk-shell protocol file to v3 Add a gtk_shell.set_startup_id request, so the application can communicate to the compositor the startup id that it received through the DESKTOP_STARTUP_ID envvar, or other means. https://bugzilla.gnome.org/show_bug.cgi?id=762268
2016-02-06 09:02:13 -05:00
<arg name="startup_id" type="string" allow-null="true"/>
</request>
wayland: Add system bell support via gtk_shell Add a system_bell request to gtk_shell. A client can use this to invoke the system bell, be it aural, visual or none at all. Currently per window visual bell support is not implemented. https://bugzilla.gnome.org/show_bug.cgi?id=763284
2016-03-06 23:47:48 -05:00
<request name="system_bell">
<arg name="surface" type="object" interface="gtk_surface1" allow-null="true"/>
</request>
Add a private gtk-mutter protocol Add a new interface, gtk_shell, than can be used by gtk to retrieve a surface extension called gtk_surface, which will be used to communicate with mutter all the GTK extensions to EWMH https://bugzilla.gnome.org/show_bug.cgi?id=707128 Add support for GTK application menus To do so, we need to be able to set surface state before creating the MetaWindow, so we introduce MetaWaylandSurfaceInitialState as a staging area. The gtk-shell-surface implementation would either write to the initial state, or directly to the window. At the same, implement set_title and set_class too, because it's easy enough. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 03:40:36 -04:00
</interface>
wayland: Don't invent our own unstable protocol semantics The gtk_shell protocol used some half baked unstable protocol semantics that worked by only allowing binding the exact version of the interface. This hack is a bit too confusing and it makes it impossible to do any compatible changes without breaking things. So, instead rename it to include a number in the interface names. This way we can add requests and events without causing compatibility issues, and we can later remove requests and events by bumping the number in the interface names. https://bugzilla.gnome.org/show_bug.cgi?id=763284
2016-03-06 22:33:03 -05:00
<interface name="gtk_surface1" version="1">
Add a private gtk-mutter protocol Add a new interface, gtk_shell, than can be used by gtk to retrieve a surface extension called gtk_surface, which will be used to communicate with mutter all the GTK extensions to EWMH https://bugzilla.gnome.org/show_bug.cgi?id=707128 Add support for GTK application menus To do so, we need to be able to set surface state before creating the MetaWindow, so we introduce MetaWaylandSurfaceInitialState as a staging area. The gtk-shell-surface implementation would either write to the initial state, or directly to the window. At the same, implement set_title and set_class too, because it's easy enough. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 03:40:36 -04:00
<request name="set_dbus_properties">
<arg name="application_id" type="string" allow-null="true"/>
<arg name="app_menu_path" type="string" allow-null="true"/>
<arg name="menubar_path" type="string" allow-null="true"/>
<arg name="window_object_path" type="string" allow-null="true"/>
<arg name="application_object_path" type="string" allow-null="true"/>
<arg name="unique_bus_name" type="string" allow-null="true"/>
</request>
wayland: Add and implement set/unset_modal for the gtk_surface interface Add set_modal ond unset_modal to the gtk_surface interface. When a surface is modal, the compositor can treat it differently from non-modal dialogs, for example attach it to the parent window if any. There is currently no changes to input device focus; it is up to the client to ignore events to the parent surface that is wanted. This bumps the gtk_shell version to 2. https://bugzilla.gnome.org/show_bug.cgi?id=745720
2015-03-05 22:44:42 -05:00
<request name="set_modal"/>
<request name="unset_modal"/>
wayland: Add gtk_surface.present to gtk-shell This commits adds a gtk_surface.present request and its implementation. The timestamp is assumed to be from some input event that the client responded to. The timestamps we deal with when managing windows will usually come from two different clocks: CLOCK_MONOTONIC if they come from libinput/evdev, or CLOCK_MONOTONIC_COARSE if they come from the X server. Luckily these are quite similar, the difference beeing that the X server timestamps having lower resolution, so we can just pass the timestamps no matter where they came from and it'll most likely work fine, except for the race condition described in bug 756272 which might happen here too until it is properly fixed. https://bugzilla.gnome.org/show_bug.cgi?id=763295
2016-03-08 03:33:27 -05:00
<request name="present">
<arg name="time" type="uint"/>
</request>
Add a private gtk-mutter protocol Add a new interface, gtk_shell, than can be used by gtk to retrieve a surface extension called gtk_surface, which will be used to communicate with mutter all the GTK extensions to EWMH https://bugzilla.gnome.org/show_bug.cgi?id=707128 Add support for GTK application menus To do so, we need to be able to set surface state before creating the MetaWindow, so we introduce MetaWaylandSurfaceInitialState as a staging area. The gtk-shell-surface implementation would either write to the initial state, or directly to the window. At the same, implement set_title and set_class too, because it's easy enough. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 03:40:36 -04:00
</interface>
</protocol>
Reference in New Issue Copy Permalink