From 972dd094292b5735432dfbc7a1ab84a965acdc34 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20=C3=85dahl?= Date: Fri, 15 Jul 2016 22:01:55 +0800 Subject: [PATCH] xdg-shell: Drop desktop environment specific state allocations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Instead of allocating state ranges that desktop environments can use as they want, let them introduce their own protocol and their own enums. If such desktop environment protocols need the configure/ack_configure semantics, they can design their protocols to extend xdg_surface, and make their private configure events a latched state tied to xdg_surface.configure. Signed-off-by: Jonas Ã…dahl Acked-by: Quentin Glidic --- unstable/xdg-shell/xdg-shell-unstable-v6.xml | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/unstable/xdg-shell/xdg-shell-unstable-v6.xml b/unstable/xdg-shell/xdg-shell-unstable-v6.xml index d3abe5b..b0044d8 100644 --- a/unstable/xdg-shell/xdg-shell-unstable-v6.xml +++ b/unstable/xdg-shell/xdg-shell-unstable-v6.xml @@ -684,18 +684,6 @@ States set in this way are double-buffered. They will get applied on the next commit. - - Desktop environments may extend this enum by taking up a range of - values and documenting the range they chose in this description. - They are not required to document the values for the range that they - chose. Ideally, any good extensions from a desktop environment should - make its way into standardization into this enum. - - The current reserved ranges are: - - 0x0000 - 0x0FFF: xdg-shell core values, documented below. - 0x1000 - 0x1FFF: GNOME - 0x2000 - 0x2FFF: EFL