From kde-i18n  Mon Apr 05 21:54:05 1999
From: weis () stud ! uni-frankfurt ! de
Date: Mon, 05 Apr 1999 21:54:05 +0000
To: kde-i18n
Subject: Re: new KURL, ...
X-MARC-Message: https://marc.info/?l=kde-i18n&m=92334960403888

Hi,

On Mon, 5 Apr 1999, David Faure wrote:

> On Mon, Apr 05, 1999 at 12:32:29AM +0200, Reginald Stadlbauer wrote:
> > Hi!
> > I just fixed KOffice to work with the new KURL and found a problem. KURL
> > requires the kdelnk files from kdebase/kioslave/* to be able to parse an
> > url and return something useful. But for some reason I had no kdebase
> > installed, so I couldn't load anything in the koffice (urls were malformed). As
> > kdebase is not really required for koffice and KURL from kdelibs is depended on
> > a kdebase module (kioslave) at the moment, what do you think about moving
> > kioslave to kdelibs?
> 
> Ah, right, this is a problem.
> In fact, it makes sense for all kioslaves that URL are not understood if
> they're not installed, except for the "file://" URLs. You don't need a
> kioslave to read a file on your hard disk ;)
> I would suggest moving only file.kdelnk to kdelibs.
> Or better : have file:/ urls recognised by KURL even if no .kdelnk is installed.
> Torben ?

What about that: If KProtocolManager does not find protocols it sets
a flag. KURL asks for the flag. if set, it does not test wether the
URL is known.

> 
> BTW, we have the same problem with tar : no kioslave currently exists, so
> no URL containing "tar:/" is considered valid. This is not really a problem 
> for konqy, since kio_tar doesn't exist anyway, but it's a problem for
> kurltest which likes to test tar urls ;)

Ooops.

However, I tested gzip:/decompress#file:/something and it really works.
It decompressed for me :-) Now I like nested URls again :-)

Bye
Torben
 
> -- 
> David FAURE
> david.faure@insa-lyon.fr, faure@kde.org
> http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
> KDE, Making The Future of Computing Available Today
> 
>