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

List:       kde-core-devel
Subject:    Re: KDE fragile?
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-09-12 19:36:31
[Download RAW message or body]

On Tue, 12 Sep 2000, Waldo Bastian wrote :
>On Tue, 12 Sep 2000, Stephan Kulow wrote:
>> Hmm, we have tons of such problems. It's time we move ksycoca into
>> kdecore.
>> How much of ksycoca depends on kio anyway these days? If it helps speed,
>> I would say it's an issue we should think about.
>
>Well, we have libksycoca and kded/kbuildsycoca. kded/kbuildsycoca probably 
>depends on kio
For KDirWatch, but not for network transparency....

>but libksycoca actually doesn't dpend that much on kio I think.
>
>If you link libksycoca against libkdecore instead of libkio you will get a 
>list of unresolved symbols which seems to be solvable by moving some stuff 
>around. E.g. moving krun, kdirlister and kfileitem to kio. And 
>kprotocolmanager back to kdecore.
>
>KMimeType seems to use `KIO::findDeviceMountPoint(QString const &)' so that 
>one will have to move as well I guess.

You can't move kmimetype itself :

And 
pid_t KDEDesktopMimeType::runLink( const KURL& _url, const KSimpleConfig &cfg )
{
[...]
  (void)new KRun( url );
}  

but in fact that's not what you need. If you put the _basis_ for ksycoca
in kdecore (i.e. the factories and the base classes) then you can extend
ksycoca with new stuff, without the need to put kmimetype itself
in ksycoca, afaics.

But /me thinks it's a bit late in the process for restructuring the libs
(thinking about non-cvs developers).

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://www.mandrakesoft.com/~david/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today
See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2

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