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

List:       kde-devel
Subject:    Re: Memory consumption in KDE 2.0
From:       Waldo Bastian <bastian () ens ! ascom ! ch>
Date:       1999-05-04 12:40:23
[Download RAW message or body]

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.

I think this is The Right Thing(tm) todo.

SuSE can of course always preload the screensaver for faster startup >:)

Cheers,
Waldo
-- 
KDE, Making The Future of Computing Available Today       
http://www.kde.org

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