[PATCH wayland-protocols v3] protocol: add compositor-debug.xml

[Pekka Paalanen]

On Wed, 4 Oct 2017 17:19:56 +0300
Pekka Paalanen <ppaalanen at gmail.com> wrote:

> On Wed, 4 Oct 2017 10:07:30 -0400
> Jonas Ådahl <jadahl at gmail.com> wrote:
> 
> > On Tue, Oct 03, 2017 at 11:45:41AM +0300, Pekka Paalanen wrote:  
> > > On Fri, 22 Sep 2017 11:17:49 +0200
> > > Maniraj Devadoss <external.mdevadoss at de.adit-jv.com> wrote:
> > >     
> > > > From: Pekka Paalanen <pq at iki.fi>
> > > > 
> > > > This is a new debugging extension for non-production environments. The
> > > > aim is to replace all build-time choosable debug prints in the
> > > > compositor with runtime subscribable debug streams.
> > > > 
> > > > Signed-off-by: Pekka Paalanen <pq at iki.fi>
> > > > Signed-off-by: Maniraj Devadoss <external.mdevadoss at de.adit-jv.com>
> > > > ---
> > > >  Makefile.am                                        |   1 +
> > > >  unstable/compositor-debug/README                   |   7 ++
> > > >  .../compositor-debug-unstable-v1.xml               | 128 +++++++++++++++++++++
> > > >  3 files changed, 136 insertions(+)
> > > >  create mode 100644 unstable/compositor-debug/README
> > > >  create mode 100644 unstable/compositor-debug/compositor-debug-unstable-v1.xml

> > For me this is out of scope for wayland-protocols. The idea behind
> > wayland-protocols is to have a place for protocols that can/should be
> > used between any compositor and "normal" client. So far (and my opinion
> > is that it will continue to be so) this has meant that things like debug
> > protocols (like the infamous "wl_randr" protocol) and desktop
> > environment components (like a generic "panel" protocol) have been out
> > of scope.
> > 
> > They may not be out of scope for Wayland as a whole (for example
> > wayland-wall tries to fill the hole regarding DE environment
> > components). I discussed this with Pekka on IRC, and for this particular
> > protocol, I think it makes more sense to keep it a weston extension.
> > Weston can however install the XML file and third party clients and
> > compositors can depend on it in any way they want.
> >   
> 
> Thank you Jonas, I perfectly understand that point of view.
> 
> Maniraj, we need to go back to the weston-specific naming for both
> interfaces and the XML file name. You could arrange libweston to
> install the XML file under $datadir/weston/protocols/. We also need a
> way to get the path from pkg-config. I would have just added a variable
> to libweston-$MAJOR.pc but I'm not sure that's good for
> arch-independent data. That would allow external projects to use the
> protocol extension.

Hi Maniraj,

I realized that while prefixing into the weston namespace again, we
should probably keep the _v1 suffix according to the wayland-protocols
rules so that we can make a new incompatible revision as needed. But I
think it's not necessary to have the word "unstable" in the names.


Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20171005/180b1b6a/attachment-0001.sig>