and single pixel buffer
protocol.
Caitlyn Stewart (1):
single-pixel-buffer-v1: clarify create_u32_rgba_buffer
Jonas Ådahl (3):
build: Add 'experimental' protocols
experimental: Add xx-session-management-v1
build: Bump version to 1.45
Kirill Primak (1):
ext
le. 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 up in a release. This
is different from wayland-protocols, since they don't end up causing any
actual changes on people's system until servers and clients make use of
and ship them.
Jonas
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
he load. This
> is also what I've been doing for Sway and wlroots for a very long time.
>
> Would this make sense? Are there other reasons why alphas/betas were
> valuable?
Personally I think only RCs are enough for what kind of changes tend to
go into the wayland repo these days.
Jonas
>
> Thanks,
>
> Simon
wlr-virtual-pointer-unstable-v1 and
https://wayland.app/protocols/virtual-keyboard-unstable-v1.
Jonas
>
> I'm looking forward to your responses.
>
> Sincerely,
> Zarif Atai
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
constrained, e.g. whether they can resize or not.
For a complete log, including bug fixes, see the short log below.
Jonas Ådahl (2):
xdg-shell: Add edge constraints
build: Bump version to 1.43
Simon Ser (1):
color-management-v1: fix typo in feature.windows_scrgb
Xaver Hugl (2
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
High Dynamic Range (HDR) content.
Jonas Ådahl (1):
build: Bump version to 1.41
Pekka Paalanen (1):
staging/color-management: credit Niels
Sebastian Wick (1):
staging: add color-management protocol
git tag: 1.41
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases
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
-idle-notify: Allow for the ignoring of idle inhibitors
Jonas Ådahl (1):
build: Bump version to 1.40
Simon Ser (1):
linux-dmabuf: link to kernel docs
Xaver Hugl (1):
stable/linux-dmabuf: clarify when the plane_set protocol error is sent
YaoBing Xiao (2):
alpha-modifier
ember'
governance: Specify how to change points of contact
governance: Deprecate wayland-devel@
Heiko Becker (1):
build: Raise required wayland-scanner version to 1.23.0 for tests
Jonas Ådahl (1):
build: Bump version to 1.39
Mike Blumenkrantz (3):
add experimental protocols
ub.com/flatpak/xdg-desktop-portal/pull/1539 for it.
Adding a Wayland protocol would scatter appearance settings into
multiple places, which isn't ideal.
Jonas
>
>
> Proposal
>
>
> It would be useful if there was a protocol for accessing the theme/size.
> Wit
pinging protocol authors on changes
presentation-time: Specify refresh bounds for VRR
Derek Foreman (2):
fifo-v1: Add new protocol
commit-timing-v1: Add new protocol
Jonas Ådahl (4):
members: Update weston point-of-contact
members: Add mesa as a member
Add
From: Jonas Ådahl
In order for compositors to utilize real time scheduling capabilities,
it must be ensured by the kernel that calling a drmModeAtomicCommit()
with DRM_MODE_ATOMIC_NONBLOCK does not block in a manner that makes the
realtime scheduler watchdog send a SIGKILL to the calling process
):
various: Fix definition of double-buffered state
Jonas Ådahl (1):
build: Bump version to 1.37
Matthias Klumpp (1):
staging: Add xdg-toplevel-icon protocol for dedicated toplevel icons
Nicolas Fella (1):
tablet-v2: Fix feedback description in mode_switch
PolyMeilex (1
Hi,
This sounds like a problem with the magnifier feature of GNOME Shell.
Please file an issue at
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ .
Jonas
On Tue, Jun 18, 2024 at 12:41:55PM -0700, Jim Greene wrote:
> I’m a visually impaired user of Ubuntu 22.04 and Libreoffice Writer
gh agenda for a topic. It'll put
an organizational burden on one or more person, but I imagine so is the
case for meetings at an interval, but will require less commitment up
front from the community at large.
Jonas
>
> [1]
> https://gitlab.freedesktop.org/wayland/wayland-p
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
cursor shape
documentation, fixing a missed enum attribute to xdg-shell.
The xdg-shell protocol now also explicitly recommends against drawing
decorations outside of the window geometry when tiled.
Enjoy!
Jonas Ådahl (1):
build: Bump version to 1.35
Sebastian Wick (2):
cursor-shape-v1
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
):
staging/dialog: Add "dialog" protocol
David Redondo (1):
Add xdg-toplevel-drag protocol
Jonas Ådahl (1):
build: Bump version to 1.34
Poly (1):
Fix typo in ext-foreign-toplevel-list-v1
Simon Ser (3):
tablet-v2: clarify that name/id events are optional
as logic to allow it to be positioned within e.g the work
area, using xdg_positioner rules.
I suggest allowing repositioning your popups only when the compositor
support it, and in other, unmap it and map a new one at a new position,
if you need to.
Jonas
The portal APIs rely on libei[3]
for input event transmission - the portals are there to negotiate
consent and to set up sessions.
It should be possible to use input-leap with mouse/keyboard sharing with
all the building blocks manually compiled, but nothing has shipped in
distributions yet.
J
reund (3):
ext-session-lock-v1: use RFC 2119 key words
ext-session-lock-v1: clarify to fix race
ext-session-lock-v1: relicense to MIT
Jonas Ådahl (4):
xdg-output: Remove and tweak contradicting examples
xdg-shell: Clarify that geometry doesn't automatically change
uses a bunch of AMD_* properties, it'd look more like the
example Simon had in the initial RFC.
Jonas
>
> There is so much stuff to do with color, that I don't think a
> prescriptive API in the kernel could ever keep up with the things that
> we want to be pushing from Ga
lly will only be exposed by out of tree drivers
will be acceptable upstream, at least as documented operations.
Jonas
>
> This feels like we are trying to go down the Android HWC road, but we
> aren't in that business.
>
> My thoughts would be userspace has to have some way to describe what
> it wants anyways, otherwise it does sound like I need to update
> mutter, kwin, surfaceflinger, chromeos, gamescope, every time a new HW
> device comes out that operates slightly different to previously
> generations. This isn't the kernel doing hw abstraction at all, it's
> the kernel just opting out of designing interfaces and it isn't
> something I'm sold on.
It is true that for a new generation of hardware that changes the color
pipeline in a way that makes existing userspace no longer able to
off-load compositing, needs an updated userspace, but the grand long
term idea is that one wouldn't update all those compositors, but only
the shared library that provides the descriptive API they all (ideally)
make use of. The compositors still handle interacting with KMS
themselves, but would share this helper library that can help
configuring a subset of the knobs KMS provide to their individual needs.
So indeed the kernel isn't doing all the abstraction, it'd be the kernel
together with a userspace library.
Jonas
>
> Dave.
>
positioned against, given all the
rules set up using the xdg_positioner interface.
It could for example be the rectangle corresponding to the hamburger
menu button where the popup opening above or below (in y-coordinates).
The gtk4 docs for GdkPopupLayout has some illustrations that might help:
https://docs.gtk.org/gdk4/struct.PopupLayout.html
Jonas
>
>
> Thanks,
> pq
t here:
https://gitlab.freedesktop.org/libinput/libinput.
Jonas
>
> On Fri, Mar 3, 2023 at 10:29 AM Roemer Claasen
> wrote:
>
> > Hi all,
> >
> > I would like your opinion about the following: thumb detection on the
> > upper side of the touchpad.
> &g
about protocol ACKs requirements was also done.
Enjoy!
Jonas Ådahl (2):
Add Victoria as Smithay/cosmic-comp member
build: Bump version to 1.31
Kenny Levinsen (1):
wp-fractional-scale-v1: new protocol
Kirill Primak (1):
xdg-shell: add defunct_role_object error
Simon Ser
or details.
Jonas Ådahl (1):
build: Bump version to 1.30
Xaver Hugl (1):
staging: add tearing control protocol
git tag: 1.30
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/1.30/downloads/wayland-protocols-1.30.tar
ension saw documentation fixes.
Enjoy!
[1] https://gitlab.freedesktop.org/wayland/wayland/-/issues/336
Jonas Ådahl (1):
build: Bump version to 1.29
Manuel Stoeckl (1):
linux-dmabuf: fix references to tranche_formats
i509VCB (1):
content-type: fix enum name in wp_conte
Add xdg-shell.unresponsive error
Jonas Ådahl (1):
build: Bump version to 1.28
Joshua Ashton (1):
xwayland_shell_v1: New protocol
git tag: 1.28
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/1.28/downloads/wayland-protocols-1.28.tar.xz
SHA256
Peyrot (1):
staging/content-type: Content type hint support
Isaac Freund (1):
ext-session-lock: add note on client termination
Jonas Ådahl (1):
build: Bump version to 1.27
Simon Ser (3):
xdg-shell: forbid loops in set_parent
ext-idle-notify: new protocol
build
e remote desktop XDG desktop portal
(https://github.com/flatpak/xdg-desktop-portal/pull/762).
The other approach focuses is as far as I know for the receiving end of
the problem, and uses various wlroots Wayland protocols for injecting
input events (https://github.com/r-c-f/waynergy). I'm sure others are
more aware of the details, and whether it aims to solve the input
capture side of this as well.
Jonas
>
> Thanks.
>
> Regards,
> Jesse
use cases is there a need to pass this functionality via virtual
mode setting to implement virtual monitors in display servers, for
headless and virtualization?
I realize that there is a use case for virtual mode setting outputs for
virtual machines meant to e.g. test run distributions while imitating real
hardware as close as possible, but for actual intended remote access to
headless machines or virtual machines, compositors can just render to
offscreen framebuffers and communicate in whatever way, e.g. using DMA
buffers via some IPC, with the software solution intended to provide the
actual access.
Jonas
e done this
by mocking a subset of the libdrm API, which I could use to test e.g.
failed commits handling:
https://gitlab.gnome.org/jadahl/mutter/-/commit/93995754484536c61c7ddeffa2e50e4aef092a78
Jonas
>
> Thanks for taking this on! Really looking forward to it.
>
> Cheers,
> Daniel
):
text-input: Reword the interpretation of serials to be more specific
Daniel Stone (1):
xdg-shell: Delete duplicate paragraph in xdg_popup
Jonas Ådahl (1):
build: Bump version to 1.26
Kenny Levinsen (1):
viewport: Remove mention of wl_surface.attach x/y
Kirill Primak (1
would not need to patch userspace? But
> now we need to patch userspace anyway, so why bother with KMS and its
> design limitations that are well appropriate for hardware drivers but
> not for virtual drivers? If you had your own winsys virtualization
> protocol, you could do so much more than
Freund (2):
ext-session-lock-v1: new protocol
xdg-shell: add invalid_resize_edge error value
Jonas Ådahl (2):
xdg-shell: Add toplevel "bounds" configure event
build: Bump version to 1.25
Max Ihlenfeldt (1):
xdg-shell: clarify conditions for remapping unmapped
) drawn by the
compositor, e.g. done by kwin or gnome-shell. This menu is shown by the
client issuing the "show_window_menu" request on the xdg_toplevel
object.
Jonas
ing able to
reuse all the sandbox permission management, portal dialog
implementations, and related things that this involves.
Jonas
On Mon, Dec 06, 2021 at 11:19:06AM +, Jesse Van Gavere wrote:
> We're not using a device driver, it's a very small application that uses
> XInput2
summary
Fabrice Fontaine (1):
meson.build: wayland-scanner is only needed for tests
Jonas Ådahl (1):
build: Bump version to 1.24
Simon Ser (4):
Drop autotools
linux-dmabuf: add note about pre-multiplied alpha
unstable/linux-dmabuf: add wp_linux_dmabuf_feedback
e:
>
> xdg-shell-client-protocol.h
>
> But I can't find it. What should I do to make it appear?
It's generated from 'xdg-shell.xml'[0] using 'wayland-scanner'.
wayland-scanner is part of the wayland repository, and can be found via
your distributio
wayland-protocols 1.23 is now available.
This release adds the new gesture "hold" to the pointer gesture protocol.
David Edmundson (1):
Set Vlad Zahorodnii as kwin maintainer
Jonas Ådahl (1):
build: Bump version to 1.23
Peter Hutterer (1):
pointer-gestures: add hol
-shell: Make xdg_surface fail when surface has role
tests: Include libwayland cflags/ldflags
Issam E. Maghni (1):
tests: use dynamic python path
Jonas Ådahl (1):
build: Bump version to 1.22
Manuel Stoeckl (1):
xdg-output: fix minor calculation error
Roman Gilg (4
On Wed, Jul 28, 2021 at 01:36:54PM +, Alyssa Ross wrote:
> Jonas Ådahl writes:
>
> > On Wed, Jul 28, 2021 at 11:06:43AM +, Alyssa Ross wrote:
> >> Daniel Stone writes:
> >>
> >> >> One big issue for us is protecting the system against
there.
wl-clipboard relies on this not being done good enough, and will
eventally stop working, unless there exist some global state like
clipboard manager protocol that bypasses any content restrictions that
wl_data_device and friends apply.
Jonas
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
io, 27/05/2021 alle 08.23 +0200, Jonas Ådahl ha scritto:
> > [...]
> > * Introduce "virtual" monitor screen recording to
> > org.freedestop.portal.ScreenCast
> > (https://github.com/flatpak/xdg-desktop-portal) and the portal
> > backend relevant
the second two steps with some VNC/RDP thing,
but that will not work for many types of devices where Miracast do.
Jonas
>
> Thank you - for your answers, and for this great piece of software.
>
> Pietro Battiston
>
>
> ¹
> https://superuser.com/questions/1434779/using-
lude a new xdg_activation protocol
Bhushan Shah (1):
text-input: document behavior regarding multiple text-inputs
Carlos Garnacho (1):
staging/xdg-activation: Describe interoperation with X11
Jonas Ådahl (11):
README.md: Add some merge request triaging conventions
Add m
On Fri, Apr 30, 2021 at 10:31:03AM +0300, Pekka Paalanen wrote:
> On Fri, 30 Apr 2021 09:11:18 +0200
> Jonas Ådahl wrote:
>
> > On Fri, Apr 30, 2021 at 11:53:16AM +0800, kai.x...@thundercomm.com wrote:
> > > Hello wayland community，
> > >
> > &
at fork as a new remote to
your locally cloned checkout, and push your changes to some branch
there, and create a merge request using that branch.
See
https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html
and
https://docs.gitlab.com/ee/user/project/merge_requ
actual movement of the
pointer cursor sprite, i.e. even if the pointer hit an edge or doesn't
move, you'll still receive the motions as sent from the device.
I think most compositors support these two protocol extensions as they
are a corner stone in how e.g. 3D FPS games work.
Jonas
n'.
> >
> > I propose that we do this for all the wayland/* repositories, either this
> > weekend or next; I'm happy to make the changes (rename 'master' to 'main'
> > and retarget all ope
n C++, C
or whatever, as long as there is a C API to use.
Jonas
>
> Simon
> ___
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel
___
On Mon, Feb 22, 2021 at 01:56:46PM +0200, Pekka Paalanen wrote:
> On Mon, 22 Feb 2021 12:10:08 +0100
> Jonas Ådahl wrote:
>
> > On Mon, Feb 22, 2021 at 10:49:33AM +, Simon Ser wrote:
>
> > > I'd like to avoid making this general, if we go down this road. Mak
On Mon, Feb 22, 2021 at 11:21:04AM +, Simon Ser wrote:
> On Monday, February 22nd, 2021 at 12:10 PM, Jonas Ådahl
> wrote:
>
> > Sounds potentially not horrible in theory, but is it remotely possible?
> > There are these approaches I can think of:
> >
> &g
x27;t call a
reasonable option either.
So, how would we make it not de-facto general?
Not to meantion the head ache of letting clients in on configuring their
window positions when any kind of HiDPI scaling, fractional or nat, is
done.
>
> Notifications popups are part of the desktop enviro
ification, and thus a bug
in gtk.
I suggest opening a bug in the gtk issue tracker:
https://gitlab.gnome.org/GNOME/gtk/issues/new
Jonas
> ___
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
ocess, not involving Wayland. For example if your parent
window receives all input events, and the subsurfaces none, the
framework managing the main surface needs to pass some internal input
event representation to the owner of the subsurface using some API
understo
uld certainly help getting the protocol merged.
weston, mutter and gtk implementations are linked to from this comment:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/26#note_554405
Jonas
> ___
> wayland-devel mailing list
&
ess [2]
> tags [3]
>
> [1] /tmp, host, xdg-config/GIMP, xdg-config/gtk-3.0, xdg-run/gvfs
> [2] org.freedesktop.FileManager1, org.gtk.vfs, org.gtk.vfs.*
> [3] stable
>
> ...
>
> Proceed with these changes to the user installation? [Y/n]:
>
>
&g
tion that isn't running inside a sandbox. Thus, if a
Ei session policy default is to ask, for a portal to be able to remember
the permission for an unsandboxed application, we would have to add a
way for the portal to blindly trust some ID or key of some sort the
application provides.
Xwayla
to open a channel comes from without having to
trust the application to tell the truth, and provide user facing ways
for potentially limiting access. In other words, it'd be blocked before
ever reaching the display server would so be needed. What this proposal
aims is t
ut being
able to be drm master? We still need API to manage the pipewire streams
(add/remove/change virtual outputs, inject input, i.e. something like
org.gnome.Mutter.RemoteDesktop/ScreenCast); would adding a new session
type bring us anything useful? We wouldn't just implicitly spit out a
pip
On Wed, Apr 08, 2020 at 11:17:14AM -0700, Erik Jensen wrote:
> On Wed, Apr 8, 2020 at 2:02 AM Jonas Ådahl wrote:
> > Either multiple separate units (e.g. GDM and Chrome Remote Desktop login
> > manager) needs to both try to manage the same sessions via logind, which
> &g
ue to access KMS directly,
and that there will be no system compositor that acts as a proxy for
session compositors.
Lets also assume we have a way to get the pixel content from the compositor
into the remote desktop service and input back into the compositor (e.g.
via PipeWire, etc.), the complex issues
ut going over the socket (and
> > > > round-tripping through the kernel). However, the only thing that
> > > > fence does is order the OpenGL API calls in the client and server and
> > > > the real synchronization is still implicit.
> > > > - linux/i915/gem:
wayland-protocols 1.20 is now available.
This release is a brown paper bag release adding the missing README.md,
GOVERNANCE.md and MEMBERS.md files to the tarball. Distributions that
distribute one or more of these files should ignore the 1.19 release and move
directly to 1.20.
Jonas Ådahl (2
and bitfield attributes will generate better
result.
Ivan Molodetskikh (2):
presentation-time: add missing bitfield marker
xdg-shell: add missing enum attribute to resize
Johan Klokkhammer Helsing (1):
Update point-of-contact for Qt
Jonas Ådahl (4):
xdg-shell: Remove left
; >
> > Thanks,
> > pq
>
> Hi,
>
> seeing the answers so far, I think starting a new branch is a good idea. In
> case there are major changes, a new major version could be created out of the
> new branch anyway.
>
> Currently, there's only one ch
e actual one.
Thus, I think using a branch until the new version is settled is the
best option here. You could still use merge requests, just that you
target a 'wip/text-input-v3.2' branch we create instead of the master
branch.
Jonas
>
> Mind
ts should handle this case
>
> I think there's a strong argument for either. What are others doing?
The answer is b). See the specification for wl_output::geometry:
The physical size can be set to zero if it doesn't make sense for this
out
On Wed, Jan 08, 2020 at 10:11:40AM +, Alan Griffiths wrote:
> On 08/01/2020 10:01, Jonas Ådahl wrote:
> > This idea has more or less been abandoned however, so I'd say it's more
> > likely we can "archive" it rather than marking it as stable, as there
> &
mode, for example only allow one client, with only a single toplevel,
that is always configured as fullscreen.
Jonas
>
> Thanks,
> Alan
>
> ___
> wayland-devel mailing list
> wayland-devel@lists.freedesktop.org
> https://lists
s outside the window geometry by making it maximized. You should be
able to accomplish this by calling
weston_desktop_surface_set_maximized() with true on the corresponding
desktop surface instance.
Jonas
>
>
> On Thu, Nov 21, 2019 at 5:52 PM Scott Anderson
> wrote:
> >
>
t; Signed-off-by: Simon Ser
> Acked-by: Daniel Stone
> Acked-by: Pekka Paalanen
> Acked-by: Johan Helsing
> Acked-by: Roman Gilg
> Cc: Mike Blumenkrantz
> Cc: Jonas Ådahl
> Cc: Carlos Garnacho
> Cc: David Edmundson
> Cc: Christopher James Halse Rogers
> Cc: Alan
?
>
> I would suggest that we push the patch with the following initial
> member projects and their points of contact defined, and finally
> enable MRs:
> * EFL/Enlightenment: Mike Blumenkrantz @zmike
> * GTK/Mutter: Jonas Ådahl @jadahl
I'd like to add Carlos Garnacho @ga
land is a few years old by now and developers should have
> > learnt better, so maybe that fear is no longer relevant.
>
> I share this fear as well. IMHO `ps` is good enough. You could
> also use something like `lsof /dev/dri/card0` to get the DRM
> master.
There is also $XDG_
ce for the new position to
take effect. The reason for this is that the position of the surface is
more of a state of the parent surface rather than the subsurface itself,
and it is likely that if you move the subsurface, something on the
parent surface needs to be updated at the same time in order
position
changes.
Signed-off-by: Jonas Ådahl
Reviewed-by: Mike Blumenkrantz
---
Changes since v1:
- Renamed move to reposition, and moved to repositioned, to not be
confused with xdg_toplevel.move. (David)
- Added invalid_popup error sent sync_with_popup() is passed
an invalid popup
figure(3)
> <-- xdg_popup_surface.ack_configure(3)
> <-- xdg_popup_surface.sync_with_popup(xdg_popup)
>
> Should this be xdg_toplevel_surface?
Yes, indeed. Well spotted.
Jonas
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
On Sat, Sep 21, 2019 at 11:57:45PM -0400, Drew DeVault wrote:
> On Thu Sep 19, 2019 at 9:02 PM Jonas Ådahl wrote:
> > I think that if there is a consensus that it's within the correct scope
> > and no-one nacks it, there shouldn't need be any artifical bureaucratic
&
On Thu, Sep 19, 2019 at 02:10:24PM -0400, Drew DeVault wrote:
> On Tue Sep 17, 2019 at 7:53 PM Jonas Ådahl wrote:
> > I think both for stable and unstable the same limitation can be
> > as problematic. A protocol that fits in xdg/wp may still only be
> > relevant for a
On Tue, Sep 17, 2019 at 05:46:49PM +, Simon Ser wrote:
> On Friday, September 6, 2019 10:45 AM, Jonas Ådahl wrote:
>
> > > 2.2. Protocol inclusion requirements
> > >
> > >
> > > a. All protocols found in the "xdg&quo
is to make the _manager object an actual manager object
that has 'added' and 'removed' events with the "_device" containing the
actual lease request.
Jonas
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
On Thu, Sep 05, 2019 at 09:34:59PM +, Simon Ser wrote:
> This is v3 of the proposal.
>
> Changes from v2 to v3:
> - Use Jonas' definition of the "xdg" namespace (Jonas)
> - Amendments to existing protocols require no minimum discussion period
> (Jonas)
;s reasonable to avoid using any new XML format features
to protocols that was initially introduced early than those features; it
should be required that scanners handle unknown attributes by ignoring
them, just as wayland-scanner does when not passing --strict.
Jonas
>
> The co
configure event. This is necessary to, for example,
properly constrain a popup given a yet-to-be-applied parent state. An
example of when this may be necessary is an interactive resize where
both the toplevel position and the relative popup position changes.
Signed-off-by: Jonas Ådahl
Reviewed-by
case to change the app ID at runtime
Jonas Ådahl (2):
xdg-shell/README: Update E-mail address
configure.ac: Bump version to 1.18
Sebastian Krzyszkowiak (1):
xdg-shell: fix a typo
Simon Ser (3):
xdg-output: deprecate the xdg_output.done event
pointer-gestures: add a
pertes of a surface
> > depending on the app ID, like the window icon specified in the
> > desktop file or a re-grouping of the surfaces in a task manager.
>
> Signed-off-by: Jan-Marek Glogowski
Thanks, this has now landed.
Jonas
> ___
thub.com/swaywm/wlroots/issues/1623
>
> Signed-off-by: Simon Ser
Now pushed with my Reviewed-by and Oliviers Acked-by.
Jonas
> ---
>
> The version isn't bumped because this has already been done in the previous
> patch.
>
> Changes in v2: rebased on top of HEAD
>
hub.com/swaywm/wlroots/issues/1623
>
> Signed-off-by: Simon Ser
Thanks for the rebase.
Reviewed-by: Jonas Ådahl
Jonas
> ---
>
> The version isn't bumped because this has already been done in the previous
> patch.
>
> Changes in v2: rebased on top of HEAD
>
ing of the surfaces in a task manager.
Just noted this is missing Signed-off-by. Mind if I help you add it?
Jonas
> ---
> stable/xdg-shell/xdg-shell.xml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/stable/xdg-shell/xdg-shell.xml b/stable/xdg-shell/xdg-shell.xml
>
estroys the
> client-side object without sending any request).
>
> Signed-off-by: Simon Ser
> Reviewed-by: Jonas Ådahl
Just saw this one never landed; but taken care of now!
Jonas
> ---
>
> Changes from v2 to v3: added a version separator
>
> .../pointer-gestures-
ng of the surfaces in a task manager.
Reviewed-by: Jonas Ådahl
Jonas
> ---
> stable/xdg-shell/xdg-shell.xml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/stable/xdg-shell/xdg-shell.xml b/stable/xdg-shell/xdg-shell.xml
> index 2e420c6..3a87a9e 100644
> ---
n it's necessary to
> add
> e.g. the connector type to tell them apart ("Dell U2717D on HDMI"). See [1]
> for
> a discussion about this.
>
> This commit bumps xdg_output's version to allow compositors to update the
> property.
Seems fine to me. Want to r
s to atomically apply the xdg_output
> state.
>
> For this reason, I think bumping the version is a better approach.
>
> This commit also deprecates xdg_output.done, which doesn't have any purpose
> anymore.
>
> [1]: https://lists.x.org/archives/xorg-devel/2019-Ap
correct grouping "hint".
I think it's fine to mention that it may change, and elaborate more
verbosely in the commit message about the LibreOffice use case, but I
don't think it should mention anything about icons, grouping and what
not since, as Simon said, that is compositor p
1 - 100 of 1597 matches
Mail list logo
