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

List:       kde-devel
Subject:    Re: Size of 2.0 compared to 1.1.1 ?
From:       Mosfet <mosfet () jorsm ! com>
Date:       1999-10-28 11:48:48
[Download RAW message or body]

David Faure wrote:
> 
> > > Hopefully using ksycoca for kicker would save quite a lot of memory as
> well,
> > > but I need
> > > some time and thoughts to do that.
> > >
> >
> > Huh? Kicker uses KSycoca.
> 
> Not for the K menu, which shows services ("applications"), that are
> already in ksycoca.
> kicker/kpanel parse the .desktop files by themselves.
> Storing the relative path ("Internet/kppp.kdesktop" for instance) in ksycoca
> 
> might speed up and save memory I think - but as I said this needs thinking
> first.
> I'm not saying it has to be done, yet.
> 
> Is the K menu built all at once, or submenu by submenu while browsing
> through them ?
> 

It builds them on demand with a configurable flush delay for releasing
the memory for the popupmenus. It also shares almost all the code with
the QuickBrowser. 

> --
> David Faure
> faure@kde.org - KDE developer
> david@mandrakesoft.com - Mandrake
> david.faure@cramersystems.com - Cramer Systems

-- 
Daniel M. Duley - Unix developer & sys admin.
mosfet@mandrakesoft.com
mosfet@kde.org
mosfet@jorsm.com

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