[Trac #1429] Screen saver needs implementation...

[Zarro Boogs per Child]

#1429: Screen saver needs implementation...
------------------------------+---------------------------------------------
  Reporter:  jg               |       Owner:  JordanCrouse
      Type:  defect           |      Status:  assigned    
  Priority:  high             |   Milestone:  BTest-4     
 Component:  x window system  |     Version:              
Resolution:                   |    Keywords:  power       
  Verified:  0                |  
------------------------------+---------------------------------------------
Changes (by JordanCrouse):

  * verified:  => 0

Comment:

 On second thought - I'm not sure this is the right course of action.  The
 screensaver and DPMS interfaces are designed to support a myriad of
 monitors and devices through a common interface, so you could take, say,
 your handy-dandy Xscreensaver and control virtually anything with it.

 Obivously, due to our unique power policy, we're not going to be able to
 just stick on a generic screensaver and be happy with that.  There will be
 entire periods of time when the screen will have to stay on (in e-book
 mode, for example), and there will be other times when we will want the
 screen immediately put to sleep and still other times when we want the
 screen to go off after a while.  There will be a third party entity (third
 party in that it is separate from X and the kernel) that will be making
 these decisions.  Obviously, we could just have that entity call the DPMS
 extensions to control the monitor through X if we wanted to, but I think
 it is more correct to have it call the DCON controls directly, rather then
 using the X driver as a proxy (which, will just turn around and use those
 same controls).

 This of course is contingent on the establishment of a solid power policy,
 which we'll need to guide us in tasks such as these.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1429#comment:3>
One Laptop Per Child <http://laptop.org/>