Re: [PATCH] xdg-shell: add draw states for xdg_surface

To me, 'draw states' sounds a lot like 'mwm hints' - which would be a 180 degree reversal from semantic states back to presentation states. Do we really want to go down that road ? ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https:/

Re: Accessibility considerations

> > Btw. Matthias guessed an implementation would belong in xkbcommon, but > that is also used client-side. How does that fit in with server-side > accessibility implementation? This is where I would really hope for Daniel Stone to chime in... ___ waylan

Re: Accessibility considerations

On Fri, Mar 11, 2016 at 12:51 AM, Timofonic wrote: > Please consider mandatory high contrast option with custom colors. I prefer > black background and green foreground, it's a lie better for Mr eyes because > clear colors really tire me. > > Text-To-Speech and braille devices should be very serio

Accessibility considerations

Hi, I would like to discuss strategies for implementing accessibility features in Wayland that will be needed for a fully featured desktop. There's a whole list of individual items, but for now I'd like to focus on keyboard accessibility features, ie roughly the feature that traditionally labeled

Re: [RFC] Implementing Wayland Security Module

On Mon, Mar 9, 2015 at 1:38 AM, Manuel Bachmann wrote: > Any comments on this ? > I don't think it makes sense to develop a specific solution just for the portion of application sandboxing that happens to overlap with wayland protocol requests. The same questions need to be answered when a third

Re: xdg shell status and gaps

On Thu, Sep 25, 2014 at 4:18 PM, Bill Spitzak wrote: > I agree it would be better to just hide the window. Pointer lock (being > discussed elsewhere) should not be lost when this happens. It sounds like > the loss of grabs is why you lower rather than hide in X. Also if your > client wants to id

Re: xdg shell status and gaps

On Thu, Sep 25, 2014 at 10:32 AM, Jasper St. Pierre wrote: >> Anyway, here's the list: >> >> 1) Marking dialogs as modal (needed so we can implement the 'attached >> modal' visuals of gnome-shell What about this one ? >> 2) Lowering windows (used e.g. by GtkInspector to get out of the way >> w

xdg shell status and gaps

Hi, so yesterday we released what we described as a day-to-day usable GNOME/Wayland. Congratulations to everybody involved in defining xdg-shell on getting us this far. But... (I wouldn't write if there wasn't a but) we are not yet calling it a '100% complete port' because there are still a numbe

Re: [PATCH 0/6] Add weston randr protocol

For comparison, here is the dbus API that gnome-shell is exposing for display configuration under both X and wayland: https://wiki.gnome.org/Initiatives/Wayland/Gaps/DisplayConfig ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://

Re: Inter-client surface embedding

On Mon, Feb 17, 2014 at 6:41 PM, Jasper St. Pierre wrote: > GtkPlug and GtkSocket are really implemented in terms of XEmbed. As we've > found, XEmbed has a surprising number of problems in real-world use cases, > so it's considered deprecated. > > Building something special-case for panels seems m

Re: [Accessibility] Need to be able to register for key events globally

On Tue, Dec 10, 2013 at 3:29 PM, Piñeiro wrote: > GNOME Assistive Technologies need to be able to listen to key events > globally and have the possibility of consuming them. Example use > cases: > > * Orca's presentation of navigation (Events not consumed) > - Right Arrow: Speak character moved

Re: [Accessibility] Need to be able to sythesize mouse events

On Wed, Dec 11, 2013 at 2:15 PM, Piñeiro wrote: > > On 12/11/2013 07:09 PM, Giulio Camuffo wrote: > > Wayland doesn't have a way to inject mouse events currently. Some > > protocol must be written, which would be presumably implemented as a > > private protocol which only trusted clients can use,

Making Wayland accessible

As part of the ongoing GNOME Wayland porting effort, the GNOME accessibility (a11y) team has been looking into what it would take to make our existing a11y tools (ATs) and infrastructure work under Wayland. Most a11y features will probably end up being implemented in the compositor: - input tweak

Re: [RFC] wl_surface scale and crop protocol extension

On Tue, Apr 30, 2013 at 8:33 AM, Pekka Paalanen wrote: > Hi all, > > below is my first draft for a wl_surface scaling and cropping > extension. I called it wl_scaler in the lack of a better name. It is > designed similarly to the other wl_surface extensions wl_shell_surface > and wl_subsurface. >

Re: [PATCH] Add api to obtain min/max keycode

On Sat, Apr 20, 2013 at 4:53 PM, Ran Benita wrote: > (This is easy to miss without some [xkbcommon] in the subject!) > > On Tue, Apr 09, 2013 at 09:57:29PM -0400, matthias.cla...@gmail.com wrote: >> From: Matthias Clasen >> >> Users of libxkbcommon need these

Re: [PATCH] selection: send selection events to all connected clients

On Fri, Apr 12, 2013 at 1:33 PM, Yichao Yu wrote: > A lot of useful features require clipboard access and monitoring > without having a keyboard focus, e.g. clipboard action (klipper[1] and > some download agents), command line access (IPython's %paste magic). > This patch sends out selection even

[PATCH] Add api to obtain min/max keycode

From: Matthias Clasen Users of libxkbcommon need these values to iterate over all keycodes in the keymap. --- src/keymap.c | 12 xkbcommon/xkbcommon.h | 20 2 files changed, 32 insertions(+) diff --git a/src/keymap.c b/src/keymap.c index 55000f4

Re: [PATCH weston] compositor: add a mouse motion binding type

On Thu, Apr 4, 2013 at 3:01 PM, Bill Spitzak wrote: > Kristian Høgsberg wrote: > > I was completely confusing corners of surfaces with corners of outputs, > sorry. He is talking about fixed locations on the screen that are usually > called "hot corners" and other terms. > > I think however that "

Re: [patches] Add a color management framework to weston

On Thu, Apr 4, 2013 at 2:58 AM, John Kåre Alsaker wrote: > I don't see a GLib event loop, so I'm curious to how the signals work. Just ftr (and without actually looking at the patch): glib signals don't need an event loop, they're entirely synchronous. ___

Re: [PATCH 00/21] Documentation improvements

On Mon, Apr 1, 2013 at 10:43 AM, Jason Ekstrand wrote: > Matthias, > First, I would like to apologize for a) being a bit harsh and > overbearing in my comments and b) getting too caught up in stylistic > issues. I really should have read through it for content first and > just kept a tally for st

Re: [PATCH 00/21] Documentation improvements

On Sat, Mar 30, 2013 at 6:32 PM, Jason Ekstrand wrote > > 1. I said this in one of the e-mails, but avoid unneeded > documentation. The documentation as is is fairly sparse and needs to > be filled in. However, too much documentation can sometimes be a bad > thing too. For example, on events c

[PATCH] docs: Add a note about unmapping surfaces without content

From: Matthias Clasen Explanation received on wayland-devel indicates that it is expected compositor behaviour to unmap surfaces without content. --- protocol/wayland.xml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 718a4a5..548b1b9

[PATCH 2/2] docs: Add information about serials and timestamps

From: Matthias Clasen Add some information about serials, timestamps and their uses to the Input section in the protocol overview. --- doc/Wayland/en_US/Protocol.xml | 16 1 file changed, 16 insertions(+) diff --git a/doc/Wayland/en_US/Protocol.xml b/doc/Wayland/en_US

[PATCH 1/2] docs: Document granularity of timestamps

From: Matthias Clasen This information is necessary to make any use of these fields. --- protocol/wayland.xml | 20 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 2a27b1b..718a4a5 100644 --- a/protocol

[PATCH 0/2] More documentation additions

From: Matthias Clasen I've received some clarifications on questions I asked about the protocol. These patches add that information to the docs, so it isn't lost. Matthias Clasen (2): docs: Document granularity of timestamps docs: Add information about serials and timestamps d

Re: [PATCH 21/21] docs: Add details about grabs

You are right, thanks. On Sat, Mar 30, 2013 at 9:16 AM, renoX wrote: > I think that there is a typo in the text, you wrote "But there is way for > clients to take an explicit grab. Instead," instead of "But there is NO > way.." > > BR, > renoX > ___ w

Re: protocol questions

On Sat, Mar 30, 2013 at 7:56 AM, Daniel Stone wrote: > > > >> - Various input events have a time field. The spec doesn't really say >> anything about this. What is it good for, and what units are these - >> monotonic time ? >> > > Monotonic (ideally) time in an undefined domain, i.e. they're only

protocol questions

Here are a few questions/observations I had while studying the protocol docs: - The use of serials in events seems a bit inconsistent. Most wl_pointer events have serials, but axis doesn't. wl_keyboard enter/leave events do. wl_data_offer.enter does, but the corresponding leave/motion events don't

[PATCH 21/21] docs: Add details about grabs

From: Matthias Clasen Mention implicit grabs, (lack of) explicit grabs, and popup windows. --- doc/Wayland/en_US/Protocol.xml | 8 1 file changed, 8 insertions(+) diff --git a/doc/Wayland/en_US/Protocol.xml b/doc/Wayland/en_US/Protocol.xml index a645409..b94e9ca 100644 --- a/doc

[PATCH 20/21] docs: Add details about surfaces

From: Matthias Clasen Mention some of the characteristic differences to X: no global positions, no access to foreign windows. --- doc/Wayland/en_US/Protocol.xml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/Wayland/en_US/Protocol.xml b/doc/Wayland/en_US/Protocol.xml index 58a5962

[PATCH 19/21] docs: Improve wl_region protocol docs

From: Matthias Clasen Just cosmetic changes, a few missing periods, and ID was not capitalized. --- protocol/wayland.xml | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 34a1bbf..2a27b1b 100644 --- a/protocol

[PATCH 18/21] docs: Improve the wl_output protocol docs

From: Matthias Clasen Some descriptions were missing. --- protocol/wayland.xml | 24 ++-- 1 file changed, 18 insertions(+), 6 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index a53cb71..34a1bbf 100644 --- a/protocol/wayland.xml +++ b/protocol

[PATCH 17/21] docs: Improve wl_touch protocol docs

From: Matthias Clasen Some descriptions were missing here. --- protocol/wayland.xml | 36 +++- 1 file changed, 27 insertions(+), 9 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 52bc98f..a53cb71 100644 --- a/protocol/wayland.xml

[PATCH 16/21] docs: Improve wl_keyboard protocol docs

From: Matthias Clasen Some descriptions were missing here. --- protocol/wayland.xml | 25 +++-- 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 87e3d5f..52bc98f 100644 --- a/protocol/wayland.xml +++ b/protocol

[PATCH 15/21] docs: Improve wl_pointer protocol docs

From: Matthias Clasen Some descriptions were missing here. --- protocol/wayland.xml | 43 +-- 1 file changed, 33 insertions(+), 10 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 442862d..87e3d5f 100644 --- a/protocol

[PATCH 14/21] docs: Improve the wl_seat protocol docs

From: Matthias Clasen Expand the main description and tell if requests don't have an effect. --- protocol/wayland.xml | 35 ++- 1 file changed, 22 insertions(+), 13 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 3e674f3..44

[PATCH 13/21] docs: Improve wl_surface protocol docs

From: Matthias Clasen Use NULL consistently. And add some more information in a few places. --- protocol/wayland.xml | 123 +-- 1 file changed, 69 insertions(+), 54 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index

[PATCH 12/21] docs: Improve wl_shell/wl_shell_surface docs

From: Matthias Clasen Add missing summaries, expand descriptions. --- protocol/wayland.xml | 233 --- 1 file changed, 149 insertions(+), 84 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 2417c0e..a3599f0 100644 --- a

[PATCH 11/21] docs: Improve the wl_data_* procol docs

From: Matthias Clasen Add a few missing summaries and descriptions, spell out file descriptor, use hyphens in drag-and-drop, don't use hyphens in 'mime type', and reword a few things. --- protocol/wayland.xml | 95 +++- 1 f

[PATCH 10/21] docs: Improve wl_shm and wl_shm_pool protocol docs

From: Matthias Clasen Reword some paragraphs, and spell out 'file descriptor'. --- protocol/wayland.xml | 73 +++- 1 file changed, 49 insertions(+), 24 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index cc009e

[PATCH 09/21] docs: Improve wl_callback protocol docs

From: Matthias Clasen Add some information about wl_callback and its done event. --- protocol/wayland.xml | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index ad72fd1..cc009eb 100644 --- a/protocol/wayland.xml +++ b

[PATCH 08/21] docs: Improve the wl_registry protocol docs

From: Matthias Clasen Reword a few things, and add some details. --- protocol/wayland.xml | 44 ++-- 1 file changed, 26 insertions(+), 18 deletions(-) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 8587b8f..ad72fd1 100644 --- a/protocol

[PATCH 07/21] docs: Improve wl_display protocol docs

From: Matthias Clasen This adds a bit of information about in-order event delivery, removes extraneous formatting, and adds a missing period. --- protocol/wayland.xml | 17 + 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/protocol/wayland.xml b/protocol

[PATCH 06/21] docs: Consistency fixes

From: Matthias Clasen Say 'object ID' throughout. --- doc/Wayland/en_US/Protocol.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/Wayland/en_US/Protocol.xml b/doc/Wayland/en_US/Protocol.xml index 9bc8232..58a5962 100644 --- a/doc/Wayland/en_US/Protocol

[PATCH 05/21] doc: Improve various sections of the documentation

From: Matthias Clasen --- doc/Wayland/en_US/Protocol.xml | 71 ++ 1 file changed, 31 insertions(+), 40 deletions(-) diff --git a/doc/Wayland/en_US/Protocol.xml b/doc/Wayland/en_US/Protocol.xml index 955b054..9bc8232 100644 --- a/doc/Wayland/en_US

[PATCH 04/21] docs: Improve the 'Connect time' section

From: Matthias Clasen Turn the bullet-point list into complete sentences. --- doc/Wayland/en_US/Protocol.xml | 19 --- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/doc/Wayland/en_US/Protocol.xml b/doc/Wayland/en_US/Protocol.xml index cab68a8..955b054 100644

[PATCH 03/21] docs: Improve the 'Types of Compositors' section

From: Matthias Clasen Turn the bullet-point lists into full paragraphs. --- doc/Wayland/en_US/Compositors.xml | 119 +++--- 1 file changed, 46 insertions(+), 73 deletions(-) diff --git a/doc/Wayland/en_US/Compositors.xml b/doc/Wayland/en_US/Compositors.xml

[PATCH 02/21] docs: Slight rewording

From: Matthias Clasen The Wayland Protocol -> Wayland Protocol Overview, to align better with the subsequent Wayland Protocol Specification. --- doc/Wayland/en_US/Protocol.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/Wayland/en_US/Protocol.xml b/doc/Wayland/en

[PATCH 01/21] docs: Reorder some sections

From: Matthias Clasen Move the 'Types of Compositors' section right after the Overview, and move the 'Client API' part after the protocol spec. --- doc/Wayland/en_US/Wayland.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/Wayland/en_US/Wayla

[PATCH 00/21] Documentation improvements

From: Matthias Clasen Hi, I spent some time going over the documentation, trying to fill gaps in my understanding - and in the documentation. Here are the resulting patches. Matthias Clasen (21): docs: Reorder some sections docs: Slight rewording docs: Improve the 'Types of Compos

[PATCH 2/2] docs: Fix the documentation build

From: Matthias Clasen The publican man page says that the options are actually called --formats and --langs, and with this, the doc build succeeds. --- doc/Wayland/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/Wayland/Makefile.am b/doc/Wayland/Makefile.am

[PATCH 1/2] docs: Add a revision history

From: Matthias Clasen Publican complains if it can't find this file. --- doc/Wayland/Makefile.am| 1 + doc/Wayland/en_US/Revision_History.xml | 7 +++ 2 files changed, 8 insertions(+) create mode 100644 doc/Wayland/en_US/Revision_History.xml diff --git a/doc/Wa

[PATCH 0/2] Fix the documentation build

From: Matthias Clasen Trying to write some review comments on the Wayland docs, I found that the docs wouldn't build here, with publican 3.1.5. These two patches make things work for me. Matthias Clasen (2): docs: Add a revision history docs: Fix the documentation build doc/Wa

Re: I feel configure events and requests are messed up

On Thu, 2011-09-08 at 22:35 +0200, Giovanni Campagna wrote: > > Probably I forgot to mention, but at the Desktop Summit it was agreed > that client-side decorations won't happen, neither in KWin nor Mutter, > so the client does not need to worry about what edges it should draw. I think it is tim