Re: [PATCH 2/2 v2] Add keyboard shortcuts inhibitor

[Peter Hutterer]

On Fri, Mar 31, 2017 at 05:31:41PM +0200, Olivier Fourdan wrote:
> This adds a new protocol to let Wayland clients specify that they want
> all keyboard events to be send to the client, regardless of the
> compositor own shortcuts.
> 
> This is for use by virtual machine and remote connections viewers.
> 
> Signed-off-by: Olivier Fourdan 
> ---
>  v2: Clarify that that the compositor is under no obligation to ignore
>  every shortcut (ajax)
>  Add "inhibit_active" and "inhibit_inactive" events to notify clients
>  Add "already_inhibited" error


i'd just go for active/inactive because we already have a interface-based
namespace anyway. but either way, this looks good now, thanks.

Note that there's an indentation issue in inhibit_inactive (tab/space mixup)

Cheers,
   Peter

> 
>  unstable/keyboard-shortcuts-inhibit/README |   4 +
>  .../keyboard-shortcuts-inhibit-unstable-v1.xml | 133 
> +
>  2 files changed, 137 insertions(+)
>  create mode 100644 unstable/keyboard-shortcuts-inhibit/README
>  create mode 100644 
> unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
> 
> diff --git a/unstable/keyboard-shortcuts-inhibit/README 
> b/unstable/keyboard-shortcuts-inhibit/README
> new file mode 100644
> index 000..929959c
> --- /dev/null
> +++ b/unstable/keyboard-shortcuts-inhibit/README
> @@ -0,0 +1,4 @@
> +Compositor shortcut inhibit protocol
> +
> +Maintainers:
> +Olivier Fourdan 
> diff --git 
> a/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
>  
> b/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
> new file mode 100644
> index 000..7a2b919
> --- /dev/null
> +++ 
> b/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
> @@ -0,0 +1,133 @@
> +
> +
> +
> +  
> + Copyright © 2017 Red Hat Inc.
> +
> + Permission is hereby granted, free of charge, to any person obtaining a
> + copy of this software and associated documentation files (the 
> "Software"),
> + to deal in the Software without restriction, including without 
> limitation
> + the rights to use, copy, modify, merge, publish, distribute, sublicense,
> + and/or sell copies of the Software, and to permit persons to whom the
> + Software is furnished to do so, subject to the following conditions:
> +
> + The above copyright notice and this permission notice (including the 
> next
> + paragraph) shall be included in all copies or substantial portions of 
> the
> + Software.
> +
> + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
> OR
> + IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
> + THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR 
> OTHER
> + LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> + FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
> + DEALINGS IN THE SOFTWARE.
> +  
> +
> +  
> + This protocol specifies a way for a client to request the compositor
> + to ignore its own keyboard shortcuts, so that all keyboard events
> + get forwarded to a surface.
> +
> + Warning! The protocol described in this file is experimental and
> + backward incompatible changes may be made. Backward compatible
> + changes may be added together with the corresponding interface
> + version bump.
> + Backward incompatible changes are done by bumping the version
> + number in the protocol and interface names and resetting the
> + interface version. Once the protocol is to be declared stable,
> + the 'z' prefix and the version number in the protocol and
> + interface names are removed and the interface version number is
> + reset.
> +  
> +
> +  
> +
> +
> +  
> + Destroy the keyboard shortcuts inhibitor manager.
> +  
> +
> +
> +
> +  
> + Create a new keyboard shortcuts inhibitor object associated with the 
> given surface.
> +
> + If shortcuts are already inhibited for the given surface, a protocol 
> error
> + "already_inhibited" is raised by the compositor.
> +  
> +   interface="zwp_keyboard_shortcuts_inhibitor_v1"/>
> +   +summary="the surface that inhibits the keyboard shortcuts behavior"/>
> +
> +
> +  
> +
> +  
> +
> + A keyboard shortcuts inhibitor instructs the compositor to ignore
> + its own keyboard shortcuts when the associated surface has keyboard
> + focus. As a result, when the surface is focused, it will receive all
> + keyboard events, even those which would normally be caught by the
> + compositor for its own shortcuts.
> +
> + The Wayland compositor is however under no obligation to disable
> + all of its shortcuts, and may keep some 

Re: [PATCH 1/2] Introduce keyboard grabbing protocol for Xwayland

[Quentin Glidic]

On 4/2/17 2:57 AM, Peter Hutterer wrote:

woohoo, grabs. My favourite topic! ;)
On Wed, Mar 22, 2017 at 05:27:22PM +0100, Olivier Fourdan wrote:

>> [snip]

+  
+   This protocol specifies a way for Xwayland to request all keyboard
+   events to be forwarded to a surface even when the surface does not
+   have keyboard focus.
+
+   Unlike the X11 protocol, Wayland doesn't have the notion of
+   active grab on the keyboard.
+
+   When an X11 client acquires an active grab on the keyboard, all
+   key events are reported only to the grabbing X11 client.
+   When running in Xwayland, X11 applications may acquire an active
+   grab but that cannot be translated to the Wayland compositor who
+   may set the input focus to some other surface, thus breaking the
+   X11 client assumption that all key events are reported.
+
+   When an X11 client requests a keyboard grab, the Wayland compositor
+   may either inform or ask the user for the right to forward all key
+   events to the given client surface.


this is confusing :) paragraph 3 talks aobut what's not working and
paragraph 4 about what this protocol should fix. How about something like:

 This protocol is application-specific to meet the needs of the X11
 protocol through Xwayland. It provides a way for XWayland to request
 all keyboard events to be forwarded to a surface even when the
 surface does not have keyboard focus.

 In the X11 protocol, a client may request an "active grab" on the
 keyboard. On success, all key events are reported only to the
 grabbing X11 client. For details, see XGrabKeyboard(3).

 The core Wayland protocol does not have a notion of an active
 keyboard grab. When running in Xwayland, X11 applications may
 acquire an active grab inside XWayland but that cannot be translated
 to the Wayland compositor who may set the input focus to some other
 surface. In doing so, it breaks the X11 client assumption that all
 key events are reported to the grabbing client.

This protocol specifies a way for Xwayland to request all keyboard
 be directed to the given surface. The protocol does not guarantee
 that the compositor will honor this request and it does not
 prescribe user interfaces on how to handle the respond. For example,
 a compositor may inform the user that all key events are now
 forwarded to the given client surface, or it may ask the user for
 permission to do so.

 Warning! Things may go boom... etc. etc.


I think it may be worth it to add a little safety net:
“Compositors are required to restrict this interface to Xwayland alone, 
and raise a protocol error for native Wayland clients.”


Cheers,

--

Quentin “Sardem FF7” Glidic
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: [PATCH 2/2] Add keyboard shortcuts inhibitor

[Peter Hutterer]

On Wed, Mar 22, 2017 at 05:27:23PM +0100, Olivier Fourdan wrote:
> This adds a new protocol to let Wayland clients specify that they want
> all keyboard events to be send to the client, regardless of the
> compositor own shortcuts.
> 
> This is for use by virtual machine and remote connections viewers.

I think it should have a blurb to state that it's still the compositor that
decides whether any given shortcut is inhibited, but otherwise this looks
good, thanks.

Cheers,
   Peter

> 
> Signed-off-by: Olivier Fourdan 
> ---
>  unstable/keyboard-shortcuts-inhibit/README |  4 +
>  .../keyboard-shortcuts-inhibit-unstable-v1.xml | 85 
> ++
>  2 files changed, 89 insertions(+)
>  create mode 100644 unstable/keyboard-shortcuts-inhibit/README
>  create mode 100644 
> unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
> 
> diff --git a/unstable/keyboard-shortcuts-inhibit/README 
> b/unstable/keyboard-shortcuts-inhibit/README
> new file mode 100644
> index 000..929959c
> --- /dev/null
> +++ b/unstable/keyboard-shortcuts-inhibit/README
> @@ -0,0 +1,4 @@
> +Compositor shortcut inhibit protocol
> +
> +Maintainers:
> +Olivier Fourdan 
> diff --git 
> a/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
>  
> b/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
> new file mode 100644
> index 000..f68e25a
> --- /dev/null
> +++ 
> b/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
> @@ -0,0 +1,85 @@
> +
> +
> +
> +  
> + Copyright © 2017 Red Hat Inc.
> +
> + Permission is hereby granted, free of charge, to any person obtaining a
> + copy of this software and associated documentation files (the 
> "Software"),
> + to deal in the Software without restriction, including without 
> limitation
> + the rights to use, copy, modify, merge, publish, distribute, sublicense,
> + and/or sell copies of the Software, and to permit persons to whom the
> + Software is furnished to do so, subject to the following conditions:
> +
> + The above copyright notice and this permission notice (including the 
> next
> + paragraph) shall be included in all copies or substantial portions of 
> the
> + Software.
> +
> + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
> OR
> + IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
> + THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR 
> OTHER
> + LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> + FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
> + DEALINGS IN THE SOFTWARE.
> +  
> +
> +  
> + This protocol specifies a way for a client to request the compositor
> + to ignore its own keyboard shortcuts, so that all keyboard events
> + get forwarded to a surface.
> +
> + Warning! The protocol described in this file is experimental and
> + backward incompatible changes may be made. Backward compatible
> + changes may be added together with the corresponding interface
> + version bump.
> + Backward incompatible changes are done by bumping the version
> + number in the protocol and interface names and resetting the
> + interface version. Once the protocol is to be declared stable,
> + the 'z' prefix and the version number in the protocol and
> + interface names are removed and the interface version number is
> + reset.
> +  
> +
> +  
> +
> +
> +  
> + Destroy the keyboard shortcuts inhibitor manager.
> +  
> +
> +
> +
> +  
> + Create a new keyboard shortcuts inhibitor object associated with the 
> given surface.
> +  
> +   interface="zwp_keyboard_shortcuts_inhibitor_v1"/>
> +   +summary="the surface that inhibits the keyboard shortcuts behavior"/>
> +
> +
> +  
> +
> +  
> +
> + A keyboard shortcuts inhibitor instructs the compositor to ignore
> + its own keyboard shortcuts when the associated surface has keyboard
> + focus. As a result, when the surface is focused, it will receive all
> + keyboard events, even those which would normally be caught by the
> + compositor for its own shortcuts.
> +
> + If the surface is destroyed, unmapped, or loses keyboard focus, the
> + the compositor will restore its own keyboard shortcuts.
> +
> + If the surface regains keyboard focus the inhibitor will take effect
> + again.
> +
> +
> +
> +  
> + Remove the keyboard shortcuts inhibitor from the associated wl_surface.
> +  
> +
> +
> +  
> +
> -- 
> 2.9.3
> 

> ___
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> 

Re: [RFC wayland] move away from C

[The Rasterman]

On Sat, 1 Apr 2017 09:41:51 -0500 Derek Foreman  said:

> On 01/04/17 09:24 AM, Carsten Haitzler (The Rasterman) wrote:
> > On Sat, 1 Apr 2017 14:03:21 +0100 Auke Booij  said:
> >
> >> The C programming language was developed in the early '70s. It was
> >> always considered a proof of concept, as it was clear to everyone
> >> involved that any serious programming lanugage should have a garbage
> >> collector. Indeed, Dennis Ritchie is widely known to have said:
> >>
> >> "What I would really like is to extend this prototype into a garbage
> >> collected, multi-paradigm, modern programming language, supported by a
> >> major player in the industry."
> >>
> >> Of course, the language thus envisioned would later be implemented as
> >> C pound (not to be confused with the cloud programming language #C).
> >>
> >> Let's catch up to 1990 and translate major parts of wayland to the
> >> language of the people - haskell.
> >
> > ummm... how about no?
> 
> Don't read the internets on April 1st.

good point. i totally didnt know what date it was... :)

> Thanks,
> Derek
> 
> >
> >> Some early code can be found here:
> >> https://github.com/abooij/sudbury
> >> Existing wayland clients run without recompilation. Compositors are
> >> not supported yet.
> >> ___
> >> wayland-devel mailing list
> >> wayland-devel@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/wayland-devel
> >
> >
> 
> ___
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel


-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com

___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: [RFC wayland] move away from C

[The Rasterman]

On Sat, 1 Apr 2017 09:41:51 -0500 Derek Foreman  said:

> On 01/04/17 09:24 AM, Carsten Haitzler (The Rasterman) wrote:
> > On Sat, 1 Apr 2017 14:03:21 +0100 Auke Booij  said:
> >
> >> The C programming language was developed in the early '70s. It was
> >> always considered a proof of concept, as it was clear to everyone
> >> involved that any serious programming lanugage should have a garbage
> >> collector. Indeed, Dennis Ritchie is widely known to have said:
> >>
> >> "What I would really like is to extend this prototype into a garbage
> >> collected, multi-paradigm, modern programming language, supported by a
> >> major player in the industry."
> >>
> >> Of course, the language thus envisioned would later be implemented as
> >> C pound (not to be confused with the cloud programming language #C).
> >>
> >> Let's catch up to 1990 and translate major parts of wayland to the
> >> language of the people - haskell.
> >
> > ummm... how about no?
> 
> Don't read the internets on April 1st.

oh good. point. i had no idea what date it was :)

> Thanks,
> Derek
> 
> >
> >> Some early code can be found here:
> >> https://github.com/abooij/sudbury
> >> Existing wayland clients run without recompilation. Compositors are
> >> not supported yet.
> >> ___
> >> wayland-devel mailing list
> >> wayland-devel@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/wayland-devel
> >
> >
> 


-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com

___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: [PATCH 1/2] Introduce keyboard grabbing protocol for Xwayland

[Peter Hutterer]

woohoo, grabs. My favourite topic! ;)

Mostly ok, a few complaints regarding the documentation but the protocol is
fine from my POV.

On Wed, Mar 22, 2017 at 05:27:22PM +0100, Olivier Fourdan wrote:
> This patch introduces a new protocol for grabbing the keyboard from
> Xwayland.
> 
> This is needed for X11 applications that map an override redirect window
> (ths not focused by the window manager) and issue an active grab on the

/me buys a 'u'

> keyboard to capture all keyboard events.
> 
> Signed-off-by: Olivier Fourdan 
> ---
>  Makefile.am|   2 +
>  configure.ac   |   2 +-
>  unstable/xwayland-keyboard-grab/README |   4 +
>  .../xwayland-keyboard-grab-unstable-v1.xml | 101 
> +
>  4 files changed, 108 insertions(+), 1 deletion(-)
>  create mode 100644 unstable/xwayland-keyboard-grab/README
>  create mode 100644 
> unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml
> 
> diff --git a/Makefile.am b/Makefile.am
> index e693afa..d100c13 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -12,6 +12,8 @@ unstable_protocols =
> \
>   unstable/tablet/tablet-unstable-v2.xml  
> \
>   unstable/xdg-foreign/xdg-foreign-unstable-v1.xml
> \
>   unstable/idle-inhibit/idle-inhibit-unstable-v1.xml  
> \
> + unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml  
> \
> + 
> unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
>  \
>   $(NULL)
>  
>  stable_protocols =   
> \
> diff --git a/configure.ac b/configure.ac
> index fbb0ec2..e98bceb 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -1,7 +1,7 @@
>  AC_PREREQ([2.64])
>  
>  m4_define([wayland_protocols_major_version], [1])
> -m4_define([wayland_protocols_minor_version], [7])
> +m4_define([wayland_protocols_minor_version], [8])
>  m4_define([wayland_protocols_version],
>[wayland_protocols_major_version.wayland_protocols_minor_version])
>  
> diff --git a/unstable/xwayland-keyboard-grab/README 
> b/unstable/xwayland-keyboard-grab/README
> new file mode 100644
> index 000..dbe45a5
> --- /dev/null
> +++ b/unstable/xwayland-keyboard-grab/README
> @@ -0,0 +1,4 @@
> +Xwayland keyboard grabbing protocol
> +
> +Maintainers:
> +Olivier Fourdan 
> diff --git 
> a/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml 
> b/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml
> new file mode 100644
> index 000..31dc365
> --- /dev/null
> +++ b/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml
> @@ -0,0 +1,101 @@
> +
> +
> +
> +  
> + Copyright © 2017 Red Hat Inc.
> +
> + Permission is hereby granted, free of charge, to any person obtaining a
> + copy of this software and associated documentation files (the 
> "Software"),
> + to deal in the Software without restriction, including without 
> limitation
> + the rights to use, copy, modify, merge, publish, distribute, sublicense,
> + and/or sell copies of the Software, and to permit persons to whom the
> + Software is furnished to do so, subject to the following conditions:
> +
> + The above copyright notice and this permission notice (including the 
> next
> + paragraph) shall be included in all copies or substantial portions of 
> the
> + Software.
> +
> + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
> OR
> + IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
> + THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR 
> OTHER
> + LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> + FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
> + DEALINGS IN THE SOFTWARE.
> +  
> +
> +  
> + This protocol specifies a way for Xwayland to request all keyboard
> + events to be forwarded to a surface even when the surface does not
> + have keyboard focus.
> +
> + Unlike the X11 protocol, Wayland doesn't have the notion of
> + active grab on the keyboard.
> +
> + When an X11 client acquires an active grab on the keyboard, all
> + key events are reported only to the grabbing X11 client.
> + When running in Xwayland, X11 applications may acquire an active
> + grab but that cannot be translated to the Wayland compositor who
> + may set the input focus to some other surface, thus breaking the
> + X11 client assumption that all key events are reported.
> +
> + When an X11 client requests a keyboard grab, the Wayland compositor
> + may either 

Re: [RFC wayland] move away from C

[Derek Foreman]

On 01/04/17 09:24 AM, Carsten Haitzler (The Rasterman) wrote:

On Sat, 1 Apr 2017 14:03:21 +0100 Auke Booij  said:


The C programming language was developed in the early '70s. It was
always considered a proof of concept, as it was clear to everyone
involved that any serious programming lanugage should have a garbage
collector. Indeed, Dennis Ritchie is widely known to have said:

"What I would really like is to extend this prototype into a garbage
collected, multi-paradigm, modern programming language, supported by a
major player in the industry."

Of course, the language thus envisioned would later be implemented as
C pound (not to be confused with the cloud programming language #C).

Let's catch up to 1990 and translate major parts of wayland to the
language of the people - haskell.


ummm... how about no?


Don't read the internets on April 1st.

Thanks,
Derek




Some early code can be found here:
https://github.com/abooij/sudbury
Existing wayland clients run without recompilation. Compositors are
not supported yet.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel





___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: [RFC wayland] move away from C

[The Rasterman]

On Sat, 1 Apr 2017 14:03:21 +0100 Auke Booij  said:

> The C programming language was developed in the early '70s. It was
> always considered a proof of concept, as it was clear to everyone
> involved that any serious programming lanugage should have a garbage
> collector. Indeed, Dennis Ritchie is widely known to have said:
> 
> "What I would really like is to extend this prototype into a garbage
> collected, multi-paradigm, modern programming language, supported by a
> major player in the industry."
> 
> Of course, the language thus envisioned would later be implemented as
> C pound (not to be confused with the cloud programming language #C).
> 
> Let's catch up to 1990 and translate major parts of wayland to the
> language of the people - haskell.

ummm... how about no?

> Some early code can be found here:
> https://github.com/abooij/sudbury
> Existing wayland clients run without recompilation. Compositors are
> not supported yet.
> ___
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel


-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com

___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel

[RFC wayland] move away from C

[Auke Booij]

The C programming language was developed in the early '70s. It was
always considered a proof of concept, as it was clear to everyone
involved that any serious programming lanugage should have a garbage
collector. Indeed, Dennis Ritchie is widely known to have said:

"What I would really like is to extend this prototype into a garbage
collected, multi-paradigm, modern programming language, supported by a
major player in the industry."

Of course, the language thus envisioned would later be implemented as
C pound (not to be confused with the cloud programming language #C).

Let's catch up to 1990 and translate major parts of wayland to the
language of the people - haskell.

Some early code can be found here:
https://github.com/abooij/sudbury
Existing wayland clients run without recompilation. Compositors are
not supported yet.
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel