[PATCHv3] Add name event to xdg-output

[Jonas Ådahl]

On Fri, Apr 13, 2018 at 10:05:39AM -0400, Drew DeVault wrote:
> On 2018-04-13  4:02 PM, Jonas Ådahl wrote:
> > > - A client using fullscreen-shell could offer the user a list of outputs
> > >   by name to fullscreen on
> > 
> > I think this would need something different, an actual "human friendly"
> > name, like 'Dell 24"' or 'Builtin monitor'. If you'd have strings like
> > "DP-1", they are hardly helpful for selecting where to fullscreen.
> 
> In sway, we have a slightly more savvy base user than the general
> population, and we've educated them to understand connectors. However,
> this is exactly why the field is vague - other compositors can name them
> anything they like, including "Dell 24".

If that is the case, I'd rather we introduced data that has actual
meaning, like something similar to "connector" (even though connector is
the wrong thing here since an "xdg_output" might not have one, maybe,
something that doesn't identify the monitor itself, but how it is
connected, if that is what you want) and then a different thing that is
more meaningful to a user interface. Then whether the "this is string is
user interface facing" should have anything to do with where the wire is
plugged in or what is actually plugged in can be up to the software that
is responsible for generating that string, but it should be clear what
its purpose is.

> 
> > > - Xwayland can name the X11 outputs based on their genuine names rather
> > >   than assigning e.g. XWAYLAND0
> > 
> > If the protocol is loosly specified as in it's not known what format
> > you'll get, I don't think Xwayland can make any use of this.
> 
> Can you elaborate on what expectations Xwayland would have? I am open to
> restricting the format a bit, e.g. to ASCII characters or so.

If we'd add quotation marks, spaces etc I'm sure many things would break
here and there. If we start adding such restrictions, it'd hardly be
suitable as a "human readable" kind of thing.


Jonas

> 
> --
> Drew DeVault