QUrl in KDE 4

Leo Savernik l.savernik at aon.at
Fri May 20 14:31:44 BST 2005

Am Freitag, 20. Mai 2005 07:08 schrieb Thiago Macieira:
> Michael Pyne wrote:
> >The theory's all well and good guys, but if people are using a URL, it's
> >because they don't *need* a URI, which generally means they're not doing
> >URI-like things to it.  If programs are trying to turn URLs into URIs in
> > a class that doesn't design it, they're buggy.
> I'm sorry, but reality proves you wrong. People ARE using URIs, even if
> they don't know they are.

Agreed. There's no need to impose additional burden upon the application 
programmers by making up a class hierarchy of URL/URI representations.
> The prime example are mailto: URIs. They are not URLs, yet everyone
> expects them to work with KURL and QUrl.

Don't forget the data: scheme (they are, ironically, called "URLs" in the 
defining rfc2397 ;-) )

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050520/fa7c36b9/attachment.sig>

More information about the kde-core-devel mailing list