--nextPart2369354.5dFlodZFln
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le Dimanche 26 Juin 2005 17:43, David Faure a =C3=A9crit :
> We could provide resolved url(s) using the standard way (text/uri-list)
> and the kde-specific url(s) in addition, using another mimetype.
> Then the receiver can pick kde protocols if it's a kde app, otherwise the
> standard text/uri-list.

That would solve the issue indeed!
Which mimetype should we use?

> Quite easy, except that KURLDrag can't call=20
> mostLocalURL itself, so it needs a new API for setting the list of resolv=
ed
> URLs.

Just point me where to start and I'll look into it.
Can you tell me why KURLDrag can't call mostLocalURL btw?

Regards.
=2D-=20
K=C3=A9vin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le ma=C3=AEtre sans disciple, Ni le disciple sans ma=C3=AEtre,
Ne font reculer l'ignorance."

--nextPart2369354.5dFlodZFln
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCvs4ZB0u7y43syeIRAmtQAKCEMrnI1YZ/lTgMzAdL0HGyOfeZMgCeMKX5
wUEuzHMNZgkCzZLYpSdRwGw=
=h3dV
-----END PGP SIGNATURE-----

--nextPart2369354.5dFlodZFln--