Hi, > Hi, > > As some of you might remember, I sent in a patch for screensaver > support for the Hurd console. I am resurrecting that patch now. > > All work has mostly be done. At the moment my biggest doubt is how to > configure the screensaver support when starting the console client. I > have two ideas for that: > > First of all, a screensaver can be registered by any plugin. So the > `life' plugin registers the `life' screensaver, a screensaver that > shows conways game of life. There is a blank plugin that registers > the screensaver blank, which just clears the screen. The vga driver > will register 3 screensavers: vga_standby, vga_suspend and vga_off. > These correspond with the DPMS power levels. > > To configure the screensaver I could use this: > > console -d vga .... --dpms-standby=vga_standby --dpms-off=vga_off > --dpms-standby-timeout=400 --dpms-off-timeout=800 --saver-events=INPUT,BELL > /dev/vcs > > In that case the console will start blanking after 400 seconds using > the vga_off screensaver and the display will turn off after > (400+800=)1200 seconds using vga_off. It will stop when someone > presses a key or the bell is activated. > > Another way to configure this would be: > > console -d vga .... --screensaver="vga_standby=400,vga_off=800" > --saver-events=INPUT,BELL /dev/vcs > > Or even: > > console -d vga .... --screensaver="vga_standby,vga_off" > --saver-events=INPUT,BELL /dev/vcs >
I think we need a message interface to the screensaver for configuration. This allows per user configuration. (ie. if another user logs in on the console, a program can be launched from her .bash_profile to reconfigure the screensaver to her personal settings). It also allows any fancy configuration scheme without impacting the console code at all. Cheers, Peter (p2).
signature.asc
Description: Digital signature
_______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
