Qt 4.8 QUrl.toLocalFile behavior change, impacts to KUrl (and friends)

Thiago Macieira thiago at kde.org
Sun Oct 30 18:36:09 GMT 2011


On Sunday, 30 de October de 2011 19:02:48 Kevin Kofler wrote:
> But that doesn't change much of the rest of my message: we definitely do
> need an API which treats relative paths as file paths (for most
> applications) and an API which treats relative paths as relative URLs (for
> web browsers and such).
> 
> I think there should be 3 ways to construct a URL:
> 1. from a path (always), i.e. the current KUrl::fromPath

QUrl::fromLocalFile

> 2. heuristically (replacing the current KUrl::KUrl and KUrl::fromPathToUrl):
> * absolute paths should be file paths
>    * relative paths should be file paths (!) (currently, they're URLs)
>    * everything with a URL scheme (protocol) should be a URL

I disagree and will not implement this in QUrl.

> 3. from a URL (always) – web browsers or any other app where the relative
>    context is a URL context should use this instead of 2.

QUrl's constructor, QUrl::fromEncoded

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20111030/50babee9/attachment.sig>


More information about the kde-core-devel mailing list