This is the official release for Wayland 1.24.
Aside from the usual bug fixes and protocol clarifications, this new
release includes:
- A new wl_fixes interface to add a request to destroy a wl_registry
object.
- A new wl_keyboard.key repeated state, to allow compositors to take
over the
This is the RC3 release for Wayland 1.24.
Full commit history below.
Demi Marie Obenour (1):
connection: Do not busy-loop if a message exceeds the buffer size
Simon Ser (1):
build: bump version to 1.23.93
git tag: 1.23.93
https://gitlab.freedesktop.org/wayland/wayland/-/releases
wayland-protocols 1.45 is now available.
This release adds two new staging protocols:
* Background effects - apply effects to transparent parts of a surface
that requires compositor side implementation.
* Pointer warp - complementary to the pointer confinement and pointer
locking
This is the RC2 release for Wayland 1.24.
Full commit history below.
Caitlyn Stewart (1):
connection: fix segfault in wl_closure_invoke()
Kirill Primak (1):
client: fix conversion specifier in the discarded event log message
Matt Turner (4):
tests: Make `tests` dict elements
t;s1:c0", and
> so only be accessable to processes containing category c0 and a
> sensitivity of s1 or greater.
>
> Thus far, there have been two potential dataflows within Wayland we
> have looked into. The first is related to clipboard access and
> drag-and-drop. If a copy
> What's worse is that in the client side, there is no way to tell what failed.
> System calls can be traced to see their return values, and X11 error events
> exist, but Wayland has neither unless you disconnect the client.
For debug purposes, there are the compositor logs
This is the RC1 release for Wayland 1.24.
Aside from the usual bug fixes and protocol clarifications, this new
release includes:
- A new wl_fixes interface to add a request to destroy a wl_registry
object.
- A new wl_keyboard.key repeated state, to allow compositors to take
over the
Thanks for the feedback! It seems like everybody is on board for
skipping alphas/betas, so let's try that. We can always go back to the
old process later if we realize it was valuable.
Simon
to RCs for libwayland itself seems
> > reasonable. But, do we even need those? Could we go straight to
> > release since the churn is so low?
>
> I think it's better to start with skipping alpha/beta for now, so that
> there is at least *some* testing before things end
On Tue, 20 May 2025 19:11:06 +
"Sloane, Brandon" wrote:
> > -Original Message-
> > From: Pekka Paalanen
> > Sent: Tuesday, May 20, 2025 4:58 AM
> > To: Sloane, Brandon
> > Cc: wayland-devel@lists.freedesktop.org
> > Subject: Re: [RFC
wrote:
> Hi all,
>
> With years passing by, development in the main Wayland repository has
> slowed down quite a bit, activity has moved over to wayland-protocols
> and compositors. However, cutting a new Wayland release is still a
> heavyweight process: it takes at least one an
From: Alyssa Ross
Sent: Wednesday, May 21, 2025 1:28 PM
To: Sloane, Brandon
Cc: wayland-devel@lists.freedesktop.org; Pekka Paalanen
Subject: RE: [RFC] Wayland Security Modules
"Sloane, Brandon" writes:
>> -Original Message-
>> From: Pekka Paalanen
>
"Sloane, Brandon" writes:
> I'm not sure how the pop-os/cosmic-comp PR is relevent. It seems to be about
> exposing cosmic-comp as a library in general. While potentially useful,
> several other compositors have been doing that for a while, and it doesn't
> seem inform security decisions.
Yea
"Sloane, Brandon" writes:
>> -Original Message-
>> From: Pekka Paalanen
>> Sent: Tuesday, May 20, 2025 4:58 AM
>> To: Sloane, Brandon
>> Cc: wayland-devel@lists.freedesktop.org
>> Subject: Re: [RFC] Wayland Security Modules
>>
>&
On Wed, May 21, 2025 at 05:43:09AM -0400, Neal Gompa wrote:
> On Tue, May 20, 2025 at 4:03 PM Simon Ser wrote:
> >
> > Hi all,
> >
> > With years passing by, development in the main Wayland repository has
> > slowed down quite a bit, activity has moved
On Wednesday, May 21st, 2025 at 11:43, Neal Gompa wrote:
> Funnily enough, I think wlroots should probably have them since
> wlroots releases are so highly disruptive for basically every
> consumer...
wlroots has them since the last release.
> That said, going straight to RCs for libwayland its
On Tue, May 20, 2025 at 08:03:02PM +, Simon Ser wrote:
> Hi all,
>
> With years passing by, development in the main Wayland repository has
> slowed down quite a bit, activity has moved over to wayland-protocols
> and compositors. However, cutting a new Wayland release is still
On Tue, May 20, 2025 at 4:03 PM Simon Ser wrote:
>
> Hi all,
>
> With years passing by, development in the main Wayland repository has
> slowed down quite a bit, activity has moved over to wayland-protocols
> and compositors. However, cutting a new Wayland release is still a
>
Hi all,
With years passing by, development in the main Wayland repository has
slowed down quite a bit, activity has moved over to wayland-protocols
and compositors. However, cutting a new Wayland release is still a
heavyweight process: it takes at least one and a half months with at
least 3 pre
> -Original Message-
> From: Pekka Paalanen
> Sent: Tuesday, May 20, 2025 4:58 AM
> To: Sloane, Brandon
> Cc: wayland-devel@lists.freedesktop.org
> Subject: Re: [RFC] Wayland Security Modules
>
> On Mon, 19 May 2025 15:48:04 +
> "Sloane, Brandon&quo
On Mon, 19 May 2025 15:48:04 +
"Sloane, Brandon" wrote:
> Hello,
>
> I've spent the past few months prototyping a security modules system
> for Wayland. Our specific motivation for this is to support SELinux
> integration to meet some rather unique security re
Hello,
I've spent the past few months prototyping a security modules system for
Wayland. Our specific motivation for this is to support SELinux integration to
meet some rather unique security requirements. However, what we are proposing
here is a rather general purpose security module s
You may find one of these projects helpful:
https://github.com/rvaiya/warpd
https://github.com/moverest/wl-kbptr
https://github.com/gabcoh/keynav-wayland
https://github.com/tadeokondrak/waypoint
I believe all of them support the virtual-pointer protocol.
Mine (waypoint) supports libei as well
Hi Zarif,
On Fri, 16 May 2025 at 11:54, Zarif Atai wrote:
> Dear subscribers of wayland-devel,
>
> As a Vim motions enthusiast, it bothers me that there are too many
> situations where I'm forced to use a pointer input device (e.g. a mouse) to
> perform an action. I loo
On Wed, May 14, 2025 at 11:27:50PM +, Zarif Atai wrote:
> Dear subscribers of wayland-devel,
>
> As a Vim motions enthusiast, it bothers me that there are too many situations
> where I'm forced to use a pointer input device (e.g. a mouse) to perform an
> action. I loo
Dear subscribers of wayland-devel,
As a Vim motions enthusiast, it bothers me that there are too many situations
where I'm forced to use a pointer input device (e.g. a mouse) to perform an
action. I looked around to see if anyone has developed a tool that would allow
me to move or telepor
Hello Wayland developers,
I wanted to share my perspective as a Linux user with motor disabilities
regarding Wayland's architecture and its implications for accessibility.
PERSONAL BACKGROUND:
I navigate computers using a Quha Zono 2 (gyroscopic air mouse) for cursor
movement, dwell cli
wayland-protocols 1.44 is now available.
This release adds a new protocol - color representation - which allows
clients to provide metadata about how primarily its YCbCr buffer
contents should be interpreted.
Jonas Ådahl (1):
build: Bump version to 1.44
Sebastian Wick (1):
staging
wayland-protocols 1.43 is now available.
This release adds a new protocol - toplevel tags - which enables clients
to tag toplevels in a script friendly way.
This release also adds toplevel edge constraints to xdg-shell, which
enables compositors to let clients know in what ways window edges are
wayland-protocols 1.42 is now available.
This release includes a new version of the cursor shape protocol, adding
more cursor shapes, as well as a new version of the tablet protocol,
adding bus type information and support for relative dials.
Jonas Ådahl (1):
build: Bump version to 1.42
wayland-protocols 1.41 is now available.
This release includes the long awaited color management protocol, which
allows clients to describe their content's colors accurately, and
compositors to display it properly. It also enables, among other things,
compositors and clients to support
wayland-protocols doesn't have a release schedule, releases are done
on-demand. A perfectly valid way is to send an E-mail here, or ask for
one on IRC.
1.40 is, FWIW, now tagged and released.
Jonas
On Tue, Jan 28, 2025 at 06:50:15PM -0500, James Ramsey wrote:
> I'm asking beca
wayland-protocols 1.40 is now available.
This release includes a new version of the ext-idle-notify protocol, which
allows users of the protocol to track only input device like activity.
Apart from that, there are the usual clarifications and protocol bug fixes.
James Ramsey (1):
ext
I'm asking because there are pull/merge requests for four compositor
implementations (wlroots, KD) of the updated ext-idle-notify protocol
that are about ready to go, and the main thing holding up those
requests from being merged is that wayland-protocols 1.40 isn't out
yet.
I did n
On Tue, Jan 28, 2025 at 6:50 PM James Ramsey wrote:
>
> I'm asking because there are pull/merge requests for four compositor
> implementations (wlroots, KD)
Argh, I'm doing terribly for my first message here. The list of
compositors should be wlroots, KWin, Smithay, and Hyprland.
I'm asking because there are pull/merge requests for four compositor
implementations (wlroots, KD) of the updated ext-idle-notify protocol
that are about ready to go, and the main thing holding up those
requests from being merged is that wayland-protocols 1.40 isn't out
yet.
I did n
.
wayland-protocols 1.39 is now available.
This new release contains two new protocols:
* ext-data-control - allow privileged clients to control data devices, e.g. a
clipboard manager.
* ext-workspace - receive events about and control workspaces, useful for
e.g. workspace indicators
Hi,
I'm trying to create a second Wayland display on Chromium OS(wayland-1):
#include
int main(int argc, char *argv[]) {
struct wl_display *display = wl_display_create();
const char *socket = wl_display_add_socket_auto(display);
wl_display_run(display);
return 0;
}
But I can&
Hacking
Hello,
The following patches (submitted by you) have been updated in Patchwork:
* wayland: [v5,01/11] tests: fix main symbol duplication
- http://patchwork.freedesktop.org/patch/285814/
- for: Wayland (DEPRECATED - USE GITLAB)
was: New
now: Accepted
* wayland: [v5,02/11
wayland-protocols 1.38 is now available.
This full packed release comes with three new staging protocols:
* system bell - allowing e.g. terminal emulators to hand off system
bell alerts to the compositor for among other things accessibility
purposes
* fifo - for implementing first in
training, cost,
course content, duration of the training (approx.)
Training Name
webOS graphics (trainer can suggest apt name basis the topics)
Objective
The objective of this training is to provide participants with a strong
understanding of the Wayland protocol, develop skills in Wayland
Dear Team
I hope this email finds you well.
I am Channa Raj, Founder of Vebsters, a corporate training organization.
We are currently working on a critical training project for our client
and have an requirement for a specialized training session on Wayland -
WebOS Graphics.
We would
wayland-protocols 1.37 is now available.
This release contains three new protocols:
* xdg-toplevel-icon
Associate an icon with a toplevel window.
* ext-image-capture-source
* ext-image-copy-capture
A set of protocols that together allow capturing the pixel content of
outputs and toplevels
This is a bugfix release for Wayland 1.23.
Joaquim Monteiro (1):
meson: Fix use of install_data() without specifying install_dir
Kirill Primak (1):
Put WL_DEPRECATED in front of the function declarations
Sebastian Wick (1):
client: Handle proxies with no queue
Simon Ser (4
The "June 05, 2024" entry refers to the Weston 13.0.3 release, not a
Wayland one.
Hello
You announce the version wayland 1.23.0 but on the Wayland website the
version is 13.0.3 dated June 2024?
Le 13/01/2023 à 13:13, Matti Ristimäki a écrit :
Hi,
Any tips, where/how to debug RDP related problem with Wayland/Weston.
Not kind of sure if this is Weston problem or Qt problem…
Goal:
Trying to create a RDP connection to a Qt GUI-application.
[Service]
# Requires systemd-notify.so
s DOS, Win32, Linux framebuffer, Linux KMS/DRM, Linux X11 and Linux
Wayland since the previous version.
The Wayland videodriver was new in MGRX version 1.5.0 and must be considered in
beta stage. Only the i386 and x86_64 platforms are tested.
In this version I have improved the Wayland d
framebuffer, Linux KMS/DRM, Linux X11 and
> Linux Wayland since the previous version.
>
> The Wayland videodriver was new in MGRX version 1.5.0 and must be considered
> in beta stage. Only the i386 and x86_64 platforms are tested.
>
> In this version I have improved the Waylan
Hi everybody
MGRX is a small 2D graphics C library derived from the GRX library. GRX
was originaly written by Csaba Biegl for DJ Delorie's DOS port of the
GCC compiler.
MGRX supports DOS, Win32, Linux framebuffer, Linux KMS/DRM, Linux X11
and Linux Wayland since the previous version.
. I
> use Gnome Magnifier, set to between 6X and 10X magnification. It works
> well with Xorg, but not with Wayland. I’ve heard some distros,
> including Ubuntu will eventually use only Wayland. That’s a problem for
> me, and for other visually impaired users.
>
> At 6X magnifi
I’m a visually impaired user of Ubuntu 22.04 and Libreoffice Writer. I
use Gnome Magnifier, set to between 6X and 10X magnification. It works
well with Xorg, but not with Wayland. I’ve heard some distros,
including Ubuntu will eventually use only Wayland. That’s a problem for
me, and for other
hello Simon ser i would like to report a bug that i got on wayland all
across the distros on intel first i would be using my desktop normally
and then it stops the window is not responding with the mouse and i
click on win key to overlay in gnome and click on the window than i
could work with it
This is the official release for Wayland 1.23.
Besides numerous bugfixes and protocol clarifications, Wayland 1.23 includes
the following new features:
- A mechanism to set the size of the internal connection buffer used by
libwayland
- An enum-header mode for wayland-scanner to generate
Hi, i would like to make a scratch pad that could work on any wayland
compositor (if its possible, if not, the main compositor will be in charge
i guess).
My requirements are:
- my client need to draw on the screen
- it need to embed any application, like firefox or anythings
- it could work with
Simon Ser (2):
server: document wl_display_add_socket_fd() ownership
build: bump to version 1.22.93 for the RC1 release
Vlad Zahorodnii (1):
server: Clarify fd ownership in wl_client_create()
git tag: 1.22.93
https://gitlab.freedesktop.org/wayland/wayland/-/releases/1.22.93
This is the beta release for Wayland 1.23.
Full commit history below.
Julian Orth (1):
protocol: explicitly describe wl_keyboard state
Simon Ser (1):
build: bump to version 1.22.92 for the beta release
git tag: 1.22.92
https://gitlab.freedesktop.org/wayland/wayland/-/releases
Hi everybody
MGRX is a small 2D graphics C library derived from the GRX library. GRX
was originaly written by Csaba Biegl for DJ Delorie's DOS port of the
GCC compiler.
MGRX supports DOS, Win32, Linux framebuffer, Linux KMS/DRM, Linux X11
and now Linux Wayland.
The Wayland videodriv
On Tue, 30 Apr 2024 17:21:41 -0700 Thiago Macieira said:
> On Monday 29 April 2024 22:23:44 GMT-7 Carsten Haitzler wrote:
> > > There is worry in our community that Wayland is going to take over and x11
> > > will become obsolete.
> >
> > It's inevitabl
ment and
> >> size. It's bearable Wayland does not handle this.
> >
> >YOU should never be handling this. It's like saying "I'm used to having to
> >hand-crank my car's motor for it to start... why can't I keep doing that?".
>
> In kee
On Tuesday 2024-04-30 07:23, Carsten Haitzler wrote:
>>
>> Although gambas provides a Settings.Write(window_name) /
>> Settings.Read(window_name) that saves/restores the window placement and
>> size. It's bearable Wayland does not handle this.
>
>YOU shoul
On Monday 29 April 2024 22:23:44 GMT-7 Carsten Haitzler wrote:
> > There is worry in our community that Wayland is going to take over and x11
> > will become obsolete.
>
> It's inevitable. We're just arguing on timescales (I think Wayland will need
> more time to
On Mon, 29 Apr 2024 22:38:10 +0100 Bruce Steers said:
> On Mon, 29 Apr 2024, 20:53 Thiago Macieira, wrote:
>
> > On Monday 29 April 2024 10:05:32 GMT-7 Bruce Steers wrote:
> > > I guess/hope a similar thing will happen to x11 or Wayland will accept
> > this
&
ngs.Write(window_name) /
> Settings.Read(window_name) that saves/restores the window placement and
> size. It's bearable Wayland does not handle this.
There is a protocol extension in development for saving and restoring
window state:
https://gitlab.freedesktop.org/wayland/wayland-protocol
On 2024-04-29 23:38, Bruce Steers wrote:
>
> There is worry in our community that Wayland is going to take over and x11
> will become obsolete.
There's no need to worry about that. X clients will keep working in a Wayland
session via Xwayland.
--
Earthling
ores the window placement and
> size. It's bearable Wayland does not handle this.
Indeed. I don't see the need for most applications to attempt to remember
their last position. They'll often get it wrong, like opening on the monitor
I'm not looking at (this annoyed me a lot
On Mon, 29 Apr 2024, 20:53 Thiago Macieira, wrote:
> On Monday 29 April 2024 10:05:32 GMT-7 Bruce Steers wrote:
> > I guess/hope a similar thing will happen to x11 or Wayland will accept
> this
> > particular issue needs addressing and provide a workaround.
> >
>
gt; The system tray is not conveyed through Wayland in the first place (it
> goes
> through D-Bus), so any issues you may be facing aren't Wayland. It's
> possible
> the SNI implementation you've got access to is broken and system trays
> work on
> X11 because it fal
On Monday 29 April 2024 10:05:32 GMT-7 Bruce Steers wrote:
> I guess/hope a similar thing will happen to x11 or Wayland will accept this
> particular issue needs addressing and provide a workaround.
>
> As fundamentally Wayland principles are to us, restrictive in a way that I
>
On Monday 29 April 2024 10:17:53 GMT-7 Bruce Steers wrote:
> I thought to redesign my software using a system tray as there was no way
> to position a window but without system tray working I'm stuck for ideas.
The system tray is not conveyed through Wayland in the first place (it goes
say anything about that.
>
> That sounds like the issue is not using the StatusNotifierItem[1]
> specification.
> The old XEmbed system tray protocol is not expected to work on Wayland. I
> don't know if xembedsniproxy works on Wayland, actually. It's running on
> my
> m
;t like
it and wanted what they knew that MATE and cinnamon happened and saved the
day. And they are still very popular today.
I guess/hope a similar thing will happen to x11 or Wayland will accept this
particular issue needs addressing and provide a workaround.
As fundamentally Wayland principles
ork on Wayland. I
don't know if xembedsniproxy works on Wayland, actually. It's running on my
machine but I don't know if anything is using it.
So turning the question back to Bruce: have your applications been updated to
use the SNI protocol? It's over 10 years old now.
[1] h
On Sat, 27 Apr 2024 08:28:00 +0100
Bruce Steers wrote:
> Hello
> I am a gambas basic developer and would like to report some wayland
> problems. (major issues) that we hear of on the gambas mailing list all the
> time.
>
> The attitude towards wayland with gambas coders at p
Hello
I am a gambas basic developer and would like to report some wayland
problems. (major issues) that we hear of on the gambas mailing list all the
time.
The attitude towards wayland with gambas coders at present is ,, ditch
wayland it sucks, use x11.
All gambas users are used to having window
wayland-protocols 1.36 is now available.
This release contains a fix to the xdg dialog protocol, placing the
protocol itself in the `xdg` namespace.
Enjoy!
Jonas Ådahl (1):
build: Bump version to 1.36
Simon Ser (1):
xdg-dialog: fix missing namespace in protocol name
git tag: 1.36
This is the alpha release for Wayland 1.23.
Besides numerous bugfixes and protocol clarifications, Wayland 1.23 includes
the following new features:
- A mechanism to set the size of the internal connection buffer used by
libwayland
- An enum-header mode for wayland-scanner to generate headers
wayland-protocols 1.35 is now available.
This release marks the tablet-v2 protocol as stable, and introduces a
new protocol, alpha-modifier, meant to allow clients to offload
transparency of an otherwise opaque buffer to the compositor.
Other than that, this release also saw a bug fix to the
Hi all,
Here is the release schedule for Wayland 1.23.0:
- Alpha: April 25th (in 2 weeks)
- Beta: May 9th
- RC1: May 23rd
- First potential final release: May 30th
Package maintainers are encouraged to pick up the pre-releases to make
sure packaging can be tested (and fixed) before the stable
On 4/2/24 10:05 PM, Vlad Zahorodnii wrote:
After some break, the governance meeting is back!
The Wayland Governance Meeting is semi-regular meeting to drive
discussion on wayland-protocols forward.
Agenda for the next meeting:
- wp-transactions-v1
Link to the doodle:https
If you need assistance running and configuring GNOME, the right place to
ask questions is https://discourse.gnome.org/.
Jonas
On Fri, Apr 05, 2024 at 12:00:22AM -0700, Shankar Ramamoorthy wrote:
> I'm trying to run Wayland on a headless EC2 instance and sessions die with
> &q
I'm trying to run Wayland on a headless EC2 instance and sessions die with
"No GPUs with outputs found".
I was wondering if perhaps there is an oversight w.r.t. the headless GPU
case.
I tracked down the message to the following code starting @ line 890 in
src/backends/native/meta-
On 4/2/24 10:05 PM, Vlad Zahorodnii wrote:
After some break, the governance meeting is back!
The Wayland Governance Meeting is semi-regular meeting to drive
discussion on wayland-protocols forward.
Agenda for the next meeting:
- wp-transactions-v1
Link to the doodle:https
After some break, the governance meeting is back!
The Wayland Governance Meeting is semi-regular meeting to drive discussion on
wayland-protocols forward.
Agenda for the next meeting:
- wp-transactions-v1
Link to the doodle:https://nuudel.digitalcourage.de/Te23sKeRoVEsKeW5
The final date will
wayland-protocols 1.34 is now available.
This release comes with three new staging protocols:
* xdg-toplevel-drag
This protocol enhances regular drag and drop by allowing attaching a
toplevel window to a drag. This can be used to implement e.g. detachable
toolbars and browser tab drag behavior
Hi,
I am a developer working on a project with XScreensaver and I would really
like to find a way to implement XScreensaver with Wayland enabled. By
default,
I have to disable Wayland in order to run XScreensaver. I maintain the
NetWare SMP based screensaver collection on Linux.
See below for
Thanks. This all seems unfortunate. I think I'll wait until I am forced
to support wayland and then sort it out. At the moment, it's too
difficult.
On Tue, 2024-03-19 at 11:04 +0200, Marius Vlad wrote:
> If the program is a client you won't be find this information, as
> that
t; cover this.
>
> I am the author of a program that in part needs to be able to obtain
> the identity of the active application and window (including its title)
If the program is a client you won't be find this information, as that's
inherent part of the Wayland architecture
bit more to try and gain some
understanding of what is going on and how this should all work.
So I have created a pure GStreamer/Wayland/Weston application to test
out how this should work. This is at:
https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
This tries to implement
supported (X11 and MacOS), but as far as I can see there does not
appear to be a unified approach to achieving this under Wayland.
Is it the case that there is no way to achieve this, or am I just
missing things that are possible? Is it the case that I may need to
only cover a subset of DEs and
On 08/03/2024 15:23, Pekka Paalanen wrote:
On Fri, 8 Mar 2024 14:50:30 +
Terry Barnaby wrote:
On 05/03/2024 12:26, Pekka Paalanen wrote:
On Mon, 4 Mar 2024 17:59:25 +
Terry Barnaby wrote:
...
I would have thought it better/more useful to have a Wayland API call
like
On Fri, 8 Mar 2024 14:50:30 +
Terry Barnaby wrote:
> On 05/03/2024 12:26, Pekka Paalanen wrote:
> > On Mon, 4 Mar 2024 17:59:25 +
> > Terry Barnaby wrote:
> >
...
> >> I would have thought it better/more useful to have a Wayland API call
> &
and gain some
understanding of what is going on and how this should all work.
So I have created a pure GStreamer/Wayland/Weston application
to test
out how this should work. This is at:
https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
This tries to implement a C++ Widget
>> While I am trying to investigate my issue in the QtWayland arena via
> >>>>>> the
> >>>>>> Qt Jira Bug system, I thought I would try taking Qt out of the equation
> >>>>>> to simplify the application a bit more to try a
I'm happy to announce the first publicly available release of The
Compositor Modules, the modular C++ library to easily write a Wayland
compositor. The release is available on GitHub. [1]
You can read the full announcement with more details about the library
exclusively on Phoronix. [2]
The
created a pure GStreamer/Wayland/Weston application to test
out how this should work. This is at:
https://portal.beam.ltd.uk/public//test022-wayland-video-example.tar.gz
This tries to implement a C++ Widget style application using native
Wayland. It is rough and could easily be doing things wrong wrt
plication a bit more to try and gain some
> >>>> understanding of what is going on and how this should all work.
> >>>>
> >>>> So I have created a pure GStreamer/Wayland/Weston application to test
> >>>> out how this should work. T
, I thought I would try taking Qt out of the equation
to simplify the application a bit more to try and gain some
understanding of what is going on and how this should all work.
So I have created a pure GStreamer/Wayland/Weston application to test
out how this should work. This is at:
https
1 - 100 of 2757 matches
Mail list logo
