[RFC] Screensaver/blanking inhibition

[Pekka Paalanen]

On Thu, 19 Nov 2015 05:09:09 -0500
Christopher Michael <cpmichael at osg.samsung.com> wrote:

> On 11/19/2015 05:04 AM, Bryce Harrington wrote:
> > On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher Michael wrote:
> >> Just some random thoughts inlined below...
> >>
> >> On 11/19/2015 03:05 AM, Bryce Harrington wrote:
> >>> A "screensaver inhibition protocol" is on the set of needed enhancements
> >>> for Wayland.  This should turn off screen blanking and any running
> >>> screensaver for a period, then re-enabling it later.

> >>> a.  Which protocol file should this stuff be added to?  Weston's
> >>>      desktop-shell.xml (soon to be renamed weston-desktop-shell.xml) has
> >>>      a screensaver interface, but that is only weston-specific, yet we
> >>>      want this functionality to work on multiple compositor
> >>>      implementations.
> >>>
> >>
> >> xdg-screensaver.xml maybe ??
> >
> > Ah, I was thinking the requests should be added to one of the existing
> > protocol files, but hadn't thought maybe it should go into its own xml
> > file.  Hmm...
> >
> 
> Well, having it inside it's own xml/protocol file would allow easier 
> adoption (IMO) as you (read: implementors) do not have to go back and 
> modify "existing" code (read: potentially large files) to support it. 
> Also, those that do not wish to support it (or they cook up their own), 
> can safely ignore it. Storing it in an existing protocol file 
> potentially means that they cannot avoid it (thinking protocol version 
> number gets bumped, other unrelated things in that protocol file get 
> changed, etc, etc)...

Making a new file is good, yes.

I just want to point out, that even if you added it in an existing file,
it would not imply anything to implementations, as long as the
foundation of the new interface hierarchy is a new global interface.
Global interfaces can be implemented or not implemented independently
in general, because they are advertised to clients separately. Whether
it is in a same or different xml file has little consequence.

There are other reasons to favour a separate XML file, and one of them
is the wayland-protocols development model for unstable protocols.


Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20151120/98a80221/attachment-0001.sig>