[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Memory consumption in KDE 2.0
From:       Roberto Alsina <ralsina () unl ! edu ! ar>
Date:       1999-05-04 11:47:23
[Download RAW message or body]

On Tue, 4 May 1999, Martin Jones wrote:

> "Dirk A. Mueller" wrote:
> > 
> > Stephan Kulow <coolo@itm.mu-luebeck.de> wrote:
> > 
> > > the screensaver is activated by a signal. But we agree that it
> > > shouldn't be in memory as long as no screensaver is active, but only a
> > > very small wrapper.
> > 
> > before adding a new wrapper, couldn't some "core" component like
> > kbgndwm take over that job ?
> 
> Well, how about making the KDE screensavers stand-alone programs
> like xscreensaver and using kbgndwm to run the screensaver when
> needed.  This would also allow you to use any screensaver from
> xlock and xscreensaver without porting.

Then why not just use xscreensaver's "modes"?

 ("\''/").__..-''"`-. .         Roberto Alsina
 `9_ 9  )   `-. (    ).`-._.`)  ralsina@unl.edu.ar
 (_Y_.)' ._   ) `._`.  " -.-'   Centro de Telematica
  _..`-'_..-_/ /-'_.'           Universidad Nacional del Litoral
(l)-'' ((i).' ((!.'             Santa Fe - Argentina
                                KDE Developer (MFCH)
The problem with winning the rat race is that you are still a rat (Lili Tomlin)

[prev in list] [next in list] [prev in thread] [next in thread]