--===============0296746497==
Content-Type: multipart/signed;
  boundary="nextPart2258764.yCl0bnlkNp";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2258764.yCl0bnlkNp
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 31 July 2006 16:24, Ferdinand Gassauer wrote:
> KDE claims to be network transparent, which is totally true for all (or at
> least most) KDE applications.
There are a number of applications that aren't network transparent.

> But many important non-KDE applications (gimp, OO obviously, Amarok less
> obviously, the user usually does not know about the xine engine behind) a=
re
> embedded nicely in the KDE desktop, but lack full support of KIO.
I can accept that amarok might be more helpful, but how do you expect KDE t=
o=20
modify the behaviour of the gimp or OpenOffice? They aren't KDE application=
s.=20
They don't use our file dialogs.

> IMHO KDE should handle this situation more gracefully by telling the user,
> that network transparency is not supported for this application instead of
> leaving it to the application to issue error messages like mentioned in
> comment 3 above or "file not existent....".
KDE can't do that. Only KDE applications can.

Brad

--nextPart2258764.yCl0bnlkNp
Content-Type: application/pgp-signature

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

iD8DBQBEzd6rGwwszQ/PZzgRAiaaAKCbguMZ00Gi7aFatpFgt1nMi0jq0QCgjNv2
OyPNRHmk2tNxJH47Bi6xAjo=
=mggS
-----END PGP SIGNATURE-----

--nextPart2258764.yCl0bnlkNp--

--===============0296746497==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============0296746497==--