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

List:       kde-devel
Subject:    Re: RFC Extending KURL ( KExtendedURL ??? )
From:       Waldo Bastian <bastian () ens ! ascom ! ch>
Date:       1999-07-19 10:51:54
[Download RAW message or body]

Dawit Alemayehu wrote:
> 
> Hello,
> 
> I am thinking about extending the functionality of KURL to support incomplete (
> better known as short or smart ) URLs as well as weird, but valid ( according
> to RFC 1738 ) formats such //www.kde.org.  I was wondering whether it would be
> best to modify KURL itself,  add a child class such as KEnhancedURL or
> KExtendedURL or simply let the apps deal with it as is the current case.  I
> personally prefer doing the second as the work involved is trivial, simply
> override ::parse() in KURL and perhaps add a couple of variables and methods in
> a subclass.

Handling broken URLs is no priority for KURL. If you can add a quick hack 
so that a broken URL is handled correctly it is great as long as it doesn't 
cause any valid URL to get broken.

The code in minicli.C does not handle URL's but handles user input which
could be a URL. This code does not belong in KURL. You can put this
code in a KEnhancedURL class but I would prefer to call it KBrokenURL or
KUserURL instead.  

> kdelibs/khtml will also need this in order to combat the
> the weird, but valid formats being used in HREF tags ( there are/were a couple
> of bugs for kfm regarding this situation). 

Weird but valid formats need to be handled correctly by KURL. 

Cheers,
Waldo
-- 
The "gui" in "Penguin" is pronounced "K-D-E"

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