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

List:       kde-core-devel
Subject:    Re: KDE fragile?
From:       Stephan Kulow <coolo () kde ! org>
Date:       2000-09-11 22:12:56
[Download RAW message or body]

Lars Knoll wrote:
> 
> On Mon, 11 Sep 2000, Dirk Mueller wrote:
> > On Mon, 11 Sep 2000, Stephan Kulow wrote:
> > > Time for a faster KConfig then? After tomorrow I will have time to fix
> > > this.
> > > (God I love saying that :)
> >
> > A good start would be avoiding that KCharset has to set up completely
> > before KGlobal::fixedFont() / KGlobal::generalFont() succeeds. i.e. storing
> > the raw X11 font name in the global config instead of just the family name
> > and the size would be a start (saving 20%).
> 
> I am sort of guilty for the kcharsets part... It was however never designed
> to be used during startup.
> 
> We do not want to store raw font names in config files, but we could
> easily get rid of the setQFont call in kglobal IMO. This was never intended
> to be called there, and should be done only in case the reading of the fonts
> from the config object failed (the config file does not specify a global
> font).
> 
> > the next part would be fixing Kcharsets..
> 
> The problem is, that the the first time we requore a specific charset, we
> have to initialize the data structure of kcharsets. getAvailableCharsets is
> however not really fast. But I do also wonder how much of the time in this
> method is spend in the initialization of the QFontDatabase used.
> 
Could _that_ part benefit from ksycoca perhaps?

Greetings, Stephan

-- 
... but you ain't had mine

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