nanogui: Screensaver?
Subject:
Re: Screensaver?
From:
Jordan Crouse ####@####.####
Date:
17 Oct 2000 13:33:28 -0000
Message-Id: <39EC55AA.8080309@censoft.com>
You all have very good points. I guess I just can't betry my kernel
hacker heritage when I say that all of these things should be a client
level concept. There comes a point in the architecture when you just
shouldn't put anything more into the server. But then again, thats my
"upbringing" if you will. Its more of a style and personal prefrence
battle that us hackers like to get into (emacs vs. VI, etc, etc...)
But hey, thats why open source kicks butt in the first place. The
project will be better for us having battled here today.
Happy hacking to all!
Jordan
Nils Faerber wrote:
> On Tue, 17 Oct 2000, Alex Holden wrote:
>
>> On Mon, 16 Oct 2000, Nils Faerber wrote:
>>
>>> OK. As I said no problem with me, I just want to extend my iPaq's
>>> battery life. Which way the screen is turned off is rather irrelevant
>>
>> You're talking about a screen blanker (something which turns the display
>> hardware off to conserve power), not a screen saver (something which
>> displays patterns and things on the screen to amuse and (supposedly)
>> avoid screen burn-in). I agree that a screen blanker function in the
>
> Ooops, then we had a language problem here and I was not precise enough about
> what I wanted, sorry.
>
>
>> main server select loop would be a good idea (so if all you want to do is
>> conserve your PDA's battery life you don't have to waste a lot of memory
>> and processor time doing it), and if you want a screen saver that should
>> be done as a seperate process which overrides the blanker, monitors
>> keyboard and mouse events, and grabs the root window to draw things on it
>> when it times out.
>
> Yep, exactly!
>
> So then the discussion is more or less open again.
> Should this really become a part of the server?
> If yes we would have to create some API functions for applications to modify
> the timeout(s). We should IMHO have two timers. Microwindows is clearly aimed
> at the embedded market and most embedded devices use LCDs with backlight in
> some form. For most of them for example Linux supports switching off the
> backlight independantly from the LCD itself. So the screenblanker coudl switch
> off the backlight upon the first timeout and the whole LCD after the second
> timeout (values of 0 should disable the respective function). And that's about
> all the server is supposed to do.
>
> Greg, what do you think about this?
> Or anyone else?
>
>
>> : Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
>
> Thanks for your help to clarify this!
> CU
> nils faerber
>
